|
|
|
|
|
by content_sesh
1806 days ago
|
|
I've held clearances before and that was very much not the attitude of the security folks I met. But they were big fans of reminding you what happens if they catch you doing an unauthorized disclosure. I was very low on the totem pole, so I can't know for certain what leadership actually expects. But it doesn't jibe with my experience that there would be some kind of "leak budget" similar to Google SRE "error budget". |
|
You are right. Security folks don't treat leaks lightly. Ever. This is part of how they maintain compliance with the rules.
But I don't think this is what the GP commenter talked about. You definitely design weapons, and doctrine and systems by assuming that it can leak to the enemy eventually. If your whole battle plan folds like wet tissue-paper just because the enemy got their hands on a single CAD file or manual then it wasn't a really good plan to begin with. Exhaust ports of doom are nice plot devices for movies, but in reality you try to avoid designed-in Achilles heels. And you do this because leaks happen.
Some information get leaked by carelessness, some by disgruntled employees, some are stolen by spies, some are picked up from a wreckage, some are stolen in transit, some are deduced from signal intelligence.
You can design mitigations against all of these. The scary security folks you mentioned are mitigation against the first two really. Their existence and behaviour doesn't have any bearing on what the leadership will expect.