Live data from Hacker News

CrowdStrike will be liable for damages in France, based on the OVH precedent

thehftguy.com

201–210 of 285 posts

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#201

Earlier quoted context omitted.

There are 2 possible questions. (1) - Why is a crutch like "anti-virus" software needed? Essentially trying to reactively cat-and-mouse hostile software that the OS has let execute on the computer. (2) Why doesn't Windows provide AV? Question (1) is more interesting - and (2) is addressed by other comments. I think both MS and their customers have very seldom prioritized security over even small compromises in functi…

The cat-and-mouse game is between OS security features and hackers. AV software is not a crutch, it's an extra level of defense. All OS kernels are vulnerable to malware - this is a 100% given at this moment in history. The question is how to mitigate this problem, and AV is one component of that, as are firewalls, network-level intrusion prevention systems, and a whole host of other security software. Maybe some day…

I think the mental model that security is attained by adding more security features just leads to sprawling complexity and awful things like AV.

Secure operating system designs tend to simplify and take away stuff rather than add more bells and whistles.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#202

French here, and working for another french CSP. We lived the OVH incident live and saw the whole aftermath. OVH was held liable because of the data loss, not for the service interruption. Data loss is something irremediable, permanent, definitive. Some businesses were basically ruined from this incident because they had no more data to operate. To add insult to injury, they sold offsite backups in the datacenter lit…

IMHO it would send really wrong signals if this doesn't end up with CrowdStrike closing their doors... like if the largest outage in history was caused by you due to a config parser failing and it looks as far as I can tell that they didn't follow industry best practices when it comes to config/parsing handling and probably also didn't follow some best practices when it comes to kernel module programming then honestl…

They didn't follow testing or deployment best practices either.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#203

Earlier quoted context omitted.

IMHO it would send really wrong signals if this doesn't end up with CrowdStrike closing their doors... like if the largest outage in history was caused by you due to a config parser failing and it looks as far as I can tell that they didn't follow industry best practices when it comes to config/parsing handling and probably also didn't follow some best practices when it comes to kernel module programming then honestl…

> it would send really wrong signals if this doesn't end up with CrowdStrike closing their doors I thought the same until I saw the damage estimates. They’re in the single-digit billions. That’s well below CrowdStrike’s market cap. Unless we’re going hard for retributive justice, liability should be enough.

That's only a low-ball for fortune 500, it's a small part of the damage they done.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#204

Earlier quoted context omitted.

The cat-and-mouse game is between OS security features and hackers. AV software is not a crutch, it's an extra level of defense. All OS kernels are vulnerable to malware - this is a 100% given at this moment in history. The question is how to mitigate this problem, and AV is one component of that, as are firewalls, network-level intrusion prevention systems, and a whole host of other security software. Maybe some day…

I think the mental model that security is attained by adding more security features just leads to sprawling complexity and awful things like AV. Secure operating system designs tend to simplify and take away stuff rather than add more bells and whistles.

Is there an example of a real OS for desktops and servers that is secure from this point of view?

I think SeL4 might qualify, but that can only realistically be used for embedded applications, it doesn't have, at this time, many of the features you'd need to build, say, an HTTP API server for it.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#205

Earlier quoted context omitted.

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?

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." https://www.crowdstrike.com/terms-conditions/

Ok, replace MRI with ATM then.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#206

Earlier quoted context omitted.

Unfortunately, CrowdStrike decides when it's time to upgrade CrowdStrike software, not the admins.

1. Your IT department shouldn't buy a product that let a third party change files on your system remotely. This one is the basis of computer security. 2. Your IT department shouldn't buy a product that doesn't give you control on when updates are applied. These are 2 huge security failures from your IT department.

Automatic security updates are widely touted as the gold standard in IT security, at least for anything that is not a life-support system.

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#207

French here, and working for another french CSP. We lived the OVH incident live and saw the whole aftermath. OVH was held liable because of the data loss, not for the service interruption. Data loss is something irremediable, permanent, definitive. Some businesses were basically ruined from this incident because they had no more data to operate. To add insult to injury, they sold offsite backups in the datacenter lit…

IMHO it would send really wrong signals if this doesn't end up with CrowdStrike closing their doors... like if the largest outage in history was caused by you due to a config parser failing and it looks as far as I can tell that they didn't follow industry best practices when it comes to config/parsing handling and probably also didn't follow some best practices when it comes to kernel module programming then honestl…

I understand that CS doesn't draw much sympathies even before this happened - from myself included - and it is easy to pin point systemic issues to a single failure point and make it liable and financially responsible for all downstream failures.

But this only creates excuses for all other responsible players in this systemic issue - or society at large. Just to pick 1 example: I keep reading comments on how profoundly health care providers were affected and that lead to human life losses.

I understand that having "tech" involved in health or any sector is important but are we really wanting to build critical services that grind to halt or have huge efficiency impact when a single vendor fails? Are these service providers not responsible for thinking about failure modes?

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#209

Earlier quoted context omitted.

That only works when the company has full power to set prices unilaterally, i.e. when it has monopoly power. Which is a separate problem that should be prevented separately. If Cisco gets fined a billion dollars, it can't just hike up the price of a router, as it will lose plenty of business to Juniper/Arista/F5/etc.

They can in the short term because they have tons of companies way too invested in their ecosystem to change. See what VMWare did after the broadcom takeover. They did exactly that.

Then what's stopping them from charging more today, in the absence of any fine?

Re: CrowdStrike will be liable for damages in France, based on the OVH precedent

#210

Earlier quoted context omitted.

1. Your IT department shouldn't buy a product that let a third party change files on your system remotely. This one is the basis of computer security. 2. Your IT department shouldn't buy a product that doesn't give you control on when updates are applied. These are 2 huge security failures from your IT department.

Automatic security updates are widely touted as the gold standard in IT security, at least for anything that is not a life-support system.

I am talking about control, I am not talking about disabling automatisation of updates.

You can have automatic security updates with delay between non prod and prod environments so that you can detect failures or possibly intrusions.

Post reply on HN