In case you don't feel like untangle the #CrowdStrike post-mortem, this is the gist of it:

"Based on the testing performed before the initial deployment of the Template Type (on March 05, 2024), trust in the checks performed in the Content Validator, and previous successful IPC Template Instance deployments, these instances were deployed into production."

In other words they simply didn't do e2e tests on the problematic update data that triggered the bug in their parser, because prev updates worked fine.

We still don't know how the malformed Template Instances were produced.

@buherator the 83 billion dollar company cant afford to do a dry run

@hajovonta Nominal resource consumption for endpoint security? :)

@hajovonta This may be related? https://www.bitsight.com/blog/crowdstrike-timeline-mystery

@buherator exactly this - I don’t know why people are praising this. Most of it was needless fluff.

@singe My impression was that they tried to stress how much testing they do at other places…