Believe it or not, CrowdStrike’s model forces updates and people pay a lot of money for it to “handle things” for them. I had to deploy it at a previous employer about 8 years ago. It was stupid.
No one forces you to update. People simply choose to run an OS where automatic updates are the default.
And that OS also lets you permanently disable automatic updates. It just doesn’t give you a straight-forward GUI option for it.
Critically wrong in this case. Crowdstrike updates push outside of, and regardless of, os settings. This wasn’t, and never was, an os issue, it’s a crowdstrike issue. Good try though.
Problem is, an individual computer user often isn’t the victim of that computer’s lack of updates.
Any time a site you like has been DDOSed, it’s often from thousands of zombie computers infected by some malware that their owners aren’t aware of. Those infections are generally made possible by unclosed security holes. So, you know…not updating.
I’m fine being part of a botnet if that’s the trade off for not using windows 11. Just got it installed on my testing PC at work and I hate it so much.
You really don’t understand how many millions of hours of human effort force updates have destroyed.
Yes, there should always be, ESPECIALLY IN CORPORATE ENVIRONMENTS, a point where the client can vet and approve the update.
This recent Crowdstrike problem is proof of it. You LITERALLY witnessed proof as 1/4 of the world basically shut down for the day. This would have been avoided in many cases if the update was vetted by the local IT teams.
So CrowdStrike shouldn’t allow real time threat protection? That’s what caused the issue. It needs to update its threat library to do deal with any day 1 attacks. It’s one of the main reasons it’s used
Forced updates should be illegal.
Believe it or not, CrowdStrike’s model forces updates and people pay a lot of money for it to “handle things” for them. I had to deploy it at a previous employer about 8 years ago. It was stupid.
No one forces you to update. People simply choose to run an OS where automatic updates are the default.
And that OS also lets you permanently disable automatic updates. It just doesn’t give you a straight-forward GUI option for it.
Critically wrong in this case. Crowdstrike updates push outside of, and regardless of, os settings. This wasn’t, and never was, an os issue, it’s a crowdstrike issue. Good try though.
Tell me you don’t have a clue what you are talking about without telling me.
Problem is, an individual computer user often isn’t the victim of that computer’s lack of updates.
Any time a site you like has been DDOSed, it’s often from thousands of zombie computers infected by some malware that their owners aren’t aware of. Those infections are generally made possible by unclosed security holes. So, you know…not updating.
I’m fine being part of a botnet if that’s the trade off for not using windows 11. Just got it installed on my testing PC at work and I hate it so much.
Forced updates of an optional corporate anti-virus designed to immediately detect and distribute information on threats should be illegal?
Or is this just an unrelated comment?
You really don’t understand how many millions of hours of human effort force updates have destroyed.
Yes, there should always be, ESPECIALLY IN CORPORATE ENVIRONMENTS, a point where the client can vet and approve the update.
This recent Crowdstrike problem is proof of it. You LITERALLY witnessed proof as 1/4 of the world basically shut down for the day. This would have been avoided in many cases if the update was vetted by the local IT teams.
So CrowdStrike shouldn’t allow real time threat protection? That’s what caused the issue. It needs to update its threat library to do deal with any day 1 attacks. It’s one of the main reasons it’s used