CIE vs. IEC 62443: How Cyber-Informed Engineering Relates to the OT Security Standard

Figure standing in a corridor of servers and floating data displays

CIE vs. IEC 62443: How Cyber-Informed Engineering Relates to the OT Security Standard

IEC 62443 specifies how to secure an industrial automation system. Cyber-Informed Engineering asks how much that system should be trusted to do. They answer different questions.

By Timothy Porritt · Porritt Inc. · November 21, 2026

Engineers who meet Cyber-Informed Engineering for the first time often ask whether it replaces IEC 62443. It does not. The two were built for different jobs, and a project that uses one without the other leaves a gap.

What IEC 62443 Is

IEC 62443 is the international series of standards for the security of industrial automation and control systems, developed by ISA and IEC. Its parts address different roles: security programs for asset owners, requirements for service providers and integrators, system-level risk assessment and security requirements, and secure development and technical requirements for product suppliers.

Its central design concepts are:

  • Zones and conduits. Group assets with similar security needs into zones and control the communication paths between them.
  • Security levels. Assign each zone a target level, from protection against casual violation up to protection against sophisticated attackers with extended resources, and select controls to meet it.
  • Foundational requirements. Seven categories, including identification and authentication, system integrity, restricted data flow, and resource availability.

It is specific, auditable, and supported by product certification.

What CIE Is

Cyber-Informed Engineering is an engineering practice from Idaho National Laboratory built on twelve principles. It begins with physical consequences and asks whether the process itself can be designed so that a compromised control system cannot cause them.

Side by Side

IEC 62443 CIE
Type Standard series with requirements Engineering practice with principles
Object The automation system The physical process and its functions
Main tools Segmentation, access control, hardening, secure development Engineered controls, simplification, manual operation
Conformance Certifiable Not a certification
Typical owner Automation and security engineers, vendors Process, mechanical, electrical, and controls engineers

Where They Overlap

The 62443 risk assessment process asks teams to consider consequences when setting target security levels, which is the natural entry point for CIE’s consequence analysis. CIE’s principles on information architecture, layered defenses, and supply chain line up with zones and conduits, defense in depth, and supplier requirements.

Where They Differ

IEC 62443 takes the process design as given and secures the automation around it. CIE treats the process design as a variable. If a scenario is severe enough, CIE’s answer may be a relief valve, a smaller pump, or the removal of a remote function, and none of those appear in a security requirements list.

Using Them Together on a Project

  • Run a CIE consequence review early, alongside the hazard analysis.
  • Engineer out or physically limit the worst scenarios.
  • Carry the remaining scenarios into the 62443 risk assessment to set zone boundaries and target levels.
  • Specify products and integrator practices to the relevant 62443 parts.
  • Confirm manual operation and recovery, which neither a firewall nor a certificate provides.

Why It Matters

Setting a high security level for a zone is a commitment to buy and maintain controls for decades. Reducing what that zone can do physically is often cheaper and never needs patching. See also CIE vs. Traditional OT Security and the CIE Implementation Checklist.

Related reading


Timothy Porritt is founder of Porritt Inc., building AI-powered tools for process safety, engineering compliance, and industrial operations. Based in Salt Lake City, Utah. Contact: timothy@porrittinc.com.

Scroll to Top