Tag: NSA

Wednesday Links

  • Federal judge dismisses charges against Blackwater guards over the killing of 17 in Baghdad. David Isenberg: “The fact that the Blackwater contractors are not getting a trial will only serve to further increase suspicion of and hostility towards security contractors. It is going to be even more difficult for them to gain the trust of local populations or government officials in the countries they work in.”
  • New report shows state and local government workers have higher average compensation levels than private workers.
  • Podcast: “Televising and Subsidizing the Big Game” featuring Neal McCluskey. “Everybody should watch the National College Football Championship because whether you’re interested or not, you are paying for it,” he says.

McCain: Interests of Defense Contractors May Conflict with US National Interest

USA Today reports that retired military officers join the boards of directors of, or become employees of, defense contractors and take home big bags of money doing so.  Not surprising.  At the same time, the paper reports, lots of them are being paid by the Pentagon to be “senior mentors” of their former colleagues. Not being government employees, but rather independent contractors, these folks aren’t subject to government ethics rules.  To take one example, as chairman of BAE Systems, Gen. Anthony Zinni is clearing almost a million a year, in addition to his $129,000 per year government pension.  In addition to all that, the Pentagon pays him about $2,000 per day to “mentor” people at DOD.

As the article points out, information is almost invaluable to the defense contractors in these contexts.  The knowledge of what’s going on at DOD is extremely useful for planners at the defense companies, and so while the retired officers are protesting that being paid nearly $2,000 per day by DOD for their work as mentors is “way below the industry average,” it increases their value to, and presumably their compensation from, their military-industrial employers.  As one coordinator of the mentors program told the retired officers, “you’re getting paid in two ways–monetarily and informationally.”

This isn’t too surprising a story, but the crowning irony comes as Sen. John McCain calls for an ethics rewrite and offers his view that “the important thing is that [the involved officers] avoid the appearance of conflict.” This is a puzzling remark coming from a man whose top foreign-policy adviser was collecting hundreds of thousands of dollars from the Georgian government to lobby McCain at the same time he was being paid by McCain to advise him on foreign policy.

McCain’s thoughts about conflict of interest in that instance?  He was “so proud” of his lobbyist-cum-adviser.  Presumably once McCain issued his ridiculous “today we are all Georgians” fatwa it became a patriotic duty to take money from foreign governments to represent their interests.  But in the case of the proposed reforms–which would attempt to institute some semblance of transparency in these mentoring deals–one can only wish the senator from Arizona the best.

The FISA Amendments: Behind the Scenes

I’ve been poring over the trove of documents the Electronic Frontier Foundation has obtained detailing the long process by which the FISA Amendments Act—which substantially expanded executive power to conduct sweeping surveillance with little oversight—was hammered out between Hill staffers and lawyers at the Department of Justice and intelligence agencies. The really interesting stuff, of course, is mostly redacted, and I’m only partway though the stacks, but there are a few interesting tidbits so far.

As Wired has already reported, one e-mail shows Bush officials feared that if the attorney general was given too much discretion over retroactive immunity for telecoms that aided in warrantless wiretapping, the next administration might refuse to provide it.

A couple other things stuck out for me. First, while it’s possible they’ve been released before and simply not crossed my desk, there are a series of position papers — so rife with  underlining that they look like some breathless magazine subscription pitch — circulated to Congress explaining the Bush administration’s opposition to various proposed amendments to the FAA. Among these was a proposal by Sen. Russ Feingold (D-WI) that would have barred “bulk collection” of international traffic and required that the broad new intelligence authorizations specify (though not necessarily by name) individual targets. The idea here was that if there were particular suspected terrorists (for instance) being monitored overseas, it would be fine to keep monitoring their communications if they began talking with Americans without pausing to get a full-blown warrant — but you didn’t want to give NSA carte blanche to just indiscriminately sweep in traffic between the U.S. and anyone abroad. The position paper included in these documents is more explicit than the others that I’ve seen about the motive for objecting to the bulk collection amendment. Which was, predictably, that they wanted to do bulk collection:

  • It also would prevent the intelligence community from conducting the types of intelligence collection necessary to track terrorits and develop new targets.
  • For example, this amendment could prevent the intelligence community from targeting a particular group of buildings or a geographic area abroad to collect foreign intelligence prior to operations by our armed forces.

So to be clear: Contra the rhetoric we heard at the time, the concern was not simply that NSA would be able to keep monitoring a suspected terrorist when he began calling up Americans. It was to permit the “targeting” of entire regions, scooping all communications between the United States and the chosen area.

One other exchange at least raises an eyebrow.  If you were following the battle in Congress at the time, you may recall that there was a period when the stopgap Protect America Act had expired — though surveillance authorized pursuant to the law could continue for many months — and before Congress approved the FAA. A week into that period, on February 22, 2008, the attorney general and director of national intelligence sent a letter warning Congress that they were now losing intelligence because providers were refusing to comply with new requests under existing PAA authorizations. A day later, they had to roll that back, and some of the correspondence from the EFF FOIA record makes clear that there was an issue with a single recalcitrant provider who decided to go along shortly after the letter was sent.

But there’s another wrinkle. A week prior to this, just before the PAA was set to expire, Jeremy Bash, the chief counsel for the House Permanent Select Committee on Intelligence, sent an email to “Ken and Ben,” about a recent press conference call. It’s clear from context that he’s writing to Assistant Attorney General Kenneth Wainstein and General Counsel for the Director of National Intelligence Ben Powell about this press call, where both men fairly clearly suggest that telecoms are balking for fear that they’ll no longer be immune from liability for participation in PAA surveillance after the statute lapses. Bash wants to confirm whether they really said that “private sector entities have refused to comply with PAA certifications because they were concerned that the law was temporary.” In particular, he wants to know whether this is actually true, because “the briefs I read provided a very different rationale.”  In other words, Bash — who we know was cleared for the most sensitive information about NSA surveillance — was aware of some service providers being reluctant to comply with “new taskings” under the law, but not because of the looming expiration of the statute. One of his correspondents — whether Wainstein or Powell is unclear — shoots back denying having said any such thing (read the transcript yourself) and concluding with a terse:

Not addressing what is in fact the situation on both those issues (compliance and threat to halt) on this email.

In other words, the actual compliance issues they were encountering would have to be discussed over a more secure channel. If the issue wasn’t the expiration, though, what would the issue have been? The obvious alternative possibility is that NSA (or another agency) was attempting to get them to carry out surveillance that they thought might fall outside the scope of either the PAA or a particular authorization. Given how sweeping these were, that should certainly give us pause. It should also raise some questions as to whether, even before that one holdout fell into compliance, the warning letter from the AG and the DNI was misleading. Was there really ever a “gap” resulting from the statute’s sunset, or was it a matter of telecoms balking at an attempt by the intelligence community to stretch the bounds of their legal authority? The latter would certainly fit a pattern we saw again and again under the Bush administration: break the law, inducing a legal crisis, then threaten bloody mayhem if the unlawful program is forced to abruptly halt — at which point a nervous Congress grants its blessing.

Some Thoughts on the New Surveillance

Last night I spoke at “The Little Idea,” a mini-lecture series launched in New York by Ari Melber of The Nation and now starting up here in D.C., on the incredibly civilized premise that, instead of some interminable panel that culminates in a series of audience monologues-disguised-as-questions, it’s much more appealing to have a speaker give a ten-minute spiel, sort of as a prompt for discussion, and then chat with the crowd over drinks.

I’d sketched out a rather longer version of my remarks in advance just to make sure I had my main ideas clear, and so I’ll post them here, as a sort of preview of a rather longer and more formal paper on 21st century surveillance and privacy that I’m working on. Since ten-minute talks don’t accommodate footnotes very well, I should note that I’m drawing for a lot of these ideas on the excellent work of legal scholars Lawrence Lessig and Daniel Solove (relevant papers at the links). Anyway, the expanded version of my talk after the jump:

Since this is supposed to be an event where the drinking is at least as important as the talking, I want to begin with a story about booze—the story of a guy named Roy Olmstead.  Back in the days of Prohibition, Roy Olmstead was the youngest lieutenant on the Seattle police force. He spent a lot of his time busting liquor bootleggers, and in the course of his duties, he had two epiphanies. First, the local rum runners were disorganized—they needed a smart kingpin who’d run the operation like a business. Second, and more importantly, he realized liquor smuggling paid a lot better than police work.

So Roy Olmstead decided to change careers, and it turned out he was a natural. Within a few years he had remarried to a British debutante, bought a big white mansion, and even ran his own radio station—which he used to signal his ships, smuggling hooch down from Canada, via coded messages hidden in broadcasts of children’s bedtime stories. He did retain enough of his old ethos, though, that he forbade his men from carrying guns. The local press called him the Bootleg King of Puget Sound, and his parties were the hottest ticket in town.

Roy’s success did not go unnoticed, of course, and soon enough the feds were after him using their own clever high-tech method: wiretapping. It was so new that they didn’t think they needed to get a court warrant to listen in on phone conversations, and so when the hammer came down, Roy Olmstead challenged those wiretaps in a case that went all the way to the Supreme Court—Olmstead v. U.S.

The court had to decide whether these warrantless wiretaps had violated the Fourth Amendment “right of the people to be secure in their persons, houses, papers, and effects against unreasonable searches and seizures.” But when the court looked at how a “search” had traditionally been defined, they saw that it was tied to the common law tort of trespass. Originally, that was supposed to be your remedy if you thought your rights had been violated, and a warrant was a kind of shield against a trespass lawsuit. So the majority didn’t see any problem: “There was no search,” they wrote, “there was no seizure.” Because a search was when the cops came on to your property, and a seizure was when they took your stuff. This was no more a search than if the police had walked by on the sidewalk and seen Roy unpacking a crate of whiskey through his living room window: It was just another kind of non-invasive observation.

So Olmstead went to jail, and came out a dedicated evangelist for Christian Science. It wasn’t until the year after Olmstead died, in 1967, that the Court finally changed its mind in a case called Katz v. U.S.: No, they said, the Fourth Amendment protects people and not places, and so instead of looking at property we’re going to look at your reasonable expectation of privacy, and on that understanding, wiretaps are a problem after all.

So that’s a little history lesson—great, so what? Well, we’re having our own debate about surveillance as Congress considers not just reauthorization of some expiring Patriot Act powers, but also reform of the larger post-9/11 surveillance state, including last year’s incredibly broad amendments to the Foreign Intelligence Surveillance Act. And I see legislators and pundits repeating two related types of mistakes—and these are really conceptual mistakes, not legal mistakes—that we can now, with the benefit of hindsight, more easily recognize in the logic of Olmstead: One is a mistake about technology; the other is a mistake about the value of privacy.

First, the technology mistake. The property rule they used in Olmstead was founded on an assumption about the technological constraints on observation. The goal of the Fourth Amendment was to preserve a certain kind of balance between individual autonomy and state power. The mechanism for achieving that goal was a rule that established a particular trigger or tripwire that would, in a sense, activate the courts when that boundary was crossed in order to maintain the balance. Establishing trespass as the trigger made sense when the sphere of intimate communication was coextensive with the boundaries of your private property. But when technology decoupled those two things, keeping the rule the same no longer preserved the balance, the underlying goal, in the same way, because suddenly you could gather information that once required trespass without hitting that property tripwire.

The second and less obvious error has to do with a conception of the value of privacy, and a corresponding idea of what a privacy harm looks like.  You could call the Olmstead court’s theory “Privacy as Seclusion,” where the paradigmatic violation is the jackboot busting down your door and disturbing the peace of your home. Wiretapping didn’t look like that, and so in one sense it was less intrusive—invisible, even. In another sense, it was more intrusive because it was invisible: Police could listen to your private conversations for months at a time, with you none the wiser. The Katz court finally understood this; you could call their theory Privacy as Secrecy, where the harm is not intrusion but disclosure.

But there’s an even less obvious potential harm here. If they didn’t need a warrant, everyone who made a phone call would know that they could whenever they felt like it. Wiretapping is expensive and labor intensive enough that realistically they can only be gathering information about a few people at a time.  But if further technological change were to remove that constraint, then the knowledge of the permanent possibility of surveillance starts having subtle effects on people’s behavior—if you’ve seen the movie The Lives of Others you can see an extreme case of an ecology of constant suspicion—and that persists whether or not you’re actually under surveillance.  To put it in terms familiar to Washingtonians: Imagine if your conversations had to be “on the record” all the time. Borrowing from Michel Foucault, we can say the privacy harm here is not (primarily) invasion or disclosure but discipline. This idea is even embedded in our language: When we say we want to control and discipline these police powers, we talk about the need for over-sight and super-vision, which are etymologically basically the same word as sur-veillance.

Move one more level from the individual and concrete to the abstract and social harms, and you’ve got the problem (or at least the mixed blessing) of what I’ll call legibility. The idea here is that the longer term possibilities of state control—the kinds of power that are even conceivable—are determined in the modern world by the kind and quantity of information the modern state has, not about discrete individuals, but about populations.  So again, to reach back a few decades, the idea that maybe it would be convenient to round up all the Americans of Japanese ancestry—or some other group—and put them in internment camps is just not even on the conceptual menu unless you have a preexisting informational capacity to rapidly filter and locate your population that way.

Now, when we talk about our First Amendment right to free speech, we understand it has a certain dual character: That there’s an individual right grounded in the equal dignity of free citizens that’s violated whenever I’m prohibited from expressing my views. But also a common or collective good that is an important structural precondition of democracy. As a citizen subject to democratic laws, I have a vested interest in the freedom of political discourse whether or not I personally want to say–or even listen to–controversial speech. Looking at the incredible scope of documented intelligence abuses from the 60s and 70s, we can add that I have an interest in knowing whether government officials are trying to silence or intimidate inconvenient journalists, activists, or even legislators. Censorship and arrest are blunt tactics I can see and protest; blackmail or a calculated leak that brings public disgrace are not so obvious. As legal scholar Bill Stuntz has argued, the Founders understood the structural value of the Fourth Amendment as a complement to the First, because it is very hard to make it a crime to pray the wrong way or to discuss radical politics if the police can’t arbitrarily see what people are doing or writing in their homes.

Now consider how we think about our own contemporary innovations in search technology. The marketing copy claims PATRIOT and its offspring “update” investigative powers for the information age—but what we’re trying to do is stretch our traditional rules and oversight mechanisms to accommodate search tools as radically novel now as wiretapping was in the 20s. On the traditional model, you want information about a target’s communications and conduct, so you ask a judge to approve a method of surveillance, using standards that depend on how intrusive the method is and how secret and sensitive the information is. Constrained by legal rulings from a very different technological environment, this model assumes that information held by third parties—like your phone or banking or credit card information—gets very little protection, since it’s not really “secret” anymore. And the sensitivity of all that information is evaluated in isolation, not in terms of the story that might emerge from linking together all the traces we now inevitable leave in the datasphere every day.

The new surveillance typically seeks to observe information about conduct and communications in order to identify targets. That may mean using voiceprint analysis to pull matches for a particular target’s voice or a sufficiently unusual regional dialect in a certain area. It may mean content analysis to flag e-mails or voice conversations containing known terrorist code phrases. It may mean social graph analysis to reidentify targets who have changed venues by their calling patterns.  If you’re on Facebook, and a you and bunch of your friends all decide to use fake names when you sign up for Twitter, I can still reidentify you given sufficient computing power and strong algorithms by mapping the shape of the connections between you—a kind of social fingerprinting. It can involve predictive analysis based on powerful electronic “classifiers” that extract subtle patterns of travel or communication or purchases common to past terrorists in order to write their own algorithms for detecting potential ones.

Bracket for the moment whether we think some or all of these methods are wise.  It should be crystal clear that a method of oversight designed for up front review and authorization of target-based surveillance is going to be totally inadequate as a safeguard for these new methods.  It will either forbid them completely or be absent from the parts of the process where the dangers to privacy exist. In practice what we’ve done is shift the burden of privacy protection to so-called “minimization” procedures that are meant to archive or at least anonymize data about innocent people. But those procedures have themselves been rendered obsolete by technologies of retrieval and reidentification: No sufficiently large data set is truly anonymous.

And realize the size of the data sets we’re talking about. The FBI’s Information Data Warehouse holds at least 1.5 billion records, and growing fast, from an array of private and government sector sources—some presumably obtained using National Security Letters and Patriot 215 orders, some by other means. Those NSLs are issued by the tens of thousands each year, mostly for information about Americans.  As of 2006, we know “some intelligence sources”—probably NSA’s—were  growing at a rate of 4 petabytes, that’s 4 million Gigabytes—each month.  Within about five years, NSA’s archive is expected to be measured in Yottabytes—if you want to picture one Yottabyte, take the sum total of all data on the Internet—every web page, audio file, and video—and multiply it by 2,000. At that point they will have to make up a new word for the next largest unit of data.  As J. Edgar Hoover understood all too well, just having that information is a form of power. He wasn’t the most feared man in Washington for decades because he necessarily had something on everyone—though he had a lot—but because he had so much that you really couldn’t be sure what he had on you.

There is, to be sure, a lot to be said against the expansion of surveillance powers over the past eight years from a more conventional civil liberties perspective.  But we also need to be aware that if we’re not attuned to the way new technologies may avoid our would tripwires, if we only think of privacy in terms of certain familiar, paradigmatic violations—the boot in the door—then like the Olmstead court, we may render ourselves blind to equally serious threats that don’t fit our mental picture of a privacy harm.

If we’re going to avoid this, we need to attune ourselves to the ways modern surveillance is qualitatively different from past search tools, even if words like “wiretap” and “subpoena” remain the same. And we’re going to need to stop thinking only in terms of isolated violations of individual rights, but also consider the systemic and structural effects of the architectures of surveillance we’re constructing.


Wednesday Links

  • Cato v. Heritage on the Patriot Act, Round III: “In hindsight, did Congress and the president react too hastily in 2001 by passing the Patriot Act just weeks after the 9/11 attacks?”

State Secrets, State Secrets Are No Fun

Despite Barack Obama’s frequent paeans to the value of transparency during the presidential campaign, his Justice Department has incensed civil liberties advocates by parroting the Bush administration’s broad invocations of the “state secrets privilege” in an effort to torpedo lawsuits challenging controversial interrogation and surveillance policies. Though in many cases the underlying facts have already been widely reported, DOJ lawyers implausibly claimed, not merely that particular classified information should not be aired in open court, but that any discussion of the CIA’s “extraordinary rendition” of detainees to torture-friendly regimes, or of the NSA’s warrantless wiretapping, would imperil national security.

That may—emphasis on may—finally begin to change as of October 1st, when new guidelines for the invocation of the privilege issued by Attorney General Eric Holder kick in. Part of the change is procedural: state secrets claims will need to go through a review board and secure the personal approval of the Attorney General. Substantively, the new rules raise the bar for assertions of privilege by requiring attorneys to provide courts with specific evidence showing reason to expect disclosure would result in “significant harm” to national security. Moreover, those assertions would have to be narrowly tailored so as to allow cases to proceed on the basis of as much information as can safely be disclosed.

That’s the theory, at any rate. The ACLU is skeptical, and argues that relying on AG guidelines to curb state secrets overreach is like relying on the fox to guard the hen house. And indeed, hours after the announcement of the new guidelines—admittedly not yet in effect—government attorneys were singing the state secrets song in a continuing effort to get a suit over allegations of illegal wiretapping tossed. The cynical read here is that the new guidelines are meant to mollify legislators contemplating statutory limits on state secrets claims while preserving executive discretion to continue making precisely the same arguments, so long as they add the word “significant” and jump through a few extra hoops. Presumably we’ll start to see how serious they are come October. And as for those proposed statutory limits, if the new administration’s commitment to greater  accountability is genuine, they should now have no objection to formal rules that simply reinforce the procedures and principles they’ve voluntarily embraced.

Bagram, Habeas, and the Rule of Law

Andrew C. McCarthy has an article up  at National Review criticizing a recent decision by Obama administration officials to improve the detention procedures in Bagram, Afghanistan.

McCarthy calls the decision an example of pandering to a “despotic” judiciary that is imposing its will on a war that should be run by the political branches. McCarthy’s essay is factually misleading, ignores the history of wartime detention in counterterrorism and counterinsurgency, and encourages the President to ignore national security decisions coming out of the federal courts.

More details after the jump.

McCarthy is Factually Misleading

McCarthy begins by criticizing a decision by District Judge John Bates to allow three detainees in Bagram, Afghanistan, to file habeas corpus petitions testing the legitimacy of their continued detention. McCarthy would have you believe that this is wrong because they are held in a combat zone and that they have already received an extraordinary amount of process by wartime detention standards. He is a bit off on both accounts.

First, this is not an instance where legal privileges are “extended to America’s enemies in Afghanistan.” The petition from Bagram originally had four plaintiffs, none of whom were captured in Afghanistan – they were taken into custody elsewhere and moved to Bagram, which is quite a different matter than a Taliban foot soldier taken into custody after an attack on an American base. As Judge Bates says in his decision, “It is one thing to detain t

hose captured on the surrounding battlefield at a place like Bagram, which [government attorneys] correctly maintain is in a theater of war. It is quite another thing to apprehend people in foreign countries – far from any Afghan battlefield – and then bring them to a theater of war, where the Constitution arguably may not reach.”

Judge Bates also took into account the political considerations of hearing a petition from Haji Wazir, an Afghan man detained in Dubai and then

moved to Bagram. Because of the diplomatic implications of ruling on an Afghan who is on Afghan soil, Bates dismissed Wazir’s petition. So much for judicial “despotism” and judicial interference on the battlefield, unless you define the world as your battlefield.

Second, the detainees have not been given very much process. Their detentions have been approved in “Unlawful Enemy Combatant Review Boards.” Detainees in these proceedings have no American representative, are not present at the hearings, and submit a written statement as to why they should be released without any knowledge of what factual basis the government is using to justify their detention. This is far less than the Combatant Status Review Tribunal procedures held insufficient in the Supreme Court’s Boumediene ruling.

Yes, Fix Detention in Afghanistan

McCarthy then chides the Obama administration for trying to get ahead of the courts by affording more process to detainees: “See, we can give the enemy more rights without a judge ordering us to do so!”

Well, yes. We should fix the detention procedures used in Afghanistan to provide the adequate “habeas substitute” required by Boumediene so that courts either: (1) don’t see a need to intervene; or (2) when they do review detention, they ratify the military’s decision more often than not.

Thing is, the only substitute for habeas is habeas. Habeas demands a hearing, with a judge, with counsel for both the detainee and the government, and a weighing of evidence and intelligence that a federal court will take seriously. If the military does this itself, then the success rate in both detaining the right people and sustaining detention decisions upon review are improved.

This is nothing new or unprecedented. Salim Hamdan, Usama Bin Laden’s driver, received such a hearing prior to his military commission. The CSRT procedures that the Bagram detainees are now going to face were insufficient to subject Hamdan to a military commission, so Navy Captain Keith Allred granted Hamdan’s motion for a hearing under Article V of the Geneva Conventions to determine his legal status.

Allred found that Hamdan’s service to Al Qaeda as Osama Bin Laden’s driver and occasional bodyguard, pledge of bayat (allegiance) to Bin Laden, training in a terrorist camp, and transport of weapons for Al Qaeda and affiliated forces supported finding him an enemy combatant. Hamdan was captured at a roadblock with two surface-to-air missiles in the back of his vehicle. The Taliban had no air force; the only planes in the sky were American. Hamdan was driving toward Kandahar, where Taliban and American forces were engaged in a major battle. The officer that took Hamdan into custody took pictures of the missiles in Hamdan’s vehicle before destroying them.

Hamdan’s past association with the Ansars (supporters), a regularized fighting unit under the Taliban, did not make him a lawful combatant. Though the Ansars wore uniforms and bore their arms openly, Hamdan was taken into custody in civilian clothes and had no distinctive uniform or insignia. Based on his “direct participation in hostilities” and lack of actions to make him a lawful combatant, Captain Allred found that Hamdan was an unlawful enemy combatant.

Hamdan’s Article V hearing should be the template for battlefield detention. Charles “Cully” Stimson at the Heritage Foundation, a judge in the Navy JAG reserves and former Bush administration detainee affairs official, wrote a proposal to do exactly that, Holding Terrorists Accountable: A Lawful Detention Framework for the Long War.

The more we legitimize and regularize these decisions, the better off we are. Military judges should be writing decisions on detention and publishing declassified versions in military law reporters. One of the great tragedies of litigating the detainees from the early days in Afghanistan is that a number were simply handed to us by the Northern Alliance with little to no proof and plenty of financial motive for false positives. My friends in the service tell me that we are still running quite a catch-and-release program in Afghanistan. I attribute this to arguing over dumb cases from the beginning of the war when we had little cultural awareness and a far less sophisticated intelligence apparatus. Detention has become a dirty word. By not establishing a durable legal regime for military detention, we created lawfare fodder for our enemies and made it politically costly to detain captured fighters.

The Long-Term Picture

McCarthy, along with too many on the Right, is fixated on maintaining executive detention without legal recourse as our go-to policy for incapacitating terrorists and insurgents. In the long run we need to downshift our conflicts from warmaking to law enforcement, and at some point detention transitions to trial and conviction.

McCarthy might blast me for using the “rule of law” approach that he associates with the Left and pre-9/11 counterterrorism efforts. Which is fine, since, just as federal judges “have no institutional competence in the conduct of war,” neither do former federal prosecutors.

Counterterrorism and counterinsurgency are not pursued solely by military or law enforcement means. We should use both. The military is a tool of necessity, but in the long run, the law is our most effective weapon.

History dictates an approach that uses military force as a means to re-impose order and the law to enforce it. The United States did this in Iraq, separating hard core foreign fighters from local flunkies and conducting counterinsurgency inside its own detention facilities. The guys who were shooting at Americans for a quick buck were given some job training and signed over to a relative who assumed legal responsibility for the detainee’s oath not to take up arms again. We moved detainees who could be connected to specific crimes into the Iraqi Central Criminal Court for prosecution. We did all of this under the Law and Order Task Force, establishing Iraqi criminal law as the law of the land.

We did the same in Vietnam, establishing joint boards with the Vietnamese to triage detainees into Prisoner of War, unlawful combatant, criminal defendant, and rehabilitation categories.

The Washington Post article on our detention reforms in Afghanistan indicates that we are following a pattern similar to past conflicts. How this is a novel and dangerous course of action escapes me.

Who’s the Despot Here?

McCarthy points to FDR as a model for our actions in this conflict between the Executive and Judiciary branches. He says that the President should ignore the judgments of the courts in the realm of national security and their “despotic” decrees. I do not think this word means what he thinks it means.

FDR was the despot in this chapter of American history, threatening to pack the Supreme Court unless they adopted an expansive view of federal economic regulatory power. The effects of an expansive reading of the Commerce Clause are felt today in an upending of the balance of power that the Founders envisioned between the states and the federal government.

McCarthy does not seem bothered by other historical events involving the President’s powers as Commander-in-Chief in the realm of national security. The Supreme Court has rightly held that the President’s war powers do not extend to breaking strikes at domestic factories when Congress declined to do so during the Korean War, trying American citizens by military commission in places where the federal courts are still open and functioning, and declaring the application of martial law to civilians unconstitutional while World War II was under way.

The Constitution establishes the Judiciary as a check on the majoritarian desires of the Legislature and the actions of the Executive, even during wartime. To think otherwise is willful blindness.