10 Years Later, Information Asymmetry Could Launch Another War

Ten years ago, the Bush Administration was planning the last details of the new product announcement it would roll out in September, a new product announcement that would lead to an expensive, illegal war that killed hundreds of thousands of Iraqis.

A key part of that product rollout was the manipulation of information asymmetry: the leaking of out-of-context classified information to Judy Miller. After she published it on the front page of the NYT, the warmongers pointed back to it as the complete truth. Yet because the information was classified–because it was illegal for experts to counter the claims made by Judy’s sources–the other side barely came out. It wasn’t until well into the war that enough of the Iraq NIE was declassified to reveal that the warmongers had presented a completely imbalanced picture of Iraq’s WMD program and that dissenters had rightly debunked some of the warmongers claims.

Which is worth remembering as you read this piece from Jeffrey Lewis (of ArmsControlWonk fame). While I think Jim would have issue with some of the claims Lewis makes on technical grounds, but Lewis addresses recent Israeli claims about new intelligence on Iran’s nuke program to argue for reading NIEs and other WMD intelligence with some nuance (you can click through to read his nuanced take, both on the 2007 Iran NIE and the purportedly new piece of intelligence). But one of several reasons why we’re not getting that nuance, Lewis argues, is because Congress and others are cracking down on responsible, nuanced communication.

Unfortunately, the White House’s concerted campaign to criminalize national security discourse has prevented officials from discussing the estimate with journalists, allowing the most alarmist conjecture to dominate public debate.

Among other things, DiFi has proposed curtailing background briefings that could provide the kind of nuanced reading Lewis speculates at here. In addition, DOD has reportedly made a top secret request for staffers to identify whether they’ve spoken with one of the journalists who has covered this issue most closely (for better and worse), David Sanger.

In short, even assuming the leak witch hunts are in good faith, they may well bring us to war just as surely as the leaks to Judy Miller did a decade ago.

Apparently, we haven’t even figured out how to avoid being snookered into war by A1 cutouts.

On the Press Release Sanctions against Hezbollah

I have never doubted that Hezbollah and/or Iran could be behind the attack in Israeli tourists in Burgas, Bulgaria. Certainly, it is one of the few attacks blamed on one or the other in the last year that exhibited the competence we expect from Hezbollah.

That said, I’ve been struck by the vary careful insistence on the part of both Dianne Feinstein and John Brennan that they have seen no proof to link Hezbollah or Iran to the attack.

Israeli intelligence sources claiming to protect the very secret intelligence they are leaking have offered this claim as evidence.

Israeli intelligence has evidence of many telephone calls between Lebanon and Burgas in the two months before the bombing, according to a senior government official who spoke on the condition of anonymity because the information is classified, with the volume intensifying in the three days leading up to it.

But they are no more prepared to expose the details of their counterintelligence work publicly than the attackers are to claim responsibility. “We know the sources in Lebanon,” though not the identity of those on the other end in Bulgaria, the official said. “They shouldn’t know that we know the numbers in Lebanon.”

Nevertheless, in spite of the fact that it was otherwise sourced to press reports, this laughable press conference announcing the What’s-Old-Is-New sanctions against Hezbollah on Friday made no mention of the new claim; it discussed the ties between Hezbollah and Burgas this way:

And we are working to assess the facts and with our partners to discover who was responsible. And although the investigation continues, and we are not in a position to make a statement about responsibility, the attack does resemble Hezbollah’s plotting earlier this year.

They didn’t mention the calls–or even the A1 cutout report of the calls–at all.

Which is notable given that at least four journalists at the press conference asked what was new behind the sanctions on Hezbollah. Josh Rogin summarizes the absurdity of imposing sanctions on a group that is already under sanctions that have the same effect.

The Cable asked both officials if designating Hezbollah for sanctions, which freezes the group’s U.S.-based assets and bars Americans from doing business with Hezbollah, has any added concrete effect if done twice. They said the added effect is in the court of public opinion.

“It will put the group in a more difficult situation, and, I think, will make them think long and hard before they continue this campaign in which the Syrian people are being brutalized. So we do see very concrete benefits coming from this designation,” said Benjamin. “Whether they will be in the area of financial sanctions or not remains to be seen, but in terms of casting a bright light on what the group is doing, I think that’s vitally important.”

So the Treasury Department doesn’t have to actually do anything to enforce the new designation it wasn’t doing already, and Hezbollah doesn’t feel any additional direct pain.

In any case, this is what we’ve come to. Treasury Under Secretary for Terrorism and Financial Intelligence David Cohen admits that these sanctions are about exposing a purportedly new role from a terrorist organization that has pretty much played the role of supporting Syria for decades.

But the purpose of our designations, whether it’s the Hezbollah action today or any of our other designations under our authorities, is not solely focused on the immediate financial impact, but as Ambassador Benjamin just expressed, to expose the activity of the party that is being designated for the conduct that has led to the designation.

And yet–even as Adam Entous refuted the government’s claims based on WSJ’s reporting–the government refuses to offer no more than press reports.

I really can’t give you any greater detail than what we’ve put forward in the press release and in my statement this afternoon about the activities of Hezbollah in Syria.

[snip]

This is not a matter of idle speculation or press reports.

[snip]

I was just going to say, look, we’re obviously very sensitive here to issues of sources and methods and we’re not going to divulge anything that shouldn’t be divulged.

[snip]

I think we have put out as much detail as we are able to put out with respect to Hezbollah’s activity in Syria.

Our war by vacuous press release, all justified in the guise of protecting sources and methods, is rapidly losing all credibility.

It feels like the Iraq War campaign again.

Another Breach of Contractor-Protected Critical Infrastructure

In my never-ending campaign to document all the ways the private sector is a bigger risk to our critical infrastructure than terrorists, hackers, political activists, or average citizens, take a look at the job Raytheon’s $100 million security system for JFK Airport has done.

Daniel Casillo, 31, was able to swim up to and enter the airport grounds on Friday night, past an intricate system of motion sensors and closed-circuit cameras designed to to safeguard against terrorists, authorities said.

[snip]

“We have called for an expedited review of the incident and a complete investigation to determine how Raytheon’s perimeter intrusion detection system-which exceeds federal requirements-could be improved. Our goal is to keep the region’s airports safe and secure at all times,” the Port Authority said in a statement.

This comes just weeks after an 82 year old peace activist was able to breach the security provided by failed Olympic security contractor G4S. In response to that failure, POGO is calling out Energy Secretary Steven Chu for his history of outsourcing to poorly-overseen contractors.

Energy Secretary Steven Chu said in a statement provided to the Knoxville News Sentinel on Monday: “The department has no tolerance for security breaches at any of our sites, and I am committed to ensure that those responsible will be held accountable.” But there is no denying that Y-12 [the actual part of Oak Ridge breached] was a giant failure of federal oversight. Now the people being axed are lower-level employees rather than those who have allowed the security standards to fall far below acceptable levels, such as Secretary Chu, himself.

Secretary Chu should be the first on the chopping block. He has been preaching for years that government overseers should get off the back of the contractors and everything will be fine. Then, of course, he is shocked when Y-12 is successfully attacked by an 82-year-old nun.

After only one year in the position, Secretary Chu’s deputy secretary, Daniel B Poneman, sent a memorandum (PDF) to the department with a safety and security reform plan aimed at curtailing pesky government oversight. “Contractors are provided the flexibility to tailor and implement safety programs in light of their situation without excessive Federal oversight or overly prescriptive Departmental requirements,” the memo said.

It should be clear by now that the current culture at DOE and its semiautonomous National Nuclear Security Administration (NNSA) is to take their orders from contractors and provide little or no oversight. Read more

I’m Confused. Are THESE Leaks Permissible, or Not?

As you read this Reuters story, remember that the House voted to mandate investigations into leaks that undermined Israel’s case for war against Iran and that the biggest new news in David Sanger’s reporting on StuxNet is that Joe Biden and others believed the Israelis set StuxNet free of Natanz. Leaks that inconvenience Israel’s hawks, you see, are bad, even if they serve US interests.

The Reuters story is a response to two reports in Ha’aretz yesterday that a new NIE–or maybe not an NIE but a top intelligence report–says Iran is closer to developing nukes than the US previously believed.

Defense Minister Ehud Barak confirmed on Thursday Haaretz’s report that President Barack Obama recently received a new National Intelligence Estimate report on the Iranian nuclear program, which shares Israel’s view that Iran has made significant progress toward military nuclear capability, and said that the report has raised the urgency of the issue.

Speaking on Israel Radio on Thursday morning, Barak said that there is a U.S. intelligence report “being passed around senior offices,” and that, as far as Israel knows, this report has brought the U.S. position over Iran closer to the Israeli position, and made the issue more urgent.

[snip]

Haaretz reported on Thursday that the National Intelligence Estimate report on Iran was supposed to have been submitted to Obama a few weeks ago, but it was revised to include new and alarming intelligence information about military components of Iran’s nuclear program. Haaretz has learned that the report’s conclusions are quite similar to those drawn by Israel’s intelligence community.

Not a single member of Congress called for a witch hunt into who leaked the NIE–or maybe not an NIE but a top intelligence report–to Israel and/or Ha’aretz.

Apparently, it’s okay to leak intelligence to Israel if it helps build a case (just in time to roll out a new product in September, I’ll note) for war, but not if it hampers Israel’s efforts to gin up a war. Is that the rule?

If so, what about this Reuters story?

In it, we have anonymous sources back in full force, refuting (sort of) those reports. Note the sourcing.

The United States still believes that Iran is not on the verge of having a nuclear weapon and that Tehran has not made a decision to pursue one, U.S. officials said on Thursday.

[snip]

But a White House National Security Council spokesman disputed the Israeli reports, saying the U.S. intelligence assessment of Iran’s nuclear activities had not changed since intelligence officials delivered testimony to Congress on the issue earlier this year.

“We believe that there is time and space to continue to pursue a diplomatic path, backed by growing international pressure on the Iranian government,” the spokesman said. “We continue to assess that Iran is not on the verge of achieving a nuclear weapon.”

[snip]

Another U.S. official said the United States regularly exchanges intelligence reporting with its allies, which would include Israel.

Apparently, Tommy Vietor (or someone sitting next to him) felt obliged to refute the reports, but would not do so on the record, not even to back his two sentence quote in the Reuters report. It’s okay for Ehud Barak, who was fed this intelligence either in normal intelligence sharing or alternately just handed the US the report in question and now is claiming that the report has been incorporated into the NIE (says a US official who seems determined to provide some explanation for this leak), to talk about leaked US intelligence on the record, but it’s not okay for the NSC spokesperson to do so.

It’s a new twist on the A1 cutout Dick Cheney used, I’m fairly certain: launder the leak through leaks to Israel, because no one in Congress or DC generally (except the FBI) gives a damn about leaks to Israel.

Whatever. I’m thoroughly confused. Am I right that the leak to Israel is considered acceptable but now the sources for the Reuters report will be targets of a witch hunt?

NGOs to Congress: Don’t Hide Our Secret Government

I noted last week that the Senate Intelligence Committee had acceded to Director of National Intelligence James Clapper’s request that it repeal the requirement that his office produce a yearly report on the number of people with security clearances.

On Tuesday a group of NGOs wrote the Intelligence Committees asking they reverse course and retain the report requirement. They argue, in part, that the report has generated far more attention than typical government reports. And that the report offered the public an unprecedented understanding of the size of the clearance community.

We believe the annual report on security clearances provides exceptional value to the public and should continue to be published.
In the two years that the report has been produced, it has dramatically altered our conception of the size and scale of the personnel security clearance system. Prior to the reporting requirement, the Government Accountability Office could only estimate the number of security cleared personnel, and its latest estimate was low by more than a million clearances.
As evidence of the exceptional public interest in this report, we note that the findings of the latest annual report have appeared in the New York Times (July 24), the Washington Post (July 28), and McClatchy Papers (July 27), among others. As you know, this level of attention is well above average for a report to Congress on any topic.
Through this annual reporting requirement, your Committees have provided an unprecedented degree of transparency concerning the security clearance system. We thank you for that, and we respectfully request that you maintain this important reporting requirement.

Let’s hope that bit of flattery at the end works. If not, I guess we can conclude that even this tiny bit of transparency on our secret government is deemed too much for mere citizens to have.

It’s Not Just Whether Nidal Hasan’s Emails Stuck Out, It’s Whether Abdulmutallab’s Did

I’ve been meaning to return to the Webster report on Nidal Hasan’s conversations with Anwar al-Awlaki. This conversation between Gunpowder & Lead and Intelwire about how alarming those emails were will be a start provides a good place to start.

Hasan’s emails should have raised more concern–but probably didn’t because of the sheer volume of Awlaki intercepts

G&L notes that certain details from the emails–such as his invocation of Hasan Akbar, a Muslim-American soldier who killed two officers in Kuwait–as an example that should have raised more concern than it did.

But more significant, his question to Awlaki didn’t actually deal with the valid question that he raised, the feeling of inner conflict between one’s faith and serving in the U.S. military. Instead, he leaped right to a question that should rightly trigger alarm: if Hasan Akbar died while attacking fellow soldiers, would he be a martyr? Hasan skipped over questions about whether serving in the U.S. military is religiously acceptable; whether going to war against fellow Muslims is a violation of religious principles. Instead, in addressing “some” soldiers who felt conflicted about fighting fellow Muslims, Hasan right away asked whether it was permissible to kill other U.S. soldiers in the way Hasan Akbar.

After a close analysis of a number of the emails, G&L refutes the representation of these emails as “fairly benign.”

I agree with that assessment (and would add that the suggestion, in a February 22, 2009 email, that Hasan was donating to entities that his mosque would not is another troubling detail). But I also agree with Intelwire. These emails, from an Army officer, surely merited more attention. But these emails, as they likely appeared among the stream of Anwar al-Awlaki communications, probably did not stick out.

Based on who Hasan was (a military officer), who he was talking to (a suspected 9/11 accomplice), and the fact he repeatedly tried to get Awlaki’s attention using a variety of stratagems, the case should have been escalated and Hasan’s superiors should have been informed.

But when you place the content of Hasan’s messages alongside all the other raw intelligence that counterterrorism investigations generate, it’s extremely hard to argue from a subjective, non-psychoanalytical reading that they represented a red flag.

Which is why this report has seemed poorly scoped to me. Because not only did Nidal Hasan’s emails fail to trigger further attention, but Umar Farouk Abdulmutallab’s contacts with Awlaki before Fort Hood did too.

In spite of the fact that the FBI had two people spending a significant chunk of each day (they claimed it took 40% or 3 hours of their work day; 88) reviewing communications tied to Awlaki, in spite of the fact that two men about to attack the US were in contact with Awlaki, “the FBI’s full understanding of Aulaqi’s operational ambitions developed only after the attempted bombing of Northwest Airlines Flight 253 on Christmas Day 2009.” (72)

The government also failed to respond to Abdulmutallab intercepts leading up to the Fort Hood attack

Consider: according to the report itself, Robert Mueller formally asked William Webster to conduct this inquiry on December 17, 2009 (though Webster’s appointment was reported over a week before then). Just 8 days later, another terrorist who had been in contact with Awlaki struck the US. Just 5 days after that, sources started leaking details of NSA intercepts from 4 months earlier (so around August) that might have warned about the attack.

Intelligence intercepts from Yemen beginning in early August, when Abdulmutallab arrived in that country, contained “bits and pieces about where he was, what his plans were, what he was telling people his plans were,” as well as information about planning by the al-Qaeda branch in Yemen, a senior administration official said. “At first blush, not all these things appear to be related” to the 23-year-old Nigerian and the bombing attempt, he said, “but we believe they were.”

It’s unclear how many of these intercepts were directly between Abdulmutallab and Awlaki, and therefore presumably reviewed by the FBI team in San Diego. But at least according to the sentencing materials submitted in the Abdulmutallab case (there are reasons to treat this with a bit of skepticism), there were substantive communications between Awlaki and Abdulmutallab.

Defendant provided this individual [who offered to connect him with Awlaki] with the number for his Yemeni cellular telephone. Thereafter, defendant received a text message from Awlaki telling defendant to call him, which defendant did. Read more

Tony Bologna, John Pike, and Stop and Frisk: A Bad Couple of Days for Abusive Cops

In a move that might make cops think twice before they go nuts on kettled protestors, NYC has decided not to defend Anthony Bologna, the officer filmed spraying defenseless protestors with pepper spray in NY.

New York City has distanced itself from a high-ranking police official accused of firing pepper spray at Occupy Wall Street protesters, taking the unusual step of declining to defend him in a civil lawsuit over the incident.

The decision means Deputy Inspector Anthony Bologna also could be personally liable for financial damages that may arise out of the suit, said lawyers familiar with similar civil-rights claims.

Because Bologna accepted the findings of an internal investigation finding him in violation of department guidelines, it appears, the city has space to say pepper-spraying docile protestors is not his job.

In even better news, John Pike–the UC Davis cop filmed spraying peaceful protestors with pepper spray–got fired, in spite of an internal review finding he acted reasonably.

The police chief at the University of California, Davis overruled an internal affairs panel’s recommendation and fired a lieutenant who soaked demonstrators with pepper spray — an incident that sparked protests after it was recorded and posted online, according to documents obtained by a McClatchy-Tribune newspaper.

The Sacramento Bee (http://sacb.ee/MABZrq ) reports that investigators concluded Lt. John Pike acted reasonably during the Nov. 18 campus protest and should face demotion or suspension at worst.

But police Chief Matthew Carmichael rejected those findings and wrote Pike on April 27 that he planned to fire him. Pike, 39, was fired Tuesday, according to the Bee.

“The needs of the department do not justify your continued employment,” Carmichael wrote in a letter to Pike, according to the documents, which included the internal affairs investigation report.

I’m curious about the delay between the time Carmichael decided to fire Pike and the time it was official, Tuesday. Hopefully, that time was spent insulating the university against suit.

Finally, there are preliminary reports that the number of stop and frisks in NYC have dropped significantly as the sheer scale of the abusive practice has become clear.

Officers conducted about 134,000 stop-and-frisks between April 1 and June 30, down from more than 200,000 during the first three months of the year.

That’s still too many. But sunshine and embarrassment seems to be making progress there, too.

Update: In related news, the 2004 RNC protestors suing for false arrest and other abuses just won class action status.

Nuke Site Breached Just Days After SSCI Moved to Eliminate Reporting on Nuke Site Security

I have been dawdling about writing this post, in which I explain that two of the reporting requirements the Senate Intelligence Committee rather stupidly, IMO, moved to eliminate last week pertain to the security of our nuclear labs.

Back when I criticized the plan to eliminate these reports in June, I wrote,

The bill would eliminate two reporting requirements imposed in the wake of the Wen Ho Lee scandal: that the President report on how the government is defending against Chinese spying and that the Secretary of Energy report on the security of the nation’s nuclear labs. Just last year, the Oak Ridge National Laboratory had to separate from the Internet because some entity–China would be a good candidate–had hacked the lab and was downloading data from their servers. Now seems a really stupid time to stop reporting on efforts to avoid such breaches.

In spite of these very obvious reasons, the Senate did indeed eliminate two reporting requirements pertaining to national labs (though they kept the one pertaining to Chinese spying).

(7) REPEAL OF REPORTING REQUIREMENT REGARDING COUNTERINTELLIGENCE AND SECURITY PRACTICES AT THE NATIONAL LABORATORIES.—Section 4507 of the Atomic Energy Defense Act (50 U.S.C. 2658) is repealed.

(8) REPEAL OF REPORTING REQUIREMENT REGARDING SECURITY VULNERABILITIES OF NATIONAL LABORATORY COMPUTERS.—Section 4508 of the Atomic Energy Defense Act (50 U.S.C. 2659) is repealed.

I’m glad I waited. Now I can use this story to demonstrate how vulnerable our nuclear labs remain.

The U.S. government’s only facility for handling, processing and storing weapons-grade uranium [Oak Ridge National Lab] was temporarily shut this week after anti-nuclear activists, including an 82-year-old nun, breached security fences, government officials said on Thursday.

[snip]

The activists painted slogans and threw what they said was human blood on the wall of the facility, one of numerous buildings in the facility known by the code name Y-12 that it was given during World War II, officials said.

While moving between the perimeter fences, the activists triggered sensors which alerted security personnel. However, officials conceded that the intruders still were able to reach the building’s walls before security personnel got to them.

When James Clapper’s office asked to throw these reports out, they justified it by saying they could just brief the information rather than report it regularly.

This reporting requirement should be repealed because it is over a decade old and the Secretary of Energy and the National Counterintelligence Executive can provide the information requested through briefings, as requested, if congressional interest persists.

Oak Ridge Lab has been breached twice in two years, once via its computer systems and now physically. I’m sure Congress will be getting a slew of briefings about the lab, but it really does seem like a little reporting requirement might help DOE to take this seriously.

“Dear John Brennan: You’re Being Investigated”

A number of people have pointed to Scott Shane’s story on the leak witch hunt for the details it gives on the increasing concern about leak witch hunts among journalists and national security experts.

But this paragraph includes the most interesting news in the article.

The F.B.I. appears to be focused on recent media disclosures on American cyberattacks on Iran, a terrorist plot in Yemen that was foiled by a double agent and the so-called “kill list” of terrorist suspects approved for drone strikes, some of those interviewed have told colleagues. The reports, which set off a furor in Congress, were published by The New York Times, The Associated Press, Newsweek and other outlets, as well as in recent books by reporters for Newsweek and The Times. [my emphasis]

That’s because prior reporting had indicated that the Kill List stories were not being investigated.

Recent revelations about clandestine U.S. drone campaigns against al Qaeda and other militants are not part of two major leak investigations being conducted by federal prosecutors, sources familiar with the inquiries said.

[snip]

The CIA has not filed a “crime report” with the Justice Department over reports about Obama’s drone policy and a U.S. “kill list” of targeted militants, an action which often would trigger an official leak investigation, two sources familiar with the matter said. They

So Shane’s revelation that the Kill List stories are being investigated amounts to the author of one of the Kill List stories reporting that some people who have been interviewed by the FBI told colleagues they got asked about the Kill List. Which might go something like, “Scott, they’re asking about your story, too.”

All without Shane acknowledging that Shane wrote one of the main Kill List Shiny Object stories.

Meanwhile, I find his reference to the outlets involved very interesting. Using the principle of parallelism, the passage seems to suggest the FBI is investigating the NYT for David Sanger’s sources on StuxNet, the AP for Adam Goldman and Matt Apuzzo’s sources on the UndieBomb 2.0 plot, and Newsweek for Daniel Klaidman’s sources on the Kill List. But of course the NYT also wrote a Kill List story, the AP wrote what is probably the most interesting Kill List story (which reported that the Kill List is now run by John Brennan). “And other outlets.” Which might include ABC for revealing that the UndieBomb 2.0 plotter was actually an infiltrator (ABC got the story indirectly from John Brennan, though Richard Clarke). Or the WaPo for Greg Miller’s original story on drone targeting, revealing that we were going to use signature strikes in Yemen. Or the WSJ, reporting that we had started using signature strikes.

In other words, it presents a rather interesting group of potential stories and sources.

Now I don’t know that John Brennan was the source for all this or that he’s really being investigated. I’m not saying Shane is being manipulative by reporting on this (though seriously, it’s another example of the NYT having a reporter report on a story that he is really a part of).

But I do find it rather interesting that a reporter targeted in this leak witch hunt just made news about the scope of the leak witch hunt.

Lost Among the Findings in Syria

The Neocons have been pressuring Obama to do something in Syria. So it’s thoroughly unsurprising that we’re officially learning what we’ve known for months: the CIA has been involved in Syria. According to Mark Hosenball the Finding Obama signed authorizing such actions permits us to collaborate at a “secret” command center on or close to our air base at Incirlik.

A U.S. government source acknowledged that under provisions of the presidential finding, the United States was collaborating with a secret command center operated by Turkey and its allies.

[snip]

This “nerve center” is in Adana, a city in southern Turkey about 60 miles from the Syrian border, which is also home to Incirlik, a U.S. air base where U.S. military and intelligence agencies maintain a substantial presence.

The Finding doesn’t authorize arming the rebels (though Hosenball’s sources seem unsure about the general scope of the Finding), but NBC has reported that the Saudis and Qataris have already armed them with shoulder-launched missiles.

It’s just like old times! The US partnering with Saudis to get shoulder-launched missiles into the hands of rebels with dubious loyalties. Whatever could go wrong with that?

There are two details about this that deserve notice.

What happened to the leak hawks in Congress?

First, this story is based on the leak of a covert Finding–precisely the kind of leak that Congress has gone on the warpath against. Hosenball attributes his reporting to US sources–an attribution that can (though doesn’t necessarily) refer to Congressional sources.

U.S. sources familiar with the matter said.

[snip]

A U.S. government source acknowledged

And while he notes–and names–the Senators who have been pressuring Obama to do precisely what he has been doing for months, Hosenball doesn’t name the members of Congress who are opposed to such an action.

Some U.S. lawmakers, such as Republican Senators John McCain and Lindsey Graham, have criticized Obama for moving too slowly to assist the rebels and have suggested the U.S. government should become directly involved in arming Assad’s opponents.

Other lawmakers have suggested caution, saying too little is known about the many rebel groups.

In short, chances are not insignificant that a Congressional source leaked the contents of a Finding authorizing covert operations.

And yet … crickets!

Those same Senate Intelligence Committee leak hawks who have authorized a range of stupid actions to prevent leaks seem unperturbed by a leak revealing information that is as sensitive as the leaks they’re demanding be investigated.

How does anti-Assad Finding relate to the Assad-cooperation authorized under the Gloves Come Off Memorandum of Notification?

Then there’s this. In his description of all the things included in the Gloves Come Off Memorandum of Notification authorizing the war on terror, Bob Woodward said cooperation with Syria (and Libya) were included.

[George Tenet] called for initiating intelligence contact with some rogue states such as Libya and Syria that he said might be helpful in trying to destroy al Qaeda. For the CIA to obtain helpful information against the terrorists, they might have to get their hands dirty. (Bush at War 77)

We know the MON included such cooperation with Libya because liberated documents have reflected cooperation on renditions. And Maher Arar, who was rendered to Syria and tortured, can tell you all about what our cooperation with Syria entailed.

The thing is, the MON authorizing cooperation with Syria remains in effect. We know that to be true because Judge Richard Wesley, in enabling the government to keep all mention of this MON secret a few months ago, stated it pertained to “active intelligence activity.” Rather than writing a new MON–one that doesn’t give CIA carte blanche in deciding the limits of things like targeted killings–Obama is still relying on this MON for things like killing American citizens.

So does that mean the CIA is at once authorized to share intelligence with Bashar al-Assad (under the Gloves Come Off MON) and help rebels overthrow and probably kill him (under this new Finding)?

Probably, there is a very simple explanation for this (and for the fact that we helped to kill Moammar Qaddafi, as well). Probably, the new FInding (and whatever Finding authorized the activities our spooks engaged in in Libya) simply includes language canceling the prior language authorizing cooperation with Assad. So no big deal, really.

Still, doesn’t that give lie to the Administration’s seeming treatment of that 11 year old MON as inviolate? That is, if this Finding renders (heh) part of that MON meaningless, then maybe it wouldn’t be so hard for Obama to write a new MON, one that involved actual oversight.