- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
alt text:
We were going to try swordfighting, but all my compiling is on hold.
explanation: https://explainxkcd.com/wiki/index.php/2961:_CrowdStrike
I appreciate the callback to #303.
I’ll be honest I thought it was just this one recaptioned. Thank you for pointing it out that they are messing around in different ways
“We were going to try swordfighting, but all my compiling is on hold.” Is the alt text. I thought it was the same too.
I even thought about a crowd strike version of #303 today too
Pretty much what happens when you knock out something important
Me, the only sysadmin with access to the data center and AD: “I’m drowning!”
ISR team that selected Crowdstrike: " were going to the coffee shop, let us know when it’s back up"
Today has been a nightmare of stupid problems
I hope you guys run a lessons learned after it all. Go ahead and roll your eyes, but reflecting on prior performance can have a huge impact for the future. It shouldn’t all come down to you in the end, and that’s okay.
Every org worth their weight will be doing a root cause analysis after this. So many lessons learned. We were impacted very minimally and only through external vendors.
Consider yourself lucky!