Re:CrowdStrike to Delta: Stop pointing at us
by chronid on Monday August 05, 2024 @11:13AM
(#41162121)
AFAIK crowdstrike can push updates at any time at any host. There are staging areas they may use, but don't have to (particularly for definitions updates).
Crowdstrike should have done a better job, but Delta chose them (to offload the responsibility and work) and now they're claiming foul. They knew the risk. This is a classic executive play of claiming the fault lies in the consultants/vendor and taking no responsibility.
Just shows how many planes would be falling out of the sky if there weren't federally mandated safety systems, secondary hydraulic circuits, and failover hot spares at nearly every layer of the stack. Delta should've had backup systems, just like their planes do.
Re:CrowdStrike to Delta: Stop pointing at us
by willhackett on Monday August 05, 2024 @12:40PM
(#41162930)
Okay, good to know. I always thought those embedded systems would be a real pain to maintain.
I'm not sure how "you should never use CrowdStrike" is an argument in CrowdStrike's favor.
I guess you're saying they shouldn't have outsourced in the first place? Which does sound like the correct conclusion in this case...
Re:CrowdStrike to Delta: Stop pointing at us
by chronid on Tuesday August 06, 2024 @06:54AM
(#41169594)
I'm not trying to defend CrowdStrike, but pointing to the fact Delta is the one maintaining and owning critical infrastructure and the executives trying to shift this responsibility onto someone else is the reason this happened in the first place. :)
Re:CrowdStrike to Delta: Stop pointing at us
by uncivilized on Monday August 05, 2024 @11:11AM
(#41162096)
No. The update was forced
In my mind, a quick test run of the update on a VM before letting it roll out globally would have revealed the BSOD boot loop.