Live data from Hacker News

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

thehftguy.com

141–150 of 285 posts

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

#141

Can someone explain to me why the protections that Falcon provides, are not provided by the OS itself? I am not completely naive, I've secured quite a few critical Linux servers, but with Windows it seems that there do not exist the same clear roles of security. Contrast with Red Hat or even Canonical, where is feels like I'm (correctly) fighting the security of the systems to get them into a state where my users can…

I read an article that stated that Microsoft lost an anti-trust court case against the EU in which the EU mandated that they allow third party competitors to provide this service. Microsoft has its own solution called Windows Defender. https://www.theregister.com/2024/07/22/windows_crowdstrike_k...

It's more nuanced than that. They have to provide the same APIs to third party security vendors that they use themselves.

They can come up with something more shielded as Apple has done, they just have to eat their own dog food and can't make an exception for defender. That's all.

Blaming the EU here is pure spin.

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

#143

Earlier quoted context omitted.

How do you actively detect a malware agent running in user space using stealth or a kernel. Authors of such are fully aware of Linux hardening like SELinux / AppArmor and work around it.

> How do you actively detect a malware agent running in user space using stealth Depending how advanced the attacker is, check the executing binary maps back to the actual expected name and location on disk. Make sure the executable and libraries used at runtime are the correct ones matching hashes of known good qualities. Ensure the process tree structure has an expected structure, ie "bash" isnt starting a process…

> [...]

> There are more, but thats the few off the top of my head.

And that is probably like 80% what EDR product will be doing, checking that the code that is executing is trustworthy and not doing some weird unexpected things.

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

#144
post #33
post #20

Earlier quoted context omitted.

The number of US tech businesses that are surprised they need, or think they can ignore the need, to obey employment and data protection laws when working in other jurisdictions is simply bonkers.

Well, it'd be a lot easier if most US entities understood that M/d/yy(yy) format is rare, or that default to Frankenstein degrees is pretty much the same/awkward (even Microsoft reset their weather widget to F on regular basis). The root of issue, not understanding local laws/culture, is very similar - surrounded by a vast market/culture (US +Canada) dulls your senses for the rest of the globe.

> f most US entities understood that M/d/yy(yy) format is rare

The worse offender on this I suspect it's Apple. Where half of their localization stuff doesn't work or works in a weird way

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

#145

Earlier quoted context omitted.

> Just look at the recent Boeing incident where people were killed, the company clearly misled the US authorities and settled only a $0.5B fine. The problem is when you fine a company, they will just turn around and offload that cost to their customers. Which in this case is the US government in a very large way. Boeing will make their part in the SLS a few billion more expensive again to offset it and even gain some…

You could force the company to pay the fine in the form of a % ownership stake in the company. Then if the company raises prices to hose the government, the extra profit flows back to the government in dividends.

That actually sounds pretty compelling...

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

#146

Earlier quoted context omitted.

If the uptime of 100% of your computers depends on a single vendor not writing software with bugs in it, you have a problem.

That would mean that you always need a fully redundant copy of everything based on entirely different OSes and software with no common component. That is obviously not realistic.

Building high-assurance systems is expensive. Anyone not doing so must accept the associated risks (which is fine, not everything needs to be high-assurance).

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

#147

What is hilarious to me is how the US government or courts doesn't seem to give a shit about this. Corporativism in US is a thing. Companies can brick hospital systems killing patients, drive self-driving cars and run over people but don't get sued, and if they do, they settle for very little. Just look at the recent Boeing incident where people were killed, the company clearly misled the US authorities and settled o…

If you want this to change, ban the CEO from holding a similar job or sitting on a board. If that doesn't work ban them from Aspen.

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

#148
post #115
post #101

Earlier quoted context omitted.

what if the fine was giving up some shares to the government? With such a rule, after enough fines, the company would basically automatically become a public company.

Sounds too much like socialism to go anyhere.

It depends on who you want to punish, the shareholders, who have to give up their shares ... or the company, which doesn't really give a crap, as a whole.

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

#149
post #14

Holy shit (hits the fan). For sure CrowdStrike will be held accountable in several countries, but I believe that some conclusions need to be drawn also from a customer/user perspective. - Is it reasonable to grant such privilege access to a piece of software that ultimately is a black box ? - Is it reasonable to put a Microsoft / Commercial / Closed source OS in critical infrastructure ? If not considered as critical…

> - Is it reasonable to have more than 70% of the computers/servers that run important infrastructure on the same OS / software ? How about the mitigation of the risks etc… This is the problem as far as I'm concerned. Industry "best practice" is "use the same thing everywhere" A diverse ecosystem is the best defence. You could run 100% FreeBSD and be hit by say a hidden kernel bug which occurs on Jan 15th 2027 when u…

You would have a hard time denying 20% of users their first choice.

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

#150

Earlier quoted context omitted.

If the uptime of 100% of your computers depends on a single vendor not writing software with bugs in it, you have a problem.

That would mean that you always need a fully redundant copy of everything based on entirely different OSes and software with no common component. That is obviously not realistic.

No. You just need to not update them all at the same time.
Post reply on HN