Tag: surveillance powers

The Risks of ‘John Doe’ Wiretaps

The Electronic Frontier Foundation has unearthed an interesting case of an improper use of surveillance in an investigation where the FBI had obtained “roving wiretap” authority. In a bizarre turn, the Bureau ended up eavesdropping on young children rather than their adult suspects for five days. The case is generating some attention because that same “roving wiretap” authority is one of the three surveillance powers set to expire in late May. The thing is, on the basis of what I can glean from the heavily redacted document EFF obtained via a Freedom of Information Act request, it’s not a case involving misuse of the roving authority. But it is a good concrete example of why the roving authority needs to be modified.

First, a bit of background: Roving wiretaps in criminal cases have been around since the 1980s, and were designed to let investigators follow a target across multiple telephone or Internet accounts when there’s reason to believe the suspect is frequently changing lines to frustrate surveillance. The Patriot Act extended the same power to intelligence investigations—fine in principle—but with a crucial difference. On the criminal side, there’s a tradeoff: For a conventional warrant, you have to specify every phone line and e-mail address covered by a wiretap warrant, but as long as you’ve got probable cause to link each line to criminal activity, you don’t necessarily need the identity of target. For a roving criminal wiretap, you don’t have to be limited to phones and accounts identified in advance, but you do have to name a target, and then directly ascertain that this named target is “proximate to” every facility you’re about to start collection on. Having both is even better, but you must have one or the other: either a named, known suspect or a list of specific facilities. Not so in the Patriot Act version used for intelligence wiretaps: They only require a “specific” description of the target. Critics argue that these “John Doe” warrants fall short of the Fourth Amendment’s requirement that warrants “particularly [describe] the place to be searched, and the persons or things to be seized,” and worry that they dramatically magnify the risk of erroneous collection of innocent people’s communications, especially given that intelligence wiretaps are, in many ways, already much more broad—and sweep in a lot more communications—than their counterparts on the criminal side.

The report EFF obtained concerned an investigation in which, it appears, roving wiretap authority was granted by at least one of two orders authorizing surveillance of two subjects, implied to be a married couple. Because it’s so heavily redacted, it’s necessary to read between the lines a bit, but as best I can reconstruct it, here’s what appears to have happened. In the course of the surveillance, an analyst was surprised to find that the conversations on one monitored line sounded like they involved “young children” who were not speaking the same language as the targets of the investigation. The Bureau nevertheless continued monitoring it for five days. Eventually, someone realized that they’d already been informed that the targets had disconnected that phone line a while ago—at which point, presumably, it was reassigned to the kids the FBI ended up wiretapping. In fact, the Bureau had initially refrained from collecting on that line, because the techies had determined that the subjects of the investigation had already disconnected it by the time surveillance was ready to begin. When the request for a renewal of the surveillance order was made, however, the lawyer at DOJ who drafted the renewal request mistakenly included that old number in the application, even though the case agents hadn’t put it in their request, and seemingly noted explicitly that it wasn’t being used by the targets anymore. But it got into the renewal order, at which point whoever was charged with implementing it dutifully began tapping some child’s phone line.

On face, the improper collection here was not the result of a “John Doe” warrant. Again, it’s hard to be absolutely sure through all the redactions, but the wording of the report strongly suggests that both targets were known, named individuals from the outset. Neither does the mistake here seem to have been a direct result of the roving authority. The wording suggests that the phone number at issue was actually specified in the initial order, rather than being selected as an exercise of roving discretion by the case agents. Even if it had initially been identified that way, the Bureau realized the subjects weren’t using it anymore before they actually went up on the number… at least originally. So one might think this is just a case of an error with conventional intel wiretapping, with no obvious implications for the roving authority as such. But I think there are a couple of important lessons to draw from it.

First as the report notes, the lawyer who drafted the renewal application and the case agents who reviewed and signed off on it all dropped the ball in failing to notice that it included a number they’d already concluded wasn’t being used by their targets. The FISA Court itself, however, was not really in any position to detect the error. So while it is an unqualified improvement that roving authority, since 2006, has included a notice requirement to the court within ten days of a wiretap roving to a new number or account, we need to be realistic about how much that’s going to accomplish. If an investigation starts going up on some conspicuously excessive number of accounts, or adding them with explanations to the court that sound wildly implausible, you might see a judge step in. But for the most part, when a tap goes up on the wrong person, we’re going to have to count on the agents and analysts themselves to notice.

Second, this is a good illustration of an important difference between criminal wiretap orders and FISA warrants. With a criminal order, interception is “minimized” in realtime—meaning you wouldn’t have had five days of automatic recording of every conversation on the line. Someone would listen to the start of the call, and as soon as it became apparent they couldn’t positively identify a known target as party to the communication, or that it was a personal call unrelated to the crime under investigation, monitoring would (in theory) stop. There’s necessarily some flexibility in practice, but the default on the criminal side is not “record everything”; on the intel side, it is.

Third, consider how important a named and identified target is to quickly catching an error. In this case, one of the technicians responsible for executing the wiretap noticed that the people named in the warrant had already disconnected service to one of the targeted phone lines. Having an actual identity for your target is also a decent proxy for having many other types of information about them: In this case, the analyst monitoring the recordings had a set of expectations about what the subjects sounded like and what language they would be speaking. In other cases, it might become apparent that a phone is making calls from one location when the target specified in the warrant is known to be elsewhere. Could these things be known for a target whose name isn’t? Sure. But as a rule, a description specific enough to guide initial targeting isn’t necessarily data-rich enough to enable very robust error-correction. Since the presumption is that people wiretapped under FISA warrants do not get notified even after the fact, this internal correction is the only real check on erroneous targeting. When wiretaps are limited neither by facility nor a known target identity, it’s not just that there’s greater risk of tapping the wrong line—it’s that it becomes much more likely nobody will be able to detect with any certainty that a mistake has been made.

The Sun Never Sets on the PATRIOT Act

A year ago, the protracted wrangling in Congress over the re-authorization of several expiring provisions of the PATRIOT ACT made plenty of headlines. Most observers expected the sunsetting powers to be extended, but civil libertarians hoped serious and sorely needed reforms might be part of the package. The House and Senate Judiciary Committees held multiple hearings on the topic, and an array of competing reform and reauthorization bills (PDF) were proposed, adding extra safeguards (of varying stringency) to the greatly expanded surveillance powers Congress had approved in the aftermath of the 9/11 attacks.

But Congress had a full plate, and so it punted—approving a straight one-year reauthorization without any modifications at the last minute. (You’d be forgiven for not noticing: The extension passed under the heading of the “Medicare Physician Payment Reform Act.”) As I
noted in December, however, the Justice Department has promised Congress that it will voluntarily adopt some of the measures that had been floated in those reform bills—which would be a fine thing in itself, but I worried that the move seemed calculated to reduce the impetus for binding legislation.

Well, I’ve just noticed—quite serendipitously, as there doesn’t appear to have been a whisper in the press—that the new House Intelligence Committee Chair, Mike Rogers (R-Mich.), has introduced yet another one-year extension, which would push the sunset of the expiring provisions back to the end of February 2012. Given the very limited number of days Congress has in session before the current deadline, and the fact that the bill’s Republican sponsor is only seeking another year, I think it’s safe to read this as signaling an agreement across the aisle to put the issue off yet again. (I’ve asked Rogers’s office for a comment and will update this post if I hear back.)

In the absence of a major scandal, though, it’s hard to see why we should expect the incentives facing legislators to be vastly different a year from now. Heck, we’ve had a pretty big scandal involving the misuse of National Security Letter powers, but even right on the heels of the Inspector General’s report documenting those abuses, the mildest reforms proffered last year died on the vine. I’d love to be proven wrong, but I suspect this is how reining in the growth of the surveillance state becomes an item perpetually on next year’s agenda.

Obama, Civil Liberties, & the Left

A confession: For all my innumerable policy disagreements with Barack Obama, on election night 2008, I found myself cheering with the rest of the throng on U Street. I fully expected to be appalled by much of his agenda – but I had also spent years covering the Bush administration’s relentless arrogation of power to the executive in the name of the War on Terror, its glib invocation of “national security” to squelch the least gesture toward transparency or accountability, its easy contempt for civil liberties and the rule of law. However fitfully, I thought, we could finally hope to see that appalling legacy reversed. And that seemed worth celebrating even if little else about the declared Obama agenda was.

As you might guess, I had a lot of disappointment coming – and not just with Obama.  There were, of course, principled civil libertarians on the left, like Salon’s Glenn Greenwald and Firedoglake’s Marcy Wheeler who kept banging the drum with undiminished fury. But many progressives seemed prepared to assume that Bush’s War-on-Terror policies would be out the door close on the heels of their author – conspicuously muting their outrage even as the reasons for it persisted. Meanwhile, the right – disappointingly if not entirely surprisingly – managed to fuse a penchant for breathless Stalin analogies with an attitude toward expansive surveillance powers and arbitrary detention authority that ranged from indifference to endorsement.

So it’s a little encouraging to see evidence over the last few weeks that burgeoning progressive disenchantment with Obama along a number of dimensions seems to be bringing these issues back into sharper focus. In a recent interview in Der Spiegel, Daniel Ellsberg of Pentagon Papers fame (described by the paper as a “lefty icon”) blasted Obama for “continuing the worst of the Bush administration in terms of civil liberties.” ACLU director Anthony Romero declared himself “disgusted” with the president, and Kevin Drum of Mother Jones catalogued a slew of reasons to agree with that appraisal. The real test of an issue’s salience, however, is whether it makes The Daily Show, and so perhaps the most significant bellwether is Jon Stewart’s decision to devote an unusually long and blistering segment to Obama’s failure to live up to his rhetoric on civil liberties and executive power:

The Daily Show With Jon Stewart Mon - Thurs 11p / 10c
Respect My Authoritah
www.thedailyshow.com
Daily Show Full Episodes Political Humor Tea Party

Democrats have spent most of the past decade playing defense against “soft on national security” attacks from the right, on the assumption – borne out thus far – that the base wasn’t going to punish them for folding on civil liberties issues. But while many progressive complaints now being aired are themselves the product of an unrealistic view of presidential puissance, this really is one sphere where the president has enormous latitude to unilaterally affect policy. It’s therefore also a set of issues where scant progress can’t easily be blamed on Republican obstructionism.

During the Bush era, we saw the brief emergence of a small but hardy left-right “strange bedfellows” coalition opposed to the FISA Amendments Act. Now I find myself wondering: If progressive grumblings on this front continue and grow louder, will the Tea Party movement that’s sprung up in the intervening years realize that their own rhetoric logically commits them to the same position? And if they do, will civil libertarians on the left be open to resurrecting that odd alliance?