The hack of an NSA malware staging server is not unprecedented, but the publication of the take is. Here's what you need to know: (1/x)
-
-
7) Why did they do it? No one knows, but I suspect this is more diplomacy than intelligence, related to the escalation around the DNC hack.
-
8) Circumstantial evidence and conventional wisdom indicates Russian responsibility. Here's why that is significant:
-
9) This leak is likely a warning that someone can prove US responsibility for any attacks that originated from this malware server.
-
10) That could have significant foreign policy consequences. Particularly if any of those operations targeted US allies.
-
11) Particularly if any of those operations targeted elections.
-
12) Accordingly, this may be an effort to influence the calculus of decision-makers wondering how sharply to respond to the DNC hacks.
-
13) TL;DR: This leak looks like a somebody sending a message that an escalation in the attribution game could get messy fast.
-
Bonus: When I came forward, NSA would have migrated offensive operations to new servers as a precaution - it's cheap and easy. So? So...
-
The undetected hacker squatting on this NSA server lost access in June 2013. Rare public data point on the positive results of the leak.
-
You're welcome,
@NSAGov. Lots of love. - 6 more replies
New conversation -
-
- 1 more reply
New conversation -
-
so it's a nation-state throw down?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@JanieBlakely Usually, a rival wouldn't reveal they'd done this, so the more interesting piece is - why did they this time?
-
Ohhhhh....ri.i.i.i.ight.
End of conversation
New conversation -
-
-
New wave of "cybersecurity" measures coming after US elections--bet on it. To "keep Americans safe".
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I see...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.