Live data from Hacker News

Don’t Mention the Cables, Future Diplomats

thelede.blogs.nytimes.com

1–10 of 15 posts

Re: Don’t Mention the Cables, Future Diplomats

#2
This isn't some paranoid crazytalk from a government driven mad by Cablegate. It is a fact that classified data isn't declassified by nature of having been published. Apparently, contractors who are cleared for handling classified data (here you learn that Matasano doesn't do government work) are quizzed on this routinely.

It's apparently a basic rule of information hygiene that you can't ignore classification just because something becomes public, so, ignoring the fact that data is classified may demonstrate to a prospective employer that you don't understand how to take classification seriously.

Re: Don’t Mention the Cables, Future Diplomats

#3
post #2

This isn't some paranoid crazytalk from a government driven mad by Cablegate. It is a fact that classified data isn't declassified by nature of having been published. Apparently, contractors who are cleared for handling classified data (here you learn that Matasano doesn't do government work) are quizzed on this routinely. It's apparently a basic rule of information hygiene that you can't ignore classification just b…

Sure, that's the precedent and official policy for actual employees and contractors.

But does that standard make sense applied to private citizens, having conversations about widely-available information, before ever applying for a job?

The State Department may get more careful, coldly calculating applicants by eliminating those who discuss leaked cables – but not more curious and well-informed ones.

Re: Don’t Mention the Cables, Future Diplomats

#4
post #2

This isn't some paranoid crazytalk from a government driven mad by Cablegate. It is a fact that classified data isn't declassified by nature of having been published. Apparently, contractors who are cleared for handling classified data (here you learn that Matasano doesn't do government work) are quizzed on this routinely. It's apparently a basic rule of information hygiene that you can't ignore classification just b…

While it's not paranoid crazytalk, it certainly looks like typical bureaucratic foolishness to me. Maybe I'm missing something here, of course.

I can sort of see the logic: if you are working for an organization whose classified data got leaked, but the organization has not declassified that data, you must still treat it as classified to avoid leaking any other related data by accident (for example).

But these students don't work for the government yet. Discussing leaked cables does not necessarily imply they don't understand classification.

Re: Don’t Mention the Cables, Future Diplomats

#5
When it comes down to it, these cables were leaked most likely due to Bradley Manning handing them over to Wikileaks. Thus, it was fundamentally a failure of the security clearance screening process that made this leak possible; a bad apple got through.

From that point of view, it only makes sense to assume that the screening process will be more strict moving forward. No surprise, then, that one metric that may be taken into account will be a person's feelings toward Wikileaks. I imagine the people conducting clearance reviews will look at everything a candidate has posted online, and ask them directly how they feel about Wikileaks.

Sympathetic feelings toward Wikileaks is simply a chance the US Government will not be willing to take.

Re: Don’t Mention the Cables, Future Diplomats

#6
post #4
post #2

This isn't some paranoid crazytalk from a government driven mad by Cablegate. It is a fact that classified data isn't declassified by nature of having been published. Apparently, contractors who are cleared for handling classified data (here you learn that Matasano doesn't do government work) are quizzed on this routinely. It's apparently a basic rule of information hygiene that you can't ignore classification just b…

While it's not paranoid crazytalk, it certainly looks like typical bureaucratic foolishness to me. Maybe I'm missing something here, of course. I can sort of see the logic: if you are working for an organization whose classified data got leaked, but the organization has not declassified that data, you must still treat it as classified to avoid leaking any other related data by accident (for example). But these studen…

> you must still treat it as classified to avoid leaking any other related data by accident (for example).

That is not quite the reason. The real reason is that those who have clearance can be prosecuted for a willful security violation if they:

* store, process, or view classified data on an un unauthorized machine (home laptop)

* grant others access to the classified data

* discuss classified information where others who are not authorized would overhear or see it.

* prying into or accessing classified info for which they don't have a need-to-know

* creating unauthorized copies of classified info

The warning not to access this info is basically a helpful tip or reminder so those who hold or will hold clearance could be subject to harsh penalties.

This is just as much about protecting the classified info as it is the protect those who have a clearance.

These rules and laws have been deliberately written to be broad and wide so that a potential spy can be easily prosecuted as they are usually found in possession of classified info in their house or on their laptop for which they have no authorization to have.

There is simply no exception for the case when thousands and thousands of classified docs have been spread over the internet and are just as easily accessed as driving directions to a restaurant.

EDIT:

This is actually a great example of how a broad and overreaching law (by virtue of not being updated to specifically exclude leaked info) can be used to selectively prosecute certain individuals at will. Chances are some of those who have a clearance have read excerpts from Cablegate on the web just by reading the news. An overzealous prosecutor can turn that into a "willful security violation" if they really want to. This is in the same category as "obstruction of business", "obstruction of justice", "disruptive behavior" charges.

Re: Don’t Mention the Cables, Future Diplomats

#7
Do government employees have an assumption that their work communications are kept private and there is no/little recourse as to what they say in them?

I always figure that at work 100% of what I write can be read by the entire company, and that I will be held accountable for anything I say/do even if I have the best intentions in mind. If I say in an email something unfavorable or slanderous about another company's CEO, and it gets out, then I must face the consequences.

It seems that American government employees and diplomats have another expectation of privacy and consequence to what they say/do.

Re: Don’t Mention the Cables, Future Diplomats

#8
post #2

This isn't some paranoid crazytalk from a government driven mad by Cablegate. It is a fact that classified data isn't declassified by nature of having been published. Apparently, contractors who are cleared for handling classified data (here you learn that Matasano doesn't do government work) are quizzed on this routinely. It's apparently a basic rule of information hygiene that you can't ignore classification just b…

I suppose. A side effect of this policy, though, is that it rules out any future employees who are passionate enough about an incredibly important issue to discuss it publicly after it's appeared on the cover of Time magazine. Seems wrongheaded to me.

Re: Don’t Mention the Cables, Future Diplomats

#9
post #6
post #4

Earlier quoted context omitted.

While it's not paranoid crazytalk, it certainly looks like typical bureaucratic foolishness to me. Maybe I'm missing something here, of course. I can sort of see the logic: if you are working for an organization whose classified data got leaked, but the organization has not declassified that data, you must still treat it as classified to avoid leaking any other related data by accident (for example). But these studen…

> you must still treat it as classified to avoid leaking any other related data by accident (for example). That is not quite the reason. The real reason is that those who have clearance can be prosecuted for a willful security violation if they: * store, process, or view classified data on an un unauthorized machine (home laptop) * grant others access to the classified data * discuss classified information where othe…

excellent point in the edit!

Re: Don’t Mention the Cables, Future Diplomats

#10
Pursued to its logical conclusion, this means that the 800,000 or so US citizens with some level of security clearance have been forbidden from reading newspapers, watching the Daily Show, or discussing politics for the last week or so. Really? I mean, I know that reductio ad absurdum isn't a successful defence against dumb law, but this seems a bit excessive.

Especially considering that a big part of what's been released so far has been ho-hum stuff that just reinforces what a lot of people have speculated was true---"Eh, they don't really think that'll work."---and now making a comment like that means you're propagating classified information and thus ineligible for a State Department job?

I mean, it has shades of the old Khrushchev line ("3 years for insulting the premier, 20 years for revealing state secrets.") It's one thing to say that a leak that one person saw does not automatically declassify something (trade secret law works the same way), but when the leak is on this kind of scale and has been commented on so publicly, it seems hard to justify.

Post reply on HN