Watching the slow motion Twitter trainwreck is just amazing. I hope we get an amazing postmortem out of this, but chances are their security team is just incompetent/understaffed and this just boils down to someone's credentials being stolen and them failing at containment.
-
Show this thread
-
Short of a nation state level attack, there's no reason this should've taken more than 5 minutes to contain, TBQH.
2 replies 2 retweets 32 likesShow this thread -
Word is this was a compromised user admin panel (screenshots are floating around). If so, it should've taken 40 seconds to disable that thing entirely, then 15 minutes to dig through the audit logs (they have audit logs, right????) and undo the damage.
6 replies 3 retweets 40 likesShow this thread -
Worth mentioning that if these tools didn't exist, it's almost certainly because management didn't let security staff build them, or didn't care, or they're understaffed, not because of sec staff themselves. This is Twitter being incompetent as an organization, not individuals.
2 replies 2 retweets 27 likesShow this thread -
Replying to @marcan42
I practically guarantee the sec staff has been pitching it, for years. Probably even saying words like "existential risk" and "if you don't do this you will hit a worst-case security breach" and getting ignored.
1 reply 0 retweets 4 likes -
Doesn't matter how competent your security staff are if they're ignored by leadership.
2 replies 0 retweets 5 likes
Alternatively, it could be that the security staff *is* incompetent because management drove away all the competent employees.
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.