Lately I’ve been dealing with a lot of ransomware cases. And often our team runs into issues with the IT staff from the victim organization.
33
260
56
1,306
Whether they’re embarrassed or afraid of being shown up or for whatever other reason, they’re uncooperative or in some cases actively working against our investigation.
2
6
1
252
So on a recent case, during our engagement kick-off call, I laid it out like this. “We’re going to investigate and figure out where this started. And it will be an unpatched system, or somebody clicking a link, or somebody just being unlucky with a web site they visited.”

Jul 18, 2021 · 9:42 PM UTC

3
14
3
263
“And NONE of that is YOUR FAULT. All organizations are vulnerable, because I have yet to meet an org whose security budget exceeds their attack surface.”
4
22
3
377
“You are not the assholes here. The assholes are the ones who took that vulnerability and used it to drop ransomware all over your network. Just because you forgot and left your door unlocked doesn’t make it right for somebody to come in and trash your place.”
4
15
1
303
“We are the good people. The ones who are trying to figure out what happened and make things better. This is a team effort that is going to require everybody’s help. Nobody is to blame, we are all just trying to fix this mess we find ourselves in.”
2
6
254
Later in the engagement, several people from all levels in the IT staff said they appreciated those words and the timing and it helped them move on from the initial FUD stage of the incident and be more productive. Your mileage, as always, may vary.
16
13
580
Replying to @hal_pomeranz
Or a supply chain vulnerability (Kaseya) that couldn't have been prevented by anything you did.
1
So true
This tweet is unavailable
Backups will definitely aid in recovery. They won't stop the ransomware from being implanted. And they won't stop the org from paying the ransom in order to avoid sensitive data being leaked.
1