Okay, deep breath, let's get this over with. In the grand act of digital self-sabotage, we've littered this site with cookies. Yep, we did that. Why? So your highness can have a 'premium' experience or whatever. These traitorous cookies hide in your browser, eagerly waiting to welcome you back like a guilty dog that's just chewed your favorite shoe. And, if that's not enough, they also tattle on which parts of our sad little corner of the web you obsess over. Feels dirty, doesn't it?
Microsoft’s 8.5 Million Machine Meltdown: How CrowdStrike’s Update Crashed the Party
Microsoft admitted its estimate of 8.5 million machines crashed by CrowdStrike’s update was too low. Vowing to reduce reliance on kernel drivers, Microsoft highlighted the need for infosec vendors to balance security against resilience risks. Are you taking notes, CrowdStrike?
Hot Take:
Looks like Microsoft just admitted that they underestimated how many computers CrowdStrike’s bad update sent to the blue screen of despair. But don’t worry, they’re on a mission to make kernel drivers as rare as a unicorn sighting in downtown Redmond. Buckle up, folks, this ride isn’t over yet!
Key Points:
– Microsoft underestimated the impact of CrowdStrike’s faulty update on Windows machines.
– Not all crash reports were shared by Windows customers, skewing the estimated number.
– Microsoft aims to reduce reliance on kernel drivers to prevent similar incidents.
– Redmond runs the Microsoft Virus Initiative (MVI) to collaborate with security vendors.
– New measures include safe rollout guidance, reducing kernel driver usage, and enhancing security with technologies like VBS enclaves.
Already a member? Log in here