Isa-tr84.00.09 -

Cybersecurity wasn’t part of the equation. Why? Because the assumption was that safety networks were air-gapped, proprietary, and obscure. No hacker would bother with a Beckhoff controller or a Triconex when they could go after corporate payroll.

The industry’s answer then was a shrug. The answer today, after TRITON, PIPEDREAM, and a dozen state-sponsored near-misses, is: catastrophe . For decades, functional safety engineers operated under a sacred pact: A safety system (SIS) must be fail-safe, deterministic, and isolated. If you pulled the logic solver’s plug, the valves went to their safe position. If a sensor failed, the system defaulted to shutdown. Safety was about physics, random hardware failures, and reliability. isa-tr84.00.09

In the world of industrial control systems (ICS), two documents get all the glory. There’s ISA-62443 (IEC 62443) , the sprawling, multi-part behemoth that serves as the constitution for industrial cybersecurity. And then there’s ISA-84 (IEC 61511) , the bible of functional safety (SIS/SIL). They sit on opposite ends of the engineering bookshelf, rarely speaking to one another. Cybersecurity wasn’t part of the equation