4 ms·
>> It's easy to blame CrowdStrike but that seems too easy on both the orgs that do this but also the upstream forces that compel them to do it. While orgs usin
by basisword 2y ago
>> It's easy to blame CrowdStrike but that seems too easy on both the orgs that do this but also the upstream forces that compel them to do it.
While orgs using auto update should reconsider, the fact that CrowdStrike don't test these updates on a small amount of live traffic (e.g. 1%) is a huge failure on their part. If they released to 1% of customers and waited even 24 hours before rolling out further this seems like it would have been caught and had minimal impact. You have to be pretty arrogant to just roll out updates to millions of customers devices in one fell swoop.
- lqet 2y agoWhy even test the updates on a small amount of live customers first? Wouldn't this issue already have surfaced if they tested the update on a handful of their own machines?
- basisword 2y agoI would hope they've done that and it passed internal QA. But maybe not a good idea to assume they're doing any sort of testing at all.
- greggsy 2y agoThey’d have rigorous test harnesses, but you can’t really account for the complexities of a highly configurable platform like Windows.
- kristjansson 2y agoThe prevalence of the issue makes it seem unlikely to have been caused by site-specific configurations