this post was submitted on 19 Jul 2024
357 points (97.1% liked)
Microblog Memes
6018 readers
2562 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The real blame lies on the fact that Windows lets hundreds of companies like Crowdstrike ship kernel-level software to millions of computers. The fact that this incident was caused by an accidental bug is hilarious, but we're lucky that it wasn't someone pushing malicious software instead.
Windows drivers are a huge liability and I wouldn't be surprised if the next time is a state actor like Russia pushing kernel-level malware.
The real fuck up is that Crowdstrike Falcon can auto update through its own updater, and doesn't have any kind of control panel for management that could be used for change control. If their customers could have tested this update first, none of this would be happening.
Yep. A lot of customers were running n-1 or even n-2 of their falcon sensor release to mitigate risk. Doesn't count for shit though if the "deployed content" bypasses all of that.