Interesting, so apparently the #CTO of #Cloudstrike is #GeorgeKurtz, the same CTO who oversaw the fiasco about 10 years ago when #McAfee #antivirus was falsely flagging a crucial system file within #Windows, and apparently he had been bragging about just how fast they were getting these updates out... Despite the fact that the updates in question included code that ran inside of kernel space at startup, meaning if they didn't run properly on any system that system would crash before it could even get to the login screen.
So clearly we know that there was some bad management involved, and while it was definitely not the fault of just one person, this offers us some insight into what the #management problem was: a focus on speed over carefulness, in a situation where a broad range of critical infrastructure could be crashed if a mistake was made.
"Move fast and break things" indeed...
https://cxotoday.com/news-analysis/microsoft-cloudstrike-lessons-from-history/