{"id":9474,"date":"2024-07-25T12:09:02","date_gmt":"2024-07-25T11:09:02","guid":{"rendered":"https:\/\/www.imsm.com\/us\/?p=9474"},"modified":"2024-07-25T12:09:02","modified_gmt":"2024-07-25T11:09:02","slug":"3-key-takeaways-from-the-crowdstrike-outage","status":"publish","type":"post","link":"https:\/\/www.imsm.com\/us\/news\/3-key-takeaways-from-the-crowdstrike-outage\/","title":{"rendered":"3 Key Takeaways from the CrowdStrike Outage"},"content":{"rendered":"

July 19, 2024, will long be remembered as the most extensive system and infrastructure outage in recent memory.<\/em><\/p>\n

Systems worldwide faltered\u2014and outright failed in many circumstances\u2014due to a faulty update to the Falcon sensor configuration for Windows systems. Consequently, mass-scale outages hit many vital industries, stirring up turmoil for those waiting for flights, appointments, bank transfers, and just going about their daily lives. If you experienced the dreaded BSOD (Blue Screen of Death) on Friday 19th, you’d be one of millions.<\/p>\n

We’ll discuss three key takeaways, both positive and negative, from the CrowdStrike outage.<\/p>\n

1. Lack of Prior Testing<\/h2>\n

CrowdStrike didn’t test their update enough before deploying it live, which led to the outage.<\/p>\n

The fault happened due to an oversight in testing. There may have been a presumption that the update was ready for deployment before it actually was. This has had colossal consequences – not just for CrowdStrike themselves but for companies and organizations running on Windows systems across the globe.<\/p>\n

2. Quick and Transparent Response<\/h2>\n

Once the update went live, the effects hit instantaneously. However, CrowdStrike responded to the situation quickly and transparently. They kept their lines of contact open and accessible throughout the crisis, which they’ve received praise for.<\/p>\n

Despite the odds, CrowdStrike has emerged from the situation quite favorably because of its response. It has set a shining example of how to manage a crisis, not just because of its response but also because it effectively managed the massive scale of the issue. They may stand out in this way because this isn’t always the outcome when large-scale problems arise. It’s important to note that they aren’t free from scrutiny – in fact, they’re far from it. But compared to similar incidents, they have fared well.<\/p>\n

When things go wrong, companies often encounter internal turmoil. When this inevitably meets the public eye, it can negatively affect their reputation and diminish trust among their consumers. So far, this has yet to happen to CrowdStrike.<\/p>\n

3. A Worldwide Impact<\/h2>\n

For many, the sheer scale of the outage is the most astounding part of the whole event. It has become one of the most significant technological failures ever, leaving no industry unaffected (aside from those using Mac and Linux!).<\/p>\n

It highlighted how dependent companies and individuals globally are on Windows-based technology and how issues can bring vital systems crashing down. What happened might make people apprehensive about Microsoft and CrowdStrike and how much of their infrastructure they should base virtually, especially with cloud-based systems.<\/p>\n

Don’t put all your eggs in one basket!<\/h3>\n

While it was a stressful day for Windows-based databases, systems, and operators, it was business as usual for Mac and Linux users.<\/p>\n

The outage begs a few questions all companies should consider:<\/p>\n