357
First and Last day
(lemm.ee)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2024
357 points (97.1% liked)
Microblog Memes
8822 readers
212 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 2 years ago
MODERATORS
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.
Or if they were smart enough to do a phased rollout to a small percentage of users before deploying worldwide. That catches most issues quickly.
Or if Microsoft reviewed drivers before signing them.
I think they do (or at least I've seen it mentioned), but this wa apparently caused a by a bad configuration fil for that driver. (A 40-something kB file pf pure zeroes)
or like, tested the fucking update at all...
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.
an antivirus-like software is something you want auto updates for in my opinion