So when you go to a restaurant, you also go into the kitchen, review the origin seal of every ingredient, the tools using to prepare the dish, perform a background check of each kitchen employee, before commiting to anything on the menu...

The info was basically on the crowdstrike whitepapers. You don't have to know the origin seal of every ingredient, but if you are allergic to peanuts, you ask if said dish has peanuts in it.

Asking what the falcon agent does, how it is updated, what it has access to, and if it can be remotely controlled is part of the job of any IT engineer / manager who plans to purchase a license for crowdstrike. If you don't, you aren't doing your job.

And when the dish has peanuts after all?

I guess it is your fault, because you failed to do the allergic chemical test, before eating it.

That is not an analogy that translate to the crowdstrike incident.

It sure does, given the reasoning they aren't to blame, rather their customer.

Yup, he also stops and inspects any civil engineering he has to use (like bridges), and he definitely does have qualifications to perform those.

You can always go to a different restaurant given it's garbage, you can't go to another delta airlines.

I am quite sure there are other airlines.

More like when you are a restaurant owner you do those things.

And when one fails to do them, the customer will sue the owner when things go south.

Yeah and customers are rightly getting money back from Delta et al. Seems to hold up?

Gross negligance vs. liability waiver - fight

Why even trust the OS at this point? Get the budget to write your own, in-house one. It's not like economies of scale really exist.

I only deploy open source reproducibly built operating systems with high accountability.

No one acting alone can deploy a change to mission critical systems I design.

This is just basic supply chain integrity.