Lessons Learned from the CrowdStrike Incident | Analyst Chat 223

[@dahlia695]

If I were to speculate, it would be that Crowdstrike has probably become very top heavy and there were 50 managers from many levels breathing down the neck of some poor 15 year old hacker kid they "hired" to do the real work and when that kid passed out from exhaustion at his computer his head hit the keybord and prematurely initiated the update process. But yeah, crappy ring 0 code that doesn't validate it's input and is a key component of high value mission critical computing resources all over the world? WTF? And how come Apple can get rid of KEXTs but the EU won't let Microsoft do similar? This whole thing wreaks of incompetence in too many areas.

[@TimothyWhiteheadzm]

Actually, I am sure they have plenty of senior programmers involved throughout the development process. The problem was nevertheless a management one and the fact that the company has previously not been punished for such failure as they essentially have a monopoly on the market or there are simply no better alternatives. So, they concentrated on features and marketing not stability and reliability. As for the EU story, that is a myth.

[@raginald7mars408]

Who "learns" what? You? ...And who else??? We are hyper vulnerable on anything easy to create new chain reactions....