KidM to [email protected]English • 4 months agoCrowdStrike Explains Friday Incident Crashing Millions of Windows Devicesthehackernews.comexternal-linkmessage-square9fedilinkarrow-up142arrow-down12
arrow-up140arrow-down1external-linkCrowdStrike Explains Friday Incident Crashing Millions of Windows Devicesthehackernews.comKidM to [email protected]English • 4 months agomessage-square9fedilink
minus-square@[email protected]linkfedilinkEnglish19•4 months agoWouldn’t any internal testing have cought this issue at CrowdStrike?
minus-square@[email protected]linkfedilinkEnglish16•4 months agoA smoke test, aka turn it on and “see if it catches fire,” would have caught this.
minus-square@[email protected]linkfedilinkEnglish14•4 months agoAnd a controlled rollout would’ve limited the damage.
minus-square@BrkdncrlinkEnglish10•4 months agoYes. Why would anyone trust Crowdstike after this? They’ve ignored foundational deployment steps.
Wouldn’t any internal testing have cought this issue at CrowdStrike?
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.
Yes. Why would anyone trust Crowdstike after this? They’ve ignored foundational deployment steps.