Crowdstrike & Microsoft Outage on July 19th – What happened?
The issue on July 19, 2024, stemmed from an error in a routine update to CrowdStrike’s security software. This update, which was meant to enhance protection, contained a flaw in a component called a “Channel File.” This mistake caused some Windows systems running Falcon sensor versions 7.11 and above to crash and show a blue screen (BSOD) on Windows.
The problem was not due to a cyberattack but was simply a technical error. CrowdStrike identified and resolved the issue within an hour, fixing the update to prevent further problems.
Systems not affected continued to operate normally and remain secure. CrowdStrike is analyzing the incident to improve their processes and prevent future issues.
Is it fair to blame Microsoft?
In our opinion, blaming Microsoft for the Blue Screen of Death (BSOD) incident caused by CrowdStrike’s buggy update is unfair and misplaced for several reasons.
The responsibility lies with the vendor who introduced the problematic update, not with the operating system that supports a diverse range of software.
First, the BSOD issue stemmed from a flaw in CrowdStrike’s update to their Falcon sensor software, not from any inherent problem with the Windows operating system itself. The configuration update was designed to enhance security by targeting new threats, but a logic error in the update’s Channel File led to the system crashes. This issue was specific to the update’s implementation and was not a failure of Windows or its core components.
Second, Microsoft’s operating system provides the framework and support for a wide range of third-party software, including security solutions like CrowdStrike’s Falcon sensor. While Windows is responsible for maintaining system stability and providing robust support for various applications, the onus for ensuring that specific updates from third-party vendors do not cause disruptions falls on those vendors. CrowdStrike is accountable for the integrity of their own updates and how they interact with Windows.
Third, the quick response from CrowdStrike in identifying and fixing the problem within an hour demonstrates their commitment to resolving the issue and mitigating any impact. This prompt action underscores that the problem was not with Windows itself but rather with the specific update released by CrowdStrike.
Finally, Microsoft continuously works to ensure compatibility and stability across a wide ecosystem of software. They cannot control the quality of updates from every third-party vendor. Holding Microsoft responsible for issues arising from a specific vendor’s software update detracts from the responsibility that vendor holds for their own product’s performance and compatibility.
How were Computer Geeks and customers affected?
As an MSP, Computer Geeks and its clients were not affected by the Blue Screen of Death (BSOD) issue caused by the faulty CrowdStrike update because we do not use CrowdStrike’s Falcon sensor. Our managed services utilize alternative security solutions, which were unaffected by the July 19, 2024, incident.
CrowdStrike’s issue specifically impacted systems running Falcon sensor versions 7.11 and above. Since our security protocols and solutions do not include CrowdStrike, our clients’ systems were not exposed to the configuration update that caused the crashes. This means that our managed services continued to operate smoothly without any disruptions related to this incident.
At Computer Geeks, we ensure that our clients benefit from a robust and reliable security framework tailored to their needs. By employing different security tools and practices, we avoid the vulnerabilities associated with specific vendors’ issues and maintain uninterrupted protection for our clients.
