Wouldn’t any internal testing have cought this issue at CrowdStrike?
Yes. Why would anyone trust Crowdstike after this? They’ve ignored foundational deployment steps.
A smoke test, aka turn it on and “see if it catches fire,” would have caught this.
And a controlled rollout would’ve limited the damage.
CrowdStrike report of the incident: https://www.crowdstrike.com/falcon-content-update-remediation-and-guidance-hub/
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!
Listening 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.”
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
