Yes, it was. Cloudstrike Falcon is a hybrid platform that combines local endpoint security with a centralized cloud-based AI back end, etc.
A decentralized solution would be enterprise software that is designed to be run on-premise in each location, self-contained.
What is the big difference? In a word, testing. In the large corporations where I have worked, patches to all enterprise software (including Windows itself) were never deployed directly into production environments. They were deployed to testing and QA environments first, to prove that they did not break anything or cause other problems - BEFORE they were ever deployed to prod. That methodology would have prevented this latest problem from occurring.
“But cloud computing costs less, and even though I’m giving ALL my data to the cloud provider, I can expense it in a way that saves a few bucks on taxes”
The only valid reasoning for cloud is security, and the people making cloud products are probably creating the security holes.
You’re misunderstanding. I didn’t say that they don’t have centralized systems. I’m saying the particular problem that just occurred is not a centralized problem. Which actually made it much more difficult to recover from.
They were deployed to testing and QA environments first, to prove that they did not break anything or cause other problems - BEFORE they were ever deployed to prod.
Right, but I'm sure this update was tested before being deployed... the problem is the dev doing the deploy sometimes does it wrong. Happens all the time, even more frequently in decentralized scenarios.
Yes, it was. Cloudstrike Falcon is a hybrid platform that combines local endpoint security with a centralized cloud-based AI back end, etc.
A decentralized solution would be enterprise software that is designed to be run on-premise in each location, self-contained.
What is the big difference? In a word, testing. In the large corporations where I have worked, patches to all enterprise software (including Windows itself) were never deployed directly into production environments. They were deployed to testing and QA environments first, to prove that they did not break anything or cause other problems - BEFORE they were ever deployed to prod. That methodology would have prevented this latest problem from occurring.
“But cloud computing costs less, and even though I’m giving ALL my data to the cloud provider, I can expense it in a way that saves a few bucks on taxes”
The only valid reasoning for cloud is security, and the people making cloud products are probably creating the security holes.
The cloud is too centralized for me.
Same.
You’re misunderstanding. I didn’t say that they don’t have centralized systems. I’m saying the particular problem that just occurred is not a centralized problem. Which actually made it much more difficult to recover from.
Right, but I'm sure this update was tested before being deployed... the problem is the dev doing the deploy sometimes does it wrong. Happens all the time, even more frequently in decentralized scenarios.
Assuming it isn't a "bad actor" situation anyway.