Skip to main content
STANDARDS · INDUSTRIAL CYBERSECURITY

What Is IEC 62443?

IEC 62443 is the international series of standards for the cybersecurity of industrial automation and control systems. Developed by ISA and the IEC, it sets requirements for asset owners, system integrators and product suppliers, and defines zones and conduits, seven foundational requirements and four security levels.

01

What IEC 62443 is

IEC 62443 is a series of international standards for securing industrial automation and control systems (IACS): the controllers, HMIs, SCADA servers, networks and software that run physical processes. It is developed jointly by the ISA99 committee of the International Society of Automation, which publishes the same documents as ISA/IEC 62443, and by IEC Technical Committee 65. That is why the series is also searched for as ISA 62443 or ISA/IEC 62443.

Unlike IT security frameworks, IEC 62443 is written for systems where availability and safety come first. It is also unusual in splitting responsibility between the three groups involved in a plant: the asset owner who operates it, the system integrator who designs and builds it and the product supplier who makes the components. Each part of the series says what one of them must do.

It is the main reference for OT security programmes worldwide, is cited by NIST SP 800-82 and the NCSC Cyber Assessment Framework, and is a reference point for industrial products under the EU Cyber Resilience Act.

02

How the IEC 62443 series is structured

The series has four groups of documents. Some are full international standards and some are technical specifications or reports.

  • //
    Part 1: general. Terminology, concepts and models (62443-1-1), a glossary, conformance metrics and the security lifecycle.
  • //
    Part 2: policies and procedures. The asset owner’s security programme (62443-2-1), patch management (62443-2-3) and requirements for service providers such as integrators and maintenance contractors (62443-2-4).
  • //
    Part 3: system. Security technologies (62443-3-1), risk assessment and the design of zones and conduits (62443-3-2), and system security requirements and security levels (62443-3-3).
  • //
    Part 4: component. Secure product development lifecycle for suppliers (62443-4-1) and technical security requirements for components (62443-4-2).
03

Zones, conduits and the foundational requirements

IEC 62443-3-2 asks the asset owner to group assets with similar security needs into zones, and to treat every communication path between zones as a conduit that must be controlled. Each zone and conduit gets a target security level based on a risk assessment. In practice zones are usually built with VLANs and firewalls, and many designs start from the levels of the Purdue model.

Requirements throughout the series are grouped under seven foundational requirements (FRs): identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events, and resource availability. IEC 62443-3-3 turns them into system requirements, and IEC 62443-4-2 into component requirements for four types of component: software applications, embedded devices, host devices and network devices.

FAQ · 01
Why do IT security standards not fit OT systems?
Because the priorities differ. IT frameworks protect data first and assume frequent patching. OT systems put safety and uptime first and often run for 15 years or more, which is why IEC 62443 was written specifically for industrial control systems.
Read the full FAQ —
04

IEC 62443 security levels

Security levels describe how capable an attacker a zone or component is designed to resist. The same scale is used as a target (SL-T), as the capability of a component or system (SL-C) and as the level actually achieved once installed (SL-A).

Level Protects against Attacker means and skills Typical use
SL 0 No specific requirement Not defined Rarely chosen deliberately
SL 1 Casual or accidental violation No intent, mistakes and misuse Low-risk zones
SL 2 Intentional violation by simple means Low resources, generic skills, low motivation A common baseline for plant networks
SL 3 Intentional violation by sophisticated means Moderate resources, IACS-specific skills, moderate motivation Critical infrastructure zones
SL 4 Intentional violation by sophisticated means with extended resources Extended resources, IACS-specific skills, high motivation The highest-consequence zones

IEC 62443-4-1 adds a separate scale of maturity levels, from 1 (initial) to 4 (improving), for how consistently a supplier follows its secure development process.

05

Applying IEC 62443 to a project

On a typical project the parts are used in a fixed order, with the asset owner, integrator and suppliers each handling their own share.

  • //
    Assess the risk. The asset owner identifies the system under consideration and runs a high-level risk assessment (62443-3-2).
  • //
    Define zones and targets. Assets are grouped into zones and conduits, and each one is given a target security level.
  • //
    Compare capabilities. The integrator checks the security level each component and system can reach (SL-C) against the target and closes any gap with extra controls.
  • //
    Run and maintain. The security programme (62443-2-1), patch management and service providers’ processes keep the achieved level in place for the life of the plant.
06

What IEC 62443-4-2 asks of hardware

Component requirements are where the standard meets the hardware in a cabinet. For embedded and host devices, IEC 62443-4-2 covers points such as unique user identification, strong authentication, role-based access, protection of software and firmware integrity, secure update, audit logging, disabling unused ports and services, and recovery to a known secure state.

Several of these map directly to hardware features. A TPM stores keys and boot measurements, Secure Boot blocks unsigned code at start-up, and port authentication and VLANs enforce zones at the switch. Our managed industrial switches list IEEE 802.1X on most models, and TPM 2.0 is listed on many of our DIN rail PCs. These features support a design to IEC 62443, but certification applies to a specific product and version, so ask for the manufacturer’s certificate where a project requires one.

07

Quick answers on IEC 62443

IEC 62443: common questions

What is the difference between ISA 62443 and IEC 62443?

None in content. ISA publishes the documents as ISA/IEC 62443 and the IEC as IEC 62443. They are developed together by the ISA99 committee and IEC TC 65.

What are zones and conduits in IEC 62443?

The building blocks of segmentation. A zone is a group of assets with the same security needs. A conduit is a controlled communication path between zones.

Who can be certified to IEC 62443?

Products, systems, suppliers and service providers. Schemes such as ISASecure and IECEE certify components to 4-2, development processes to 4-1, systems to 3-3 and service providers to 2-4.

What is IEC 62443-3-3?

The system security requirements. It sets the requirements a complete control system must meet to reach each security level, grouped under the seven foundational requirements.

Is IEC 62443 mandatory?

Not by itself. It is voluntary, but customers, sector regulators and frameworks such as the NCSC CAF and the EU Cyber Resilience Act increasingly point to it.

We configure the industrial PCs, gateways and managed switches we supply with the security features each model supports enabled as standard, and pass on the manufacturer’s security documentation for your IEC 62443 assessment.