Did you know that buildings have doors that cannot be locked to prevent them from being opened from inside, because otherwise in case of a fire (or in the US, active shooter), people will die if they cannot exit the building?

Did you know that many industrial plants intentionally disable certificate revocation checks, because having a certificate expire on you for whatever reason is a sure-fire way to break the plant (and in some case possibly kill people), and overall a nuisance when trying to keep the plant running, while the threat it protects against can be handled elsewhere in the stack?

Security and safety are very often at odds - not just in emergency, but during regular operations.

By whom and for what?

The problem with security maximalist[0] ideology is that it does not accept reality for what it is: shit will happen. The correct way to handle risks is to mitigate them to some extent, and then insure (or self-insure) against the risk that remains[1].

Then, when the risk actually materializes and mitigations prove insufficient, you write off the damage and carry on with your day - and yes, perhaps even reward the executives who set up mitigations and insurance that allowed the business operations to continue undisturbed.

Only then, mitigations MAY be upgraded and insurance premiums adjusted, as an event happening is an important new evidence in risk estimate for it happening again.

That's how adults in the room handle security.

It's only the general public and cybersecurity people who see random events happening and decry that somehow it affects them and Somebody Needs To Be Accountable, and Someone Must Do Something About It.

--

[0] - Or should I say, cybersecurity maximalist, because in every other field except software, this is well understood.

[1] - Talking about regular security, that applies to 99.99%+ of businesses; the risk to life and limb is a special case with extra considerations, though it fundamentally doesn't change much about the framework.

One of the most well-read person I know recently revealed to me that the hundreds of books he read over past few years were actually mostly audiobooks - because it turns out that most of his dayjob is physical, low-cognitive-demand kind, and pairs perfectly with audiobooks, basically keeping his brain engaged while his muscles do the repetitive work.

Though I'm afraid things are getting worse, or at least it looked so a few years ago, back when I worked in this space. The hot thing in IIoT / Industry 4.0 was basically taking all webshit technologies and deploying them on industrial hardware, to "leverage mature innovation and OSS ecosystem" or such nonsense. The problem (one of many) being, once the engineers were done trimming excessive security measures that negatively impacted safety, they were still left with node.js running on industrial controllers, now even less secure in general than it was originally.

Vulnerabilities will always exist. Systems will always be hackable. You solve the problem by patching what you can, and cleaning up after what gets exploited, if and when it gets exploited.

What? Pinning a browser?

First thing it'll want to do after starting is update itself to newest version anyway.