After pretty much bricking every Windows 10/11 computer that ran CrowdStrike Falcon, CrowdStrike put out a post that details the technical ins and outs of what led up to what happened on Friday. You can read it here. In it they seem very open. And the company has committed to providing additional details and a root cause analysis.
The thing is that what happened on Friday is a warning to the planet, and to the IT industry. CrowdStrike really screwed up here and disrupted the planet in the process. The mitigation for this is relatively easy to apply as I did that a whole bunch of times on Friday and Saturday. But because of the scale of this event, we’re talking about days before this problem is fully dealt with. In other words, this was bad. But it could have been worse. We need to learn from that and be prepared for the next event like this. Because there will be a next event. That starts with CrowdStrike being completely open to laying bare what happened and what they will do to ensure that it never happens again. And that’s followed up by other companies learning from this event and ensuring that they don’t become the next Crowdstrike.
UPDATE: After I posted this, I got this commentary from John Gunn, CEO, Token:
If anyone wants to know what a full-blown cyberattack from China or other enemy nations might look like, this event just gave us a small preview of the interruptions and havoc that could be inflicted. Every day we hear about new ransomware attacks, but these are revealed because of the immediate financial payoff the attackers seek. There are undoubtedly countless significant network intrusions throughout our infrastructure and essential services that are undetected which are like sleeper cells waiting to be activated if we enter a major conflict with these nations.
CrowdStrike Puts Out Technical Details Of Their Epic Screw Up… Why This Should Be Required Reading For Everyone
Posted in Commentary with tags CrowdStrike on July 21, 2024 by itnerdAfter pretty much bricking every Windows 10/11 computer that ran CrowdStrike Falcon, CrowdStrike put out a post that details the technical ins and outs of what led up to what happened on Friday. You can read it here. In it they seem very open. And the company has committed to providing additional details and a root cause analysis.
The thing is that what happened on Friday is a warning to the planet, and to the IT industry. CrowdStrike really screwed up here and disrupted the planet in the process. The mitigation for this is relatively easy to apply as I did that a whole bunch of times on Friday and Saturday. But because of the scale of this event, we’re talking about days before this problem is fully dealt with. In other words, this was bad. But it could have been worse. We need to learn from that and be prepared for the next event like this. Because there will be a next event. That starts with CrowdStrike being completely open to laying bare what happened and what they will do to ensure that it never happens again. And that’s followed up by other companies learning from this event and ensuring that they don’t become the next Crowdstrike.
UPDATE: After I posted this, I got this commentary from John Gunn, CEO, Token:
If anyone wants to know what a full-blown cyberattack from China or other enemy nations might look like, this event just gave us a small preview of the interruptions and havoc that could be inflicted. Every day we hear about new ransomware attacks, but these are revealed because of the immediate financial payoff the attackers seek. There are undoubtedly countless significant network intrusions throughout our infrastructure and essential services that are undetected which are like sleeper cells waiting to be activated if we enter a major conflict with these nations.
Leave a comment »