Kid@sh.itjust.worksM to Cybersecurity@sh.itjust.worksEnglish · 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.comKid@sh.itjust.worksM to Cybersecurity@sh.itjust.worksEnglish · 4 months agomessage-square9fedilink
minus-squarekylian0087@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up19·4 months agoWouldn’t any internal testing have cought this issue at CrowdStrike?
minus-squareTelorand@reddthat.comlinkfedilinkEnglisharrow-up16·4 months agoA smoke test, aka turn it on and “see if it catches fire,” would have caught this.
minus-squaresugar_in_your_tea@sh.itjust.workslinkfedilinkEnglisharrow-up14·4 months agoAnd a controlled rollout would’ve limited the damage.
minus-squareBrkdncr@lemmy.worldlinkfedilinkEnglisharrow-up10·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.