{"id":5914,"date":"2024-07-26T10:21:53","date_gmt":"2024-07-26T09:21:53","guid":{"rendered":"https:\/\/www.imsm.com\/hk\/?p=5914"},"modified":"2024-07-26T10:21:53","modified_gmt":"2024-07-26T09:21:53","slug":"3-takeaways-from-the-crowdstrike-outage","status":"publish","type":"post","link":"https:\/\/www.imsm.com\/hk\/news\/3-takeaways-from-the-crowdstrike-outage\/","title":{"rendered":"3 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

On Friday, systems worldwide faltered\u2014and outright failed in many instances\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), you\u2019d be one of many.<\/p>\n

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

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

CrowdStrike didn\u2019t test their update rigorously enough before deploying it live, which led to the outage, meaning that ultimately, the fault happened due to a testing oversight.<\/p>\n

There may have been a presumption that the update was ready for deployment before it actually was. As we\u2019ve all come to know, this has had colossal consequences \u2013 not just for CrowdStrike themselves but for companies and organisations 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\u2019ve received some praise for.<\/p>\n

Despite the odds, CrowdStrike has emerged from the situation quite favourably 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 navigated the issue despite its sheer scale. They may stand out in this way because this isn\u2019t always the outcome when large-scale problems arise. It\u2019s important to note that they aren\u2019t entirely free from scrutiny \u2013 in fact, they\u2019re far from it. But compared to similar incidents, they have fared quite 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 in recent history, leaving no industry unaffected (aside from those using Mac and Linux systems).<\/p>\n

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

Don\u2019t Put All Your Eggs in One Basket!<\/h3>\n

While it was a stressful day for Windows-based databases, systems, and general users, it was business as usual for Mac and Linux. So, the outage begs a few questions all companies should consider:<\/p>\n