A Word About Leaks

By Shane Harris

August 8, 2012

Leaks of classified information are back in the news. Or more precisely, the hunt for leakers is making headlines again. After big news scoops on intelligence programs—involving counterterrorism operations in Yemen, drone strikes and a cyberwar campaign against Iran—lawmakers are accusing the White House of disclosing covert operations to make President Obama look strong on national security in an election year. The Obama administration, which has prosecuted an unprecedented number of government employees for allegedly disclosing classified information to journalists, insists that the president abhors leaks and no one in the White House gave away any national security secrets.

The truth lies somewhere in the middle. And it all depends on how you define the word “leak.” For argument’s sake, let’s consider leaks to be disclosures of classified information. Officials reveal all kinds of information every day that could be sensitive or potentially embarrassing, but isn’t covered by a classification regime.

The next question is whether the leak was authorized.  

Authorized leaking happens all the time in Washington. If the president tells his counterterrorism adviser to give a speech on the United States’ use of drones to kill terrorists—which he did recently—the president has effectively declassified whatever information his adviser relays.

Authorized leaks were also a part of at least one of the recent news scoops that has so many officials in a lather. David E. Sanger, a reporter for The New York Times and the author of the book Confront and Conceal (Crown, 2012), revealed new details about the administration’s cyberwar tactics. Sanger tells us in his book that he was granted access to almost every member of the president’s national security team. Such access is rare and is the result, in part, of a decision by the Obama administration to disclose certain secrets. They might not have been the most startling revelations that Sanger discovered in his reporting—which was surely based on some un-authorized leaks—or even the most secret. But the mere fact that officials were talking with a journalist about intelligence programs meant leaks of some kind were blessed at a high level.      

It’s the unauthorized leaks that tend to cause the most controversy and put government employees in the most danger. How do we know when a leak is unauthorized? For reporters, it can be hard to tell sometimes, but a good indication is if the person sharing the information says, “I could lose my job over this.” Or, “I might go to jail for this.”

Does it follow that the information shared in an unauthorized leak must be more sensitive, more revealing, more potentially damaging to the United States than the authorized leak? Absolutely not.

Former National Security Agency official Thomas Drake was not authorized to talk to journalists when he contacted a reporter forThe Baltimore Sun and told her about wasteful spending at NSA. The information he conveyed was nowhere near as sensitive as secrets about drone strikes or cyberwar. And yet, the Justice Department indicted Drake under the 1917 Espionage Act for illegally disclosing classified information.

Drake insisted he’d done no such thing, and the dubious case against him fell apart before it went to trial. But it proved an essential point: In matters of leaks, it’s not the leak itself that’s at issue, but whether it was authorized. When lower level career employees make that decision—however more principled it may be—they’re open to prosecution.

No system of secrecy can work if people are allowed to arbitrarily break its rules. But a decision to leak may be arbitrary, too, even if it was authorized.   

Shane Harris is the author of The Watchers: The Rise of America’s Surveillance State and was a staff writer for Government Executive.


By Shane Harris

August 8, 2012

http://www.govexec.com/excellence/management-matters/2012/08/word-about-leaks/57271/