Re:CrowdStrike will be liable for damages in France
by Retr0id on Thursday July 25, 2024 @07:58AM
(#41067560)
See the sentence I wrote just after that one.
Re:CrowdStrike will be liable for damages in France
by simiones on Thursday July 25, 2024 @08:29AM
(#41067855)
How is it someone other than CrowdStrike's fault that the systems failed again at every reboot until someone with physical access and know-how deleted the crashing driver manually from recovery mode? What should a company operating, say, an MRI machine protected by CrowdStrike have done to recover access in a reasonable amount of time?
Re:CrowdStrike will be liable for damages in France
by Retr0id on Thursday July 25, 2024 @08:38AM
(#41067937)
CrowdStrike's software should not be installed on an MRI machine, per CrowdStrike's own guidance:
"Neither the offerings nor crowdstrike tools are for use in the operation of [...] direct or indirect life-support systems [...] or any application or installation where failure could result in death, severe physical injury, or property damage."
Re:CrowdStrike will be liable for damages in France
by fabian2k on Thursday July 25, 2024 @09:00AM
(#41068171)
If the PC controlling an MRI crashes nothing will happen to the instrument itself. The data might be lost and you can't continue using the MRI until this is fixed, but not more. This would not violate these guidelines.
Re:CrowdStrike will be liable for damages in France
by simiones on Thursday July 25, 2024 @09:50AM
(#41068686)
Ok, replace MRI with ATM then.
Re:CrowdStrike will be liable for damages in France
by balderdash on Thursday July 25, 2024 @08:31AM
(#41067882)
For what it’s worth - I got the BSOD, once I got the email from IT with the instructions, it took me about 20min to apply the fix. Almost all of the company employees who were affected were able to easily apply a self help fix.
I could imagine this was not the case if you had to physically access remote servers, or didn’t have access to bit locker recovery keys
Not even remotely correct.
Most computers that were affected by the fault needed physical remediation via safe mode boot to fix the issue because they were not able to download a fix because of being stuck in a reboot loop. The understanding is that for most cases, the fix needed to be applied by an IT technician dispatched to physically access the computer.
A week or 168 hours later, there are still many, many computers out there that remain bricked by this fault because it is so heinously difficult to fix.