Posts

3 Tech Issues the Non-Technologist NSA Technical Committee Needs to Address

A number of people are asking why I’m so shocked that President Obama appointed no technologists for his NSA Review Committee.

Here are three issues that should be central to the Committee’s discussions that are, in significant part, technology questions. There are more. But for each of these questions, the discussion should not be whether the Intelligence Community thinks the current solution is the best or only one, but whether it is an appropriate choice given privacy implications and other concerns.

  • Whether the Intelligence Community can accomplish the goals of the Section 215 dragnet without collecting all US person metadata
  • Whether the NSA can avoid collecting Multiple Communication Transactions as part of upstream collection
  • How to oversee unaudited actions of technical personnel

There are just three really obvious issues that should be reviewed by the committee. And for all of them, it would be really useful for someone with the technical background to challenge NSA’s claims to be on the committee.

Whether the Intelligence Community can accomplish the goals of the Section 215 dragnet without collecting all US person metadata

One of the most contentious NSA practices — at least as far as most Americans go — is the collection of all US person phone metadata for the Section 215 dragnet. Yet even Keith Alexander has admitted — here in an exchange with Adam Schiff in a House Intelligence Committee hearing on June 18 — that it would be feasible to do it via other means, though perhaps not as easy.

REP. SCHIFF: General Alexander, I want to ask you — I raised this in closed session, but I’d like to raise it publicly as well — what are the prospects for changing the program such that, rather than the government acquiring the vast amounts of metadata, the telecommunications companies retain the metadata, and then only on those 300 or so occasions where it needs to be queried, you’re querying the telecommunications providers for whether they have those business records related to a reasonable, articulable suspicion of a foreign terrorist connection?

Read more

FISC Judges Should Threaten NSA with Criminal Prosecution More Often

This James Bamford description of NSA efforts to avoid criminal prosecution in a 1975 investigation convinced me to point to evidence that then FISA Chief Judge John Bates — who is normally fairly deferential to the Executive Branch — cowed the government with threats of criminal prosecution.

The story starts in the October 3, 2011 opinion. After having laid out how the government was collecting US person data from the switches, Bates noted that the government wanted to keep on doing so.

The government’s submissions make clear not only that the NSA has been acquiring Internet transactions since before the Court’s approval of the first Section 702 certification in 2008,15 but also that NSA seeks to continue the collection of Internet transactions.

Noting that this collection had been going on longer than the 3 years the government had been using Section 702 of the FISA Amendments Act to justify its collection likely references a time when the NSA — led by Keith Alexander as far back as 2005 — was collecting that US person information with no legal sanction whatsoever as part of Dick Cheney’s illegal program.

Then, in footnote 15, Bates notes that sharing such illegally collected information is a crime.

The government’s revelations regarding the scope of NSA’s upstream collection implicate 50 U.S.C. § 1809(a), which makes it a crime (1) to “engage[] in electronic surveillance under color of law except as authorized” by statute or (2) to “disclose[] or use[] information obtained under color of law by electronic surveillance, knowing or having reason to know that the information was obtained through electronic surveillance not authorized” by statute. See [redacted] (concluding that Section 1809(a)(2) precluded the Court from approving the government’s proposed use of, among other things, certain data acquired by NSA without statutory authority through its “upstream collection”). The Court will address Section 1809(a) and related issues in a separate order. [my emphasis]

Now, I’m particularly interested in the redacted text, because it appears some FISC judge has had to issue this threat in a past (still-redacted) opinion. That threat may have applied to this same upstream collection, but from the time before the government pointed to FAA to justify it (again, Alexander’s tenure would overlap into that illegal period).

Read more

How the NCTC Gets Its NSA Data

I’m working on a more substantive post on the Section 702 Semiannual Compliance Assessment released last week as part of the I Con dump.

But for the moment, I want to point to a passage that begins to answer a question I asked two months ago: how does the data from NSA’s programs get to the National Counterterrorism Center, which then crunches that data and sends it out to other parts of government.

A footnote of the Assessment notes,

The other agency involved in implementing Section 702 is the National Counterterrorism Center (NCTC), which has a limited role, as reflected in the recently approved “Minimization Procedures Used by NCTC in connection with Information Acquired by the FBI pursuant to Section 702 of FISA, as amended.” Under these limited minimization procedures, NCTC is not authorized to receive unminimized Section 702 data. Rather, these procedures recognize that, in light of NCTC’s statutory counterterrorism role and mission, NCTC has been provided access to certain FBI systems containing minimized Section 702 information, and prescribe how NCTC is to treat that information. For example, because NCTC is not a law enforcement agency, it may not receive disseminations of Section 702 information that is evidence of a crime, but which has no foreign intelligence value; accordingly, NCTC’s minimization procedures require in situations in which NCTC personnel discover purely law enforcement information with no foreign intelligence value in the course of reviewing minimized foreign intelligence information that the NCTC personnel either purge that information (if the information has been ingested into NCTC systems) or not use, retain, or disseminate the information (if the information has been viewed in FBI systems). No incidents of noncompliance with the NCTC minimization procedures were identified during this reporting period. The joint oversight team will be assessing NCTC’s compliance with its minimization procedures in the next reporting period.

This passage has some good news, and some bad news.

The good news is that NCTC gets no unminimized collection, which CIA and FBI do. We have no idea what FBI’s minimization procedures  (which does the minimization before NCTC gets it) look like — though elsewhere this Assessment makes it clear that most initial distributions of data from FBI come with US person identity hidden. But at least most US person data will be protected when NCTC gets it.

The bad news is that this is a recent development. It probably post-dates 2011, as John Bates makes no mention of NCTC’s minimization procedures in his October 3, 2011. And the reference to the compliance team reviewing this in the next Assessment (which would cover December 2012 through May 2013) suggests the minimization procedures may be very recent. What has happened with this data in the past?

And explain to me how, if NCTC “may not” receive that US person data that has been referred to FBI because it is evidence of a non-terrorist crime, its minimization procedures explain what to do if they happen to discover such data in their possession. Perhaps the problem is in processing that takes place at FBI (in that such information isn’t adequately segregated), not at NCTC?

Remember, much of the analysis that happens at NCTC can affect US person’s lives, but (unlike much of FBI’s work) doesn’t get reviewed by a court. The data that gets to them might well be particularly sensitive.

The Google/Yahoo Problem: Fruit of the Poison MCT?

OK, this will be my last post (at least today) to attempt to understand why some Internet providers incurred so many costs associated with the response to the FISA Court’s October 3, 2011 decision that the government had improperly collected US person data as part of Multiple Communication Transactions.

For the moment, I’m going to bracket the question of whether Google and Yahoo are included in upstream providers (though I think it more likely for Google than Yahoo). Footnote 3 in the October 3 opinion seems to distinguish upstream collection from collection from Internet service providers. Though note the entirely redacted sentence in that footnote that may modify that easy distinction.

But let’s consider how the violative data might be used. We know from the conference call the I Cons had the other day (you can listen along here) that this is primarily about getting email inboxes.

An intelligence official who would not be identified publicly described the problem to reporters during a conference call on Wednesday.

“If you have a webmail email account, like Gmail or Hotmail, you know that if you open up your email program, you will get a screenshot of some number of emails that are sitting in your inbox, the official said.

“Those are all transmitted across the internet as one communication. For technological reasons, the NSA was not capable of breaking those down, and still is not capable, of breaking those down into their individual [email] components.”

If one of those emails contained a reference to a foreign person believed to be outside the US – in the subject line, the sender or the recipient, for instance – then the NSA would collect the entire screenshot “that’s popping up on your screen at the time,” the official continued.

Now, whether or not this collection comes from the telecoms or the Internet companies themselves, it effectively serves as an index of Internet communications deemed interesting based on the participants or because the email talks about an approved selector.

But it may be that this upstream collection serves primarily to identify which content the government wants to collect.

In his November 30, 2011 opinion, Bates emphasized (see page 10) the limits on what analysts could do with properly segregated upstream MCTs in the future.

An analyst seeking to use (e.g., in a FISA application, in an intelligence report, or in a Section 702 targeting decision) a discrete communication within an Internet transaction that contains multiple discrete communications must document each of the determinations. [my emphasis]

Then, the September 25, 2012 opinion describes how, using threats that he would declare the previous collection a crime under 1809(a)(2), which prohibits the “disclosure” of any information collected illegally, Judge John Bates got the government purge that previous collection and any reports generated from it.

The government informed the Court in October 2011 that although the amended NSA procedures do not by their terms apply to information acquired before October 31, NSA would apply portions of the procedures to the past upstream collection, including certain limitations on the use or disclosure of such information.

That effort, according to Bates, did not begin until “late in 2011.”

But here’s the thing: the government would have “disclosed” this information to email providers if it had used any of the violative MCTs to target emails in their custody — the Section 702 targeting decisions Bates was explicitly concerned about.

So presumably, once Bates made it clear he considered 1809 violations real problems in November 2011, the government would have had to modify any certifications authorizing collection on email addresses identified through the violative upstream collection (regardless of source).

I don’t yet understand why, in adjusting to a series of modified certifications, the providers would incur millions of dollars of costs. But I think expunging poison fruit targeting orders from the certifications would have taken some time and multiple changed certifications.

Update: Footnote 24 in the October 3, 2011 opinion provides more clarity on whether PRISM collection includes MCTs; it doesn’t.

In addition to its upstream collection, NSA acquires discrete Internet communications from Internet service providers such as [redacted] Aug. 16 Submission at 2; Aug. 30 Submission at 11; see also Sept. 7 2011 Hearing Tr. at 75-77. NSA refers to this non-upstream collection as its “PRISM collection.” Aug. 30 Submission at 11. The Court understands that NSA does not acquire Internet transactions” through its PRISM collection. See Aug Submission at 1.

NSA Has a Database Problem

Back in 2009 when the government released what we now know is a FISA Court of Review decision ordering Yahoo to cooperate in PRISM, I questioned a passage of the decision that relied on the government’s claim that it doesn’t keep a database of incidentally collected conversations involving US persons.

In this post, I just want to point to a passage that deserves more scrutiny:

The government assures us that it does not maintain a database of incidentally collected information from non-targeted United States persons, and there is no evidence to the contrary. On these facts, incidentally collected communications of non-targeted United States persons do not violate the Fourth Amendment.(26)

To translate, if the government collects information from a US citizen (here or abroad), a legal permanent US resident, a predominantly US organization, or a US corporation in the course of collecting information on someone it is specifically targeting, it it claims it does not keep that in a database (I’ll come back and parse this in a second). In other words, if the government has a tap on your local falafel joint because suspected terrorists live off their falafels, and you happen to call in a take out order, it does not that have in a database.

There are reasons to doubt this claim.

In the rest of the post, I showed how a response from Michaels Mukasey and McConnell to Russ Feingold’s efforts to protect US person incidental collection during the FISA Amendments Act had made it clear having access to this incidentally collected data was part of the point, meaning the government’s reassurances to the FISCR must have been delicate dodges in one way or another. (Feingold’s Amendments would have prevented 3 years of Fourth Amendment violative collection, by the way.)

Did the court ask only about a database consisting entirely of incidentally collected information? Did they ask whether the government keeps incidentally collected information in its existing databases (that is, it doesn’t have a database devoted solely to incidental data, but neither does it pull the incidental data out of its existing database)? Or, as bmaz reminds me below but that I originally omitted, is the government having one or more contractors maintain such a database? Or is the government, rather, using an expansive definition of targeting, suggesting that anyone who buys falafels from the same place that suspected terrorist does then, in turn, becomes targeted?

McConnell and Mukasey’s objections to Feingold’s amendments make sense only in a situation in which all this information gets dumped into a database that is exposed to data mining. So it’s hard to resolve their objections with this claim–as described by the FISA Appeals Court.

Which is part of the reason I’m so intrigued by this passage of John Bates’ October 3, 2011 decision ruling some of NSA’s collection and retention practices violated the Fourth Amendment. In a footnote amending a passage explaining why the retention of entirely US person communications with the permissive minimization procedures the government had proposed is a problem, Bates points back to that earlier comment.

The Court of Review plaining limited its holding regarding incidental collection to the facts before it. See In re Directives at 30 (“On these facts, incidentally collected communications of non-targeted United States persons do not violate the Fourth Amendment.” (emphasis added). The dispute in In re Directives involved the acquisition by NSA of discrete to/from communications from an Internet Service Provider, not NSA’s upstream collection of Internet transactions. Accordingly, the Court of Review had occasion to consider NSA’s acquisition of MCTs (or even “about” communications, for that matter). Furthermore, the Court of Review noted that “[t]he government assures us that it does not maintain a database of incidentally collected information from non-targeted United States persons, and there is no evidence to the contrary.” Id. Here, however, the government proposes measures that will allow NSA to retain non-target United States person information in its databases for at least five years.

Ultimately, Bates’ approval for the government to query on US person identifiers on existing incidentally collected Section 702 material (see pages 22-23) show that he hasn’t really thought through what happens to US person incidental collection; he actually has a shocking (arguably mis-) understanding of how permissive the existing minimization rules are, and therefore how invasive his authorization for searching on incidentally collected information will actually be.

But his complaint with the proposed minimization procedures shows what he believes they should be.

The measures proposed by the government for MCTs, however, largely dispense with the requirement of prompt disposition upon initial review by an analyst. Rather than attempting to identify and segregate information “not relevant to the authorized purpose of the acquisition” or to destroy such information promptly following acquisition, NSA’s proposed handling of MCTs tends to maximize the retention of such information, including information of or concerning United States persons with no direct connection to any target.

As Bates tells it, so long as he’s paying close attention to an issue, the government should ideally destroy any US person data it collects that is not relevant to the authorized purpose of the acquisition. (His suggestion to segregate it actually endorses Russ Feingold’s fix from 2008.)

But the minimization rules clearly allow the government to keep such data (after this opinion, they made an exception only for the multiple communication transactions in question, but not even for the other search identifiers involving entirely domestic communication so long as that’s the only communication in the packet).

All the government has to do, for the vast majority of the data it collects, is say it might have a foreign intelligence or crime or encryption or technical data or threat to property purpose, and it keeps it for 5 years.

In a database.

Back when the FISCR used this language, it allowed the government the dodge that, so long as it didn’t have a database dedicated to solely US person communications incidentally, it was all good. But the language Bates used should make all the US person information sitting in databases for 5 year periods (which Bates seems not to understand) problematic.

Not least, the phone dragnet database, which — after all — includes the records of 310 million people even while only 12 people’s data has proved useful in thwarting terrorist plots.

Update: Fixed the last sentence to describe what the Section 215 dragnet has yielded so far.

NSA’s “Presumption of Regularity”

As you’ve probably heard, the most striking part of the October 3, 2011 FISA opinion finding NSA’s collection violated the Fourth Amendment is Footnote 14.

The Court is troubled that the government’s revelations regarding NSA’s acquisition of Internet transactions mark the third instance in less than three years in which the government has disclosed a substantial misrepresentation regarding the scope of a major collection program.

In March, 2009, the Court concluded that its authorization of NSA’s bulk acquisition of telephone call detail records from [redacted] in the so-called “big business records” matter “ha[d] been premised on a flawed description of how the NSA uses [the acquired] metadata,” and that “[t]his misperception by the FISC existed from the inception of its authorized collection in May 2006, buttressed by repeated inaccurate statements made in the government’s submissions, and despite a government-devised and Court-mandated oversight regime.” Docket [redacted] Contrary to the governent’s repeated assurances, NSA had been routinely running queries of the metadata using querying terms that did not meet the required standard for querying. The Court concluded that this requirement had been “so frequently and systematically violated that it can fairly be said that this critical element of the overall … regime has never functioned effectively.” Id.

Two more entirely redacted substantial misrepresentations follow.

Footnote 32 reveals how, after NSA did a review of the communications the FISC ultimately found to violate the Fourth Amendment, the FISC caught it in downplaying the number of affected communications. After it sent the NSA back to new analysis, the problem grew from 2,000 to 10,000 a year to 48,000 to 56,000 a year. I guess the FISC found, like I have, that you can’t trust the biggest math organization in the world to do basic math.

Yet in spite of the fact that this opinion lists three substantial misrepresentations the NSA had made in recent history and caught the NSA in bad math, here’s how it decided it could trust the government’s assurances that it didn’t use this abusive communication to target non-targeted people.

Therefore, the Court has no reason to believe that NSA, by acquiring the Internet transactions containing multiple communications, is targeting anyone other than the user of the selected tasked selector. See United States v. Chemical Found., Inc., 272 U.S. 1, 14-15 (1926) (“The presumption of regularity supports the official acts of public officers, and, in the absence of clear evidence to the contrary, courts presume that they have properly discharged their official duties.”).

I’m not surprised FISC invoked this (especially not surprised that John Bates, who can be very deferential, did). It is the law.

But (as the case of Adnan Latif showed) we keep extending the presumption of regularity to the government in spite of abundant evidence we shouldn’t.

Targeted Killing Timeline

A timeline!

I’ve been working on this timeline for almost nine months, trying to pull together the known dates about strikes against Americans, the evidence supporting the strike against Anwar al-Awlaki, the legal cases surrounding both targeted killing and torture, to which targeted killing is linked via the Memorandum of Notification, and Congressional efforts to exercise oversight.

September 17, 2001: George Bush signs Memorandum of Notification (henceforth, Gloves Come Off MON) authorizing a range of counterterrorism techniques, including torture and targeted killing.

September 18, 2001: Congress passes the Authorization to Use Military Force.

November 3, 2002: US citizen Kamal Derwish killed in drone purportedly targeting Abu Ali al-Harithi.

Late 2008: Ruben Shumpert reported killed in Somalia.

June 24, 2009: Leon Panetta gets briefed on assassination squad program.

June 26, 2009: HPSCI passes a funding authorization report expanding the Gang of Eight briefings.

July 8, 2009: The Administration responds with an insulting appeal to a “fundamental compact” between Congress and the President on intelligence matters.

July 8, 2009: Silvestre Reyes announces CIA lied to Congress.

October 26, 2009: British High Court first orders British government to release language on Binyam Mohamed’s treatment.

October 28, 2009: FBI kills Imam Luqman Asmeen Abdullah during Dearborn, MI arrest raid.

October 29, 2009: Hearing on declassifying mention of Gloves Come Off MON before Judge Alvin Hellerstein; in it, Hellerstein reveals NSA James Jones has submitted declaration to keep mention of MON secret.

November 5, 2009: Nidal Hasan attacks Fort Hood, killing 13.

December 24, 2009: JSOC tries but fails to hit Anwar al-Awlaki. On that day, the IC did not yet believe him to be operational.

December 25, 2009: With Umar Farouk Abdulmutallab attack, FBI develops full understanding of Awlaki’s operational goals.

January 2, 2010: In conversation with David Petraeus, Yemeni President Ali Abdullah Saleh http://www.cablegatesearch.net/cable.php?id=10SANAA4“>speaks as if Awlaki, whom he refers to as a cleric, not an AQAP member, was a designated target of December 24 attack.

Read more

Lots of Senior Officials Spilling State Secrets Today

Last year, Director of National Intelligence James Clapper said the following:

I am asserting privilege over classified intelligence information, assessments, and analysis prepared, obtained, or under the control of any entity within the U.S. Intelligence Community concerning al-Qaeda, AQAP or Anwar al-Aulaqi that may be implicated by [Awlaki’s father’s attempt to sue for information about why Awlaki was on the CIA’s assassination list]. This includes information that relates to the terrorist threat posed by Anwar al-Aulaqi, including information related to whether this threat may be “concrete,” “specific,” or “imminent.”

Then Secretary of Defense Robert Gates said the following:

DOD cannot reveal to a foreign terrorist organization or its leaders what it knows about their activities and how it obtained that information.

[snip]

The disclosure of any operational information concerning actions U.S. armed forces have or may plan to take against a terrorist organization overseas would risk serious harm to national security and foreign relations. Official confirmation or denial of any operations could tend to reveal information concerning operational capabilities that could be used by adversaries to evade or counter any future strikes.

[snip]

Finally, as discussed below, public confirmation or denial of either prior or planned operations could seriously harm U.S. foreign relations.

[snip]

The disclosure of information concerning cooperation between the United States and a foreign state, and specifically regarding any possible military operations in that foreign country, could lead to serious harm to national security, including by disrupting any confidential relations with a foreign government. [my emphasis]

Then CIA Director and current Secretary of Defense Leon Panetta said the following:

I am invoking the [state secrets] privilege over any information, if it exists, that would tend to confirm or deny any allegations in the Complaint [about CIA targeting Awlaki for assassination] pertaining to the CIA.

Yet in spite of the fact that these top government officials swore to a judge that revealing operational details about the CIA’s assassination operations, US counterterrorist cooperation with Yemen, and confirmation of prior or planned military operations would harm foreign relations and national security, we’re seeing details like this in reporting on Anwar al-Awlaki’s death:

An American-born cleric killed in Yemen played a “significant operational role” in plotting and inspiring attacks on the United States, U.S. officials said Friday, as they disclosed detailed intelligence to justify the killing of a U.S. citizen.

Anwar al-Awlaki, an American-born radical Islamic preacher who rose to the highest level of al Qaeda’s franchise in Yemen, was killed in a CIA-directed strike upon his convoy, carried out with the U.S. Joint Special Operations Command’s firepower, according to a counterterrorist official, speaking on condition of anonymity to discuss intelligence.

[snip]

Four individuals were killed in Friday’s attack, according to U.S. officials.

[snip]

Al-Awlaki had been under observation for three weeks while they waited for the right opportunity to strike, one U.S. official said.

[snip]

U.S. counterterrorism officials said that counterterrorism cooperation between the U.S. and Yemen has improved in recent weeks, allowing the U.S. to gather better intelligence on al-Awlaki’s movements. The ability to better track him was a key factor the successful strike, U.S. officials said.

Or details like this, including John Brennan’s comments on the record:

Fox News has learned that two Predator drones hovering above al-Awlaki’s convoy fired the Hellfire missiles which killed the terror leader. According to a senior U.S. official, the operation was carried out by Joint Special Operations Command, under the direction of the CIA.

[snip]

But American sources confirmed the CIA and U.S. military were behind the strike on al-Awlaki, whom one official described as a “big fish.”

The strike hit a vehicle with three or four suspected Al Qaeda members inside, in addition to al-Awlaki. According to a U.S. senior official, the other American militant killed in the strike was Samir Khan, the co-editor of an English-language Al Qaeda web magazine called “Inspire.”

[snip]

Top U.S. counter terrorism adviser John Brennan says such cooperation with Yemen has improved since the political unrest there. Brennan said the Yemenis have been more willing to share information about the location of Al Qaeda targets, as a way to fight the Yemeni branch challenging them for power. Other U.S. officials say the Yemenis have also allowed the U.S. to fly more armed drone and aircraft missions over its territory than ever previously, trying to use U.S. military power to stay in power. [my emphasis]

Judge Bates, if I were you, I’d haul Clapper, Gates, and Panetta into your courtroom to find out whether they lied their ass off to you last year so as to deprive a US citizen of due process, and if they didn’t, then how long it will be until John Brennan and some other counterterrorism officials get charged with Espionage.

As Expected, Judge Bates Punts on Rule of Law

I almost felt like I was reading Judge John Bates’ ruling on whether or not Valerie Plame could sue those who outed her when I read Judge Bates’ ruling dismissing the suit challenging the government’s ability to assassinate Anwar al-Awlaki with no due process.

He starts by admitting the importance of the issues at hand.

This is a unique and extraordinary case. Both the threshold and merits issues present fundamental questions of separation of powers involving the proper role of the courts in our constitutional structure. Leading Supreme Court decisions from Marbury v. Madison, 5 U.S. (1 Cranch) 137 (1803), through Justice Jackson’s celebrated concurrence in Youngstown Sheet & Tube Co. v. Sawyer, 343 U.S. 579 (1952), to the more recent cases dealing with Guantanamo detainees have been invoked to guide this Court’s deliberations. Vital considerations of national security and of military and foreign affairs (and hence potentially of state secrets) are at play.

Stark, and perplexing, questions readily come to mind, including the following: How is it that judicial approval is required when the United States decides to target a U.S. citizen overseas for electronic surveillance, but that, according to defendants, judicial scrutiny is prohibited when the United States decides to target a U.S. citizen overseas for death? Can a U.S. citizen — himself or through another — use the U.S. judicial system to vindicate his constitutional rights while simultaneously evading U.S. law enforcement authorities, calling for “jihad against the West,” and engaging in operational planning for an organization that has already carried out numerous terrorist attacks against the United States? Can the Executive order the assassination of a U.S. citizen without first affording him any form of judicial process whatsoever, based on the mere assertion that he is a dangerous member of a terrorist organization? How can the

courts, as plaintiff proposes, make real-time assessments of the nature and severity of alleged threats to national security, determine the imminence of those threats, weigh the benefits and costs of possible diplomatic and military responses, and ultimately decide whether, and under what circumstances, the use of military force against such threats is justified? When would it ever make sense for the United States to disclose in advance to the “target” of contemplated military action the precise standards under which it will take that military action? And how does the evolving AQAP relate to core al Qaeda for purposes of assessing the legality of targeting AQAP (or its principals) under the September 18, 2001 Authorization for the Use of Military Force?

But then he punts entirely on standing grounds.

Although these threshold questions of jurisdiction may seem less significant than the questions posed by the merits of plaintiff’s claims, “[m]uch more than legal niceties are at stake here” — the “constitutional elements of jurisdiction are an essential ingredient of separation and equilibration of powers, restraining the courts from acting at certain times, and even restraining them from acting permanently regarding certain subjects.”

[snip]

Because these questions of justiciability require dismissal of this case at the outset, the serious issues regarding the merits of the alleged authorization of the targeted killing of a U.S. citizen overseas must await another day or another (non-judicial) forum.

But just for good measure, Bates says he would rule in the government’s favor on state secrets, but doesn’t need to.

So, too, defendants have established that the three procedural requirements for invocation of the state secrets privilege — (1) a formal claim of privilege (2) by an appropriate department head (3) after personal consideration — have been satisfied here. See Reynolds, 345 U.S. at 7-8; Jeppesen Dataplan, 614 F.3d at 1080; Defs.’ Mem. at 48-50.[snip]

Under the circumstances, and particularly given both the extraordinary nature of this case and the other clear grounds for resolving it, the Court will not reach defendants’ state secrets privilege claim. That is consistent with the request of the Executive Branch and with the law, and plaintiff does not contest that approach. Indeed, given the nature of the state secrets assessment here based on careful judicial review of classified submissions to which neither plaintiff nor his counsel have access, there is little that plaintiff can offer with respect to this issue.17 But in any event, because plaintiff lacks standing and his claims are non-justiciable, and because the state secrets privilege should not be invoked “more often or extensively than necessary,” see Jeppesen Dataplan, 614 F.3d at 1080, this Court will not reach defendants’ invocation of the state secrets privilege.

It was nice of Bates to save the Obama Administration the embarrassment of invoking state secrets to hide the logic for its tyranny.

All in all, a tremendous victory for unchecked executive powers!

Read more