Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is IEC 62443?

IEC 62443 is the international standard series for the security of industrial automation and control systems, covering the asset owner, the integrator, and the product supplier in one coherent framework.

Illustration for the cybersecurity term IEC 62443
Home / Blog / Cybersecurity Terms / What Is IEC 62443?
17 November 2026

What Is IEC 62443?

What Is IEC 62443?

IEC 62443 is the standard the industrial world settled on. Developed jointly by the International Society of Automation and the International Electrotechnical Commission, it is a series of documents rather than a single standard, and its distinguishing feature is that it assigns responsibilities to three different parties: the asset owner who operates the plant, the system integrator who builds and commissions it, and the product supplier who makes the controllers, software, and devices. Most security frameworks address only the operator, which is why industrial procurement was impossible to write before this existed.

The Four Groups

Zones and Conduits

The central design idea is simple enough to draw on a whiteboard. Group assets with shared security requirements into zones. Define every communication path between zones as a conduit, with a stated purpose, a defined protocol set, and a control that enforces it. Assess the risk for each zone, derive a target security level, and then design to meet it.

The method in 62443-3-2 works through it systematically: identify the system under consideration, perform an initial high-level risk assessment, partition into zones and conduits, decide whether the initial risk already exceeds tolerance, perform a detailed risk assessment per zone, and document the resulting target security levels and the countermeasures that achieve them. The output is a document that an engineer, a procurement officer, and a regulator can all use, which is the real value.

Foundational Requirements and Security Levels

Seven foundational requirements run through the whole series and give the framework its spine: identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events, and resource availability. Notice the order. Confidentiality sits fourth, and availability last in listing but first in practice; this is not an accident, and it is the clearest signal that the standard was written by people who run plants.

Security levels run from 0 to 4 and are defined by the adversary they resist rather than by a control count:

  1. SL 1: protection against casual or coincidental violation.
  2. SL 2: protection against intentional violation using simple means, low resources, generic skills, and low motivation.
  3. SL 3: protection against intentional violation using sophisticated means, moderate resources, system-specific skills, and moderate motivation.
  4. SL 4: protection against intentional violation using sophisticated means, extended resources, system-specific skills, and high motivation.

Levels come in three flavours: target, the level a zone needs; capability, the level a product or system can deliver; and achieved, the level actually realised once everything is installed and configured. The gap between capability and achieved is where most assessments live.

Certification and Where It Fits

Certification schemes exist for products, development processes, and sites, run through the ISASecure programme and national certification bodies under the IECEE arrangements. For suppliers, a 4-1 process certificate and 4-2 component certificates are increasingly a condition of tender. For asset owners, certification is less common than self-assessment against 2-1 and 3-3, and that is usually the right balance.

IEC 62443 does not replace the frameworks a UK operator is measured against. The NCSC Cyber Assessment Framework sets outcomes; IEC 62443 provides the engineering detail that demonstrates those outcomes in an industrial estate, and NIST SP 800-82 provides a free, readable companion. It is also becoming the reference point for European product regulation, as the Cyber Resilience Act drives manufacturers toward demonstrable secure development.

A caution worth stating: the series is large, parts of it cost money, and a programme that begins by buying every document and reading it in order will stall. Start with a 3-2 zone and conduit exercise on one plant, because it produces an architecture diagram, a risk register, and a procurement specification in a few weeks, and everything else hangs off those.

At Privia Security, we run zone and conduit assessments and standard-aligned reviews through our Regulation and Compliance Services.

FAQ – Frequently Asked Questions

Is IEC 62443 the Same as ISA-99?

It is the successor. The work began in the International Society of Automation as the ISA-99 committee and was renumbered as ISA/IEC 62443 when it was adopted internationally. Older documents and job adverts still say ISA-99, and the committee retains the name, but the current standards are published as IEC 62443 and that is what you should cite.

Which Part Should I Read First?

62443-3-2 if you are an asset owner, because the zone and conduit risk assessment method produces an architecture, a risk register, and a procurement baseline in one exercise. Suppliers should start with 62443-4-1 and 4-2. Integrators should start with 62443-2-4, since that is what their customers will contract against.

What Security Level Should I Target?

It depends on the consequence in each zone, and uniform targets are a common mistake. A safety instrumented system or a zone whose failure causes environmental or life safety harm justifies SL 3. Most general process zones sit at SL 2. Specifying SL 3 everywhere produces a design nobody can afford or operate, and the standard explicitly expects differentiated targets.

Does IEC 62443 Certification Prove a System Is Secure?

It proves a defined scope met defined requirements at a point in time. A 4-1 certificate means the supplier operates a secure development process; a 4-2 certificate means a component has stated security capability. Neither tells you how the system was configured, segmented, or maintained on your site, which is why achieved security level, not capability, is the figure that matters.

Related Terms

You May Be Interested In These

What Is AI Agent Security?

Cybersecurity Terms

17 November 2026

What Is AI Agent Security?

Read More
What Are OWASP MASVS and MASTG?

Cybersecurity Terms

17 November 2026

What Are OWASP MASVS and MASTG?

Read More