What can IT organizations learn from the software update that brought the world to its knees this week? Spoiler: a lot of things they should already know.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

The CrowdStrike disaster highlights critical lessons for IT and software management. Key takeaways include the dangers of relying on monocultures, the importance of quality assurance and staged rollouts, and the necessity of disaster recovery plans and enhanced monitoring. Implementing robust risk management strategies can help mitigate similar incidents in the future.

7 Urgent Lessons from the CrowdStrike Disaster

3. Quality Assurance Is Absolutely Necessary.

5) Disaster Recovery and Backups Are Must-Haves.

6. You Need Enhanced Monitoring and Incident Response.

If this is true:
<blockquote>
was a channel update that bypassed client’s staging controls and was rolled out to everyone regardless
</blockquote>
Then the rest of the article is moot. If that statement is true, CrowdStrike is 100% at fault for this. They should never do this kind of update/push without applying all of the other advice in the article. From automated testing to manual testing to rolling updates. Hell, dogfood the update!
I hope we actually hear a post-mortem on this from CrowdStrike so we will all know the truth. I really don’t care if people get fire, but I imagine someone will because this was huge.