Microsoft looking to restrict kernel level access after CrowdStrike incident might help us with our current Anti-Cheat dilemma
Microsoft looking to restrict kernel level access after CrowdStrike incident might help us with our current Anti-Cheat dilemma
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.
You're viewing a single thread.
Imo, third party companies just shouldn't have access to the kernel level. Someone is always getting hacked, and having this level of access to potentially hundreds of millions of computers is a huge risk. Especially if it's for something trivial, like anticheat in Helldivers 2.
and let someone into the kernel,
Problem is, that similarly to invasion of privacy, this is not visible, and so they don't understand what's happening. It's just one more program, what could happen? It's not like somebody coming and inspecting your house, in that it is not noticeable in practice.
@ReversalHatchery , I completely agree. My ring 0 is sacred and I can't prove there isn't anything in it already, but I wouldn't knowingly shove third party stuff into my kernel. I like to keep my apps restricted from anything they don't need on my system in userland. However, millions upon millions of people installed Tencent's Vanguard to play League of Legends like it wasn't any big deal (it is). If people want an inner ring security module, I suppose that's a bit their choice. 🤷🏽♂️
Yeah, those security agents can become attack vectors themselves, so running them kernel level is nuts.
Enterprise level AVs are going to sit in the kernel so they can watch for anomalies in the OS. There are better EDRs out there than Crowdstrike, and virus definitions are an outdated way of detecting anamalous behavior anyway.