Microsoft drops subtle hints about the future direction of Windows security.
CrowdStrike’s Falcon software uses a special driver that allows it to run at a lower level than most apps so it can detect threats across a Windows system. Microsoft tried to restrict third parties from accessing the kernel in Windows Vista in 2006 but was met with pushback from cybersecurity vendors and EU regulators. However, Apple was able to lock down its macOS operating system in 2020 so that developers could no longer get access to the kernel.
Now, it looks like Microsoft wants to reopen the conversations around restricting kernel-level access inside Windows.
Exactly. Either they’re going to make Windows Defender have the monopoly on antivirus and endpoint protection (EU will shut them down faster than a crowdstrike bluescreen), or they will need to grant the access to those providers.
If Microsoft think they will be able to curate every single device driver and other kernel module (like antivirus etc) and catch the kind of bug that caused this error? They’re deluded.
I’ll wait and see what they actually propose before outright ruling it out. But, I can’t see how they do this in any realistic way.
Either they’re going to make Windows Defender have the monopoly on antivirus and endpoint protection (EU will shut them down faster than a crowdstrike bluescreen)
Really not sure if they have any kernel level antivirus products. Although the same question applies I guess to third party hardware drivers. How are they installed? What privilege level do they run in?
Sure, “restrict” the kernel access. And the first company to be granted the requisites for kernel access, CrowdStrike.
Exactly. Either they’re going to make Windows Defender have the monopoly on antivirus and endpoint protection (EU will shut them down faster than a crowdstrike bluescreen), or they will need to grant the access to those providers.
If Microsoft think they will be able to curate every single device driver and other kernel module (like antivirus etc) and catch the kind of bug that caused this error? They’re deluded.
I’ll wait and see what they actually propose before outright ruling it out. But, I can’t see how they do this in any realistic way.
How does Apple handle this?
Really not sure if they have any kernel level antivirus products. Although the same question applies I guess to third party hardware drivers. How are they installed? What privilege level do they run in?