Crowdstrike took a day to respond, and then asked for a bunch more proof (beyond the above) that it was their fault. They acknowledged the bug a day later, and weeks later had a root cause analysis that they didn't cover our scenario (Debian stable running version n-1, I think, which is a supported configuration) in their test matrix. In our own post mortem there was no real ability to prevent the same thing from happening again -- "we push software to your machines any time we want, whether or not it's urgent, without testing it" seems to be core to the model, particularly if you're a small IT part of a large enterprise. What they're selling to the enterprise is exactly that they'll do that.

Wizards,

I know the last week has been intense, with the buzz about a potential acquisition. While we are flattered by offers we have received, we have chosen to continue on our path to building Wiz.

Let me cut to the chase: our next milestones are $1 billion in ARR and an IPO.

Saying no to such humbling offers is tough, but with our exceptional team, I feel confident in making that choice.

The market validation we have experienced following this news only reinforces our goal – creating a platform that both security and development teams love. We are grateful for the faith our employees, investors, and customers have in us as we build the best cybersecurity company in the world.

Thank you for your hard work and focus during these days, which helped us stay on track and finish the quarter stronger than ever. As we always say: LFG.

Assaf