Case 8B99CD · Famous breaches · L3 Applied
Every Windows box is bluescreening
Live alertFriday 19 July 2024, 05:30 UTC: hundreds of Windows servers and laptops are stuck in BSOD boot loops pointing at csagent.sys. Linux and Mac hosts are fine; the service desk is asking if this is a cyberattack.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- Not an attack: a faulty CrowdStrike Falcon content update (Channel File 291) crashed Windows hosts that were online to receive it
- Root cause: the sensor expected 21 input fields but the template gave 20, causing an out-of-bounds read in a kernel driver
- Fix: boot to Safe Mode or WinRE and delete C-00000291*.sys from the CrowdStrike drivers folder; hosts need BitLocker recovery keys
- Prioritise: DCs and the systems that hold BitLocker keys first, then critical services; plan hands-on work at scale
- Expect phishing and fake 'fix' scripts riding the outage; Microsoft estimated about 8.5 million Windows devices were affected
If the interviewer pushes back
- Your BitLocker recovery keys live in AD, and the DCs are also bluescreening. How do you get out of that loop?
- What should you require from security vendors about staged rollout of content updates that run in the kernel?