Article Details

Scrape Timestamp (UTC): 2024-07-22 13:04:20.146

Source: https://www.theregister.com/2024/07/22/windows_crowdstrike_kernel_eu/

Original Article Text

Click to Toggle View

EU gave CrowdStrike the keys to the Windows kernel, claims Microsoft. Was a 2009 directive on interoperability to blame?. Did the EU force Microsoft to let third parties like CrowdStrike run riot in the Windows kernel as a result of a 2009 undertaking? This is the implication being peddled by the Redmond-based cloud and software titan. As the tech industry deals with the fallout from the CrowdStrike incident, Microsoft is facing questions. Why is software like CrowdStrike permitted to run at such a low level, where a failure could spell disaster for the operating system? To be clear, Microsoft is not to blame for the now-pulled update that continues to cause chaos. However, the underlying architecture that allows third parties to run deeply integrated software merits closer examination. According to a report in the Wall Street Journal, a Microsoft spokesperson pointed to a 2009 undertaking by the company with the European Commission as a reason why the Windows kernel was not as protected as that of the current Apple Mac operating system, for example. The agreement [DOC] is about interoperability and came as Microsoft was subject to European scrutiny. The undertaking seeks a level playing field and includes the following clause: Microsoft shall ensure on an ongoing basis and in a Timely Manner that the APIs in the Windows Client PC Operating System and the Windows Server Operating System that are called on by Microsoft Security Software Products are documented and available for use by third-party security software products that run on the Windows Client PC Operating System and/or the Windows Server Operating System. In other words, third-party security vendors must get the same access as Microsoft's own products. Which, on the face of it, is fair enough. However, nothing in that undertaking would have prevented Microsoft from creating an out-of-kernel API for it and other security vendors to use. Instead, CrowdStrike and its ilk run at a low enough level in the kernel to maximize visibility for anti-malware purposes. The flip side is this can cause mayhem should something go wrong. The Register asked Microsoft if the position reported by the Wall Street Journal was still the company's stance on why a CrowdStrike update for Windows could cause the chaos it did. The company has yet to respond. Windows is far from the only operating system that permits software to run at a level low enough to crash a kernel. However, failures of third-party software running at a low level in Windows can be embarrassingly public, even if Microsoft is not directly to blame.

Daily Brief Summary

MISCELLANEOUS // Microsoft Links EU Directives to Windows Kernel Vulnerabilities

Microsoft attributes third-party access to Windows kernel to a 2009 EU directive aimed at ensuring interoperability.

The directive requires Microsoft to make certain APIs available to third-party security products, similar to those used by Microsoft’s own security software.

This policy has allowed companies like CrowdStrike to operate deeply within the Windows system, which can enhance security but also pose significant risks.

Microsoft is scrutinized over its decisions on third-party kernel level access, especially following a disruptive update from CrowdStrike.

The issue highlights the broader challenge of balancing system security with third-party software capabilities within operating systems.

Microsoft has not updated its stance following the chaos caused by the CrowdStrike update.

The architecture of Windows allows such deep integration by third parties, similar to permissions seen in other operating systems, though with potentially high-profile failures.