Microsoft also cut their QA department almost a decade ago.
It’s both Microsoft’s AND Crowd Strike’s fault.
it’s Crowdstrikes fault 100%. Just because it caused Windows to crash because Microsoft let Crowdstrike have system driver level access isn’t really Microsoft’s problem. You wouldn’t blame Microsoft if your video driver causes a crash when your video game loads would you? In a big picture kind of way maybe its Microsoft’s problem because they enabled the situation to happen but that’s not really in scope of what has actually happened.
But Microsoft designed the system such that they needed a level of access that allowed them to crash it. Microsoft could make changes that allowed the software to do what it needed with protections against letting that software crash the system. Basically a wrapper. Or, it could track updates to software that has such special access, and roll back updates after crashing more than once or something. It chooses not to. So it shares the blame because of that decision.
Anything with enough access to block malicious programs has enough access to block any other program by mistake.
Security modules like this usually get very invasive with the OS, to be able to monitor everything and so that malicious programs don’t have the ability to shut it off.
Wait until you learn about CrowdStrike breaking Linux systems as well.
Just kidding, no need to wait, here’s one article about it: https://www.neowin.net/news/crowdstrike-broke-debian-and-rocky-linux-months-ago-but-no-one-noticed/
Different events. Crowdstrike is really good at what they do (breaking systems).
Not to be smart, but just in conclusion: it’d have been pretty special, if they had broken down Linux and Windows with the same patch.
