KidM to CybersecurityEnglish • 2 months agoCrowdStrike Explains Friday Incident Crashing Millions of Windows Devicesthehackernews.comexternal-linkmessage-square9arrow-up142arrow-down12
arrow-up140arrow-down1external-linkCrowdStrike Explains Friday Incident Crashing Millions of Windows Devicesthehackernews.comKidM to CybersecurityEnglish • 2 months agomessage-square9
minus-square@[email protected]linkfedilinkEnglish19•2 months agoWouldn’t any internal testing have cought this issue at CrowdStrike?
minus-square@[email protected]linkfedilinkEnglish16•2 months agoA smoke test, aka turn it on and “see if it catches fire,” would have caught this.
minus-square@sugar_in_your_tealinkEnglish14•2 months agoAnd a controlled rollout would’ve limited the damage.
minus-square@[email protected]linkfedilinkEnglish10•2 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.