Hello,
To be fair, he had just been newly appointed to the CTO position at McAfee, Inc,, and was responsible for GRC activities.
I would imagine that after his experience with the bad DAT 5958 rollout at McAfee, he would have made sure that CrowdStrike had a robust set of processes in place to ensure that this never happened again. That's part of what makes this so interesting: CrowdStrike must have had all sorts of controls in place to ensure that only a detection update which had passed through numerous quality gating procedures was released. Such processes are usually highly automated because they run 7x24x365, so you have all sorts of signalling and telemetry coming back at you to make sure all the tests are passed and everything's okay before you release.
What I'm thinking is that maybe this was going on, but there was failure in the alerting mechanism(s) and the update was pushed to production; think of it as being like an alarm light that didn't flash because its lamp bulb was burnt-out.
I will point out that this is all very speculative by me. I do not know personally know Mr. Kurtz, I was at McAfee from 1989-1995, and have worked at a competitor for the last 18 years. But during the past 35 years, every antivirus/antimalware/internet security/EPP/EDR/{insert marketing term du jour} company has put out a bad update at some time or another. None of us are immune to doing that, and they will happen again in the future.
Everyone in the industry is talking amongst themselves about what happened, and wondering if their own systems are vulnerable to such a problem, but it is difficult to check your systems if you don't know what you are checking them for. There has been all sorts of guessing about what happened, but until CrowdStrike releases their post mortem incident report with an analysis showing the root cause, that's exactly what it all is: guesswork, especially my comments.
Until then, the only thing I can really do is hope that CrowdStrike and their customers get their systems up and running as quickly as possible.
Regards,
Aryeh Goretsky