Feels like a good time to repost this https://medium.com/quinn-norton/how-antisec-died-654abf6aeff7 About how CrowdStrike got started and the kind of nice, responsible dudes who started it.
Feels like a good time to repost this https://medium.com/quinn-norton/how-antisec-died-654abf6aeff7 About how CrowdStrike got started and the kind of nice, responsible dudes who started it. 5 comments
At some point we need to start investigating the body count and ruined lives linked to these outages. 911 service is down in some places in America. CrowdStrike is killing people today, but they will not have to answer for it. There's not criminal negligence if you're a technology company, and there needs to be. @quinn There is certainly something to be said about neglicence in technology, but I would not exclude the infrastructure organisations that created knowingly a single point of failure and handed the trigger to an external entity. @raucao @quinn About the "not forced" thing, they kind of are. 'HAE-NCF-1: There should be a unified endpoint management (UEM) [48] solution in place to Not any specific brand or solution, but to be honest is there a big worst case scenario difference between Crowdstrike and its competitors? I'm oversimplifying but all of them require more or less a centralized management console with full admin access to endpoints. |
I know I'm supposed to feel sorry for Crowdstrike rank and file. But I mostly feel sorry for their victims/customers.
I suppose I can also feel sorry for anyone who didn't understand what kind of company they went to work for, but they should be trying to get a job elsewhere by now.