Even if this is not a #cyberattack, I think it could be an attack scenario,
We had a bitter experience in #solarwinds where customers were poisoned by malicious updates, we are talking about a much bigger service interruption in the current live situation. I see a laxity on both the vendor #Crowdstrike and the customer side, and I think #Microsoft Windows is waiting open to such vulnerabilities, even if it is not the perpetrator. Assuming that this problem is caused by a personal error;
Process management (especially #changemanagement process) should not be dependent on individuals, this can be caused by user errors (intentional/accidental), which have been increasing in recent years, or it can be caused by compromised accounts and insider threats.
"Automation Update Management" or "Automated Patch Management" in patch management strategy, especially on #Windows servers, should be reviewed, and processes should be designed and implemented according to the worst-case scenarios.
Even if the technologies working together are competitors, cooperation should be increased for customer satisfaction,
Problems that don't have such earth-shattering consequences are always blamed on others, but when the consequences are severe, unfortunately the spear doesn't fit in the sack.
It's not over yet, but let it be a lesson for all of us.
CrowdStrike is actively working with customers impacted by a defect found in a single content update for Windows hosts. Mac and Linux hosts are not impacted. This is not a security incident or cyberattack. The issue has been identified, isolated and a fix has been deployed. We refer customers to the support portal for the latest updates and will continue to provide complete and continuous updates on our website. We further recommend organizations ensure they’re communicating with CrowdStrike representatives through official channels. Our team is fully mobilized to ensure the security and stability of CrowdStrike customers.