CrowdStrike Explains Friday Incident Crashing Millions of Windows Devices
CrowdStrike Explains Friday Incident Crashing Millions of Windows Devices
CrowdStrike's faulty update caused a widespread Windows device crash, impacting millions. The company is improving its error handling and testing proc
Wouldn't any internal testing have cought this issue at CrowdStrike?
19 0 ReplyA smoke test, aka turn it on and "see if it catches fire," would have caught this.
16 0 ReplyAnd a controlled rollout would've limited the damage.
14 0 Reply
Yes. Why would anyone trust Crowdstike after this? They’ve ignored foundational deployment steps.
10 0 Reply
But will you try actually installing the update on a machine or 50 to see if you bork things horrifically?
Crowdstrike: "We are really focused on unit testing right now"
I probably misread it, don't mind my grumbling, rabble rabble rabble
13 0 ReplyCrowdStrike report of the incident: https://www.crowdstrike.com/falcon-content-update-remediation-and-guidance-hub/
5 0 ReplyLocal developer testing
Hmm, didn't think of that one...
staggered deployment strategy
Also a novel idea...
It's like they're catching up to best practices from 10 years ago, good job team!
6 0 ReplyListening to literally any sysadmin would have had these practices already in play.
I wonder if any are in the building, of if it's all devs and "platform engineers."
2 0 Reply
Systems in scope include Windows hosts running sensor version 7.11 and above that were online between Friday, July 19, 2024 04:09 UTC and Friday, July 19, 2024 05:27 UTC and received the update.
Definitely incorrect. My machine was powered off by physical switch at that time. It was powered off at 17:00 the day before and powered up at 08:00 CEST / 06:00 UTC and promptly bluescreened.
1 0 Reply
Local developer testing
Hmm, didn't think of that one...
staggered deployment strategy
Also a novel idea...
It's like they're catching up to best practices from 10 years ago, good job team!
1 0 Reply