IEC 62443

IEC 62443: The Standard Series for OT Security in Industry and Critical Infrastructure

IEC 62443 is the international standard for the cybersecurity of industrial automation and control systems. This page explains the parts of the series, zones and conduits, security levels and certification schemes, and shows how to use the standard as evidence under the Cyber Resilience Act and NIS-2.

Last reviewed 26 October 2026Reviewed by David Kleinz, CISSPReading time 11 min
In short

IEC 62443 is the series of standards for the cybersecurity of industrial automation and control systems. It defines zones and conduits, four security levels and requirements for asset owners (2-1), integrators (2-4), systems (3-3) and product suppliers (4-1, 4-2). Manufacturers use 4-1 and 4-2 as evidence under the CRA, operators use 2-1 and 3-3 for NIS-2.

What is IEC 62443?

IEC 62443 is the internationally authoritative series of standards for the cybersecurity of industrial automation and control systems (IACS). It was originally developed by the ISA (International Society of Automation) as ISA-99 and is now maintained jointly by ISA and IEC, hence the designation ISA/IEC 62443. Its subject is operational technology (OT): controllers (PLCs), control systems (SCADA, DCS), field devices, industrial networks and the processes used to develop, integrate and operate these systems.

The decisive difference from classic IT standards such as ISO/IEC 27001: IEC 62443 does not only describe a management system, it defines concrete technical requirements for systems and components, graded by protection needs. To do this, the series introduces three concepts you should know: partitioning a plant into zones and conduits, classification into security levels (SL 1 to 4) and the seven foundational requirements from which all technical requirements are derived.

For companies in the DACH region, the standard has become considerably more binding in recent years. The Cyber Resilience Act requires manufacturers of connected industrial components to run a secure development process and deliver secure product properties. NIS-2 and the BSIG oblige operators to secure their production networks in line with the state of the art as well. In both cases, IEC 62443 is the benchmark that auditors, customers and authorities use in OT environments.

Who IEC 62443 applies to: asset owner, system integrator, product supplier

IEC 62443 is a standard, not a legal act. It becomes binding through contracts, tenders, certification and, increasingly, through references in legislation. The series distinguishes three roles, each with its own parts of the standard:

  • Asset owner (operator): The company that operates the plant and is responsible for its secure operation, for example a chemical plant, an energy utility or a production line in mechanical engineering. The operator defines the protection needs and runs the security programme (Part 2-1).
  • System integrator (service provider): Designs, builds and maintains the automation system on behalf of the operator. Integrators and maintenance providers are subject to the process requirements of Part 2-4 and the system requirements of Part 3-3.
  • Product supplier (manufacturer): Develops components such as controllers, HMIs, network devices or embedded software. Part 4-1 (development process) and Part 4-2 (technical component requirements) are relevant here.

In practice, many companies occupy several roles at once. A machine builder is the product supplier of its machine controller, the system integrator of the overall system at the customer's site and the asset owner of its own production.

The parts of the standard at a glance

The series is organised in four groups: General (1-x), Policies and Procedures (2-x), System (3-x) and Component (4-x). The following table shows the parts that most frequently play a role in projects.

PartTitle (short form)AudienceContent
IEC TS 62443-1-1Terminology, concepts and modelsAll rolesTerminology, reference model, zones and conduits, foundational requirements, security level concept.
IEC 62443-2-1Security programme for asset ownersOperatorsRequirements for an IACS security programme: organisation, policies, risk management, operation and improvement. Revised edition 2024.
IEC 62443-2-4Requirements for service providersIntegrators, maintenance providersProcess capabilities of the service provider for integration and maintenance, such as hardening, patch management, backup, remote access, network design.
IEC 62443-3-2Security risk assessment for system designOperators, integratorsProcedure for partitioning into zones and conduits, risk assessment per zone, definition of the target security level (SL-T).
IEC 62443-3-3System security requirements and security levelsIntegrators, operators, system suppliersTechnical system requirements (SRs) per foundational requirement, graded by SL 1 to 4.
IEC 62443-4-1Secure product development lifecycleProduct suppliersProcess requirements for development: security requirements, secure design, implementation, testing, vulnerability management, update process, security documentation.
IEC 62443-4-2Technical security requirements for componentsProduct suppliersTechnical requirements (CRs) for embedded devices, host devices, network devices and software applications, graded by SL 1 to 4.

Zones and conduits: segmentation as the core principle

The core principle of IEC 62443 is partitioning an automation system into areas with the same protection needs. A zone is a group of logical or physical assets that share common security requirements, for example a manufacturing cell, a safety system or the control system of a plant. A conduit is the communication channel between two zones, such as the connection between the production network and corporate IT, or a remote maintenance access.

Part 3-2 describes the procedure: first, the system is partitioned into zones and conduits, taking operational and protection needs into account. Each zone and conduit then undergoes a detailed risk assessment from which the target security level (SL-T) is derived. This yields the requirements for network architecture, firewalls, data diodes, access control and monitoring. The result is a documented security architecture that you can demonstrate to auditors and authorities.

Practical note: Zones should follow protection needs and responsibility, not the network structure that has grown over time. Safety systems, engineering workstations and remote maintenance access almost always belong in separate zones with their own conduit.

Security levels SL 1 to 4 and the 7 foundational requirements

The security levels describe the type of attacker a system or component must be protected against. They are the link between risk assessment and technical requirements.

Security levelProtection againstTypical attacker
SL 1Casual or coincidental violationOperator error, unintentional misconfiguration
SL 2Intentional violation using simple meansAttacker with low resources, generic skills and low motivation
SL 3Intentional violation using sophisticated meansAttacker with moderate resources, IACS-specific skills and moderate motivation
SL 4Intentional violation using sophisticated means with extended resourcesAttacker with extended resources, IACS-specific skills and high motivation, such as state actors

The standard distinguishes three variants: SL-T (target) as the goal derived from the risk assessment, SL-C (capability) as the level a component or system is technically capable of, and SL-A (achieved) as the level actually reached in operation.

The security level is not expressed as a single number but as a vector across the seven foundational requirements (FR). Each FR groups a set of system requirements (3-3) or component requirements (4-2).

FRNameKey question
FR 1Identification and authentication control (IAC)Who is accessing: users, processes, devices? Password rules, certificates, MFA.
FR 2Use control (UC)What may the authenticated party do? Roles, permissions, session control, audit logs.
FR 3System integrity (SI)Are software, firmware and data unaltered? Signatures, integrity checks, malware protection.
FR 4Data confidentiality (DC)Is data protected in transit and at rest? Encryption, key management.
FR 5Restricted data flow (RDF)Does data only flow where it should? Segmentation, zone boundary protection, protocol filtering.
FR 6Timely response to events (TRE)Are incidents detected and reported? Logging, monitoring, alerting.
FR 7Resource availability (RA)Does the system remain operational under attack? DoS protection, backup, recovery.

An example: a zone with the vector SL-T {2 2 3 1 3 2 2} requires a higher level for system integrity (FR 3) and data flow (FR 5) than for confidentiality (FR 4).

Certification: ISASecure, TÜV and others

IEC 62443 can be certified by accredited bodies. The best-known programmes are:

  • ISASecure (ISA Security Compliance Institute): SDLA certifies the development process against 4-1, CSA certifies components against 4-2, SSA certifies systems against 3-3, and ACSSA certifies automation solutions at the operator against 2-1, 2-4, 3-2 and 3-3. There is a dedicated programme for IIoT components (ICSA).
  • TÜV organisations (such as TÜV SÜD, TÜV Rheinland, TÜV Nord) and other test institutes offer certification for processes (2-4, 4-1), components (4-2) and systems (3-3), partly as ISASecure-accredited laboratories, partly under their own certification mark.

Certification is not an end in itself. It pays off when customers demand it in tenders, when you as a manufacturer want to demonstrate process maturity to many customers at once, or when you use the certificates as a building block for a conformity assessment under the CRA.

Status as of 26 October 2026: IEC 62443 certification replaces neither the CE conformity assessment under the CRA nor the evidence required under Section 39 BSIG. It is a robust building block, not a presumption of conformity. Harmonised standards for the CRA have not yet been cited in the Official Journal.

Relation to CRA and NIS-2: where IEC 62443 serves as evidence

For manufacturers, the link to the Cyber Resilience Act (Regulation (EU) 2024/2847) is the most important reason to engage with IEC 62443. The essential requirements in Annex I of the CRA largely coincide with what 4-1 (process) and 4-2 (product properties) have required for years. For operators, 2-1, 3-2 and 3-3 provide the structure to implement the risk management measures under Section 30 BSIG in OT environments.

Legal requirementMatching part of IEC 62443What the part contributes
CRA Annex I Part I: secure product properties (secure by default, access control, encryption, integrity, logging, secure updates)IEC 62443-4-2Concrete technical component requirements per foundational requirement, graded by SL; evidence via test reports and SL-C.
CRA Annex I Part II: vulnerability handling (SBOM, CVD policy, security testing, updates)IEC 62443-4-1Practices for vulnerability management, security testing, update process and security documentation within the development process.
CRA Article 13(2): cybersecurity risk assessment of the productIEC 62443-4-1 (threat modelling) and 3-2Methodology for threat model and risk assessment that can be referenced in the technical documentation under Annex VII.
CRA Article 32, Annex III: conformity assessment of important products (such as industrial firewalls, routers, microcontrollers with security functions)IEC 62443-4-1 and 4-2 (certificate)Existing certificates shorten the assessment by notified bodies; full presumption of conformity only through harmonised standards (expected from Q4 2026 to 2027).
NIS-2 / Section 30(2) no. 1 BSIG: risk analysis and security policiesIEC 62443-3-2Zone and conduit model and risk assessment per zone as the OT risk analysis.
Section 30(2) nos. 2, 3, 6, 9 BSIG: incident handling, business continuity, effectiveness assessment, access control and asset managementIEC 62443-2-1Establishment and operation of an OT security programme that can be integrated into an ISMS under ISO/IEC 27001.
Section 30(2) nos. 4 and 5 BSIG: supply chain security, security in acquisition, development and maintenanceIEC 62443-2-4 and 4-2Requirements catalogue for integrators and service providers; procurement requirements for components (SL-C).
Section 30(2) nos. 8 and 10 BSIG, Section 31 BSIG: cryptography, MFA, attack detection for critical facilitiesIEC 62443-3-3System requirements for authentication (FR 1), confidentiality (FR 4) and event detection (FR 6) per security level.

Important for context: this mapping is a technical correlation, not a legal presumption of conformity. Whether a company falls under NIS-2 is clarified by the NIS-2 applicability check; whether a product falls under the CRA, by the CRA applicability check. A side-by-side comparison of both legal acts is available in CRA vs NIS-2.

Implementing IEC 62443: a 4-step approach

Whether operator or manufacturer, implementation follows a proven pattern. The key is to start with the protection needs, not with the product list.

01
Clarify role and scope

Which roles do you occupy (asset owner, system integrator, product supplier)? Which plants, product families and customer requirements are affected? Which legal obligations under CRA and NIS-2 come on top?

02
Risk assessment and target security level

Partitioning into zones and conduits according to 3-2, risk assessment per zone and definition of the SL-T. Manufacturers derive the intended SL-C of their components from the deployment context and threat model.

03
Gap analysis against 2-1, 3-3, 4-1 or 4-2

Comparison of the current state with the requirements of the relevant part of the standard. The result is a prioritised list of measures with effort, responsibility and form of evidence.

04
Implementation, evidence and operation

Implement technical and organisational measures, build up documentation, certify if desired. Then: patch management, monitoring and regular effectiveness reviews as an ongoing process.

Typical mistakes are an SL-T set too high across the entire plant (expensive and not achievable), segmentation that exists only on paper, and components that offer SL-C 2 but are operated with default passwords.

Next steps

If you want to know where your plant or product family stands against IEC 62443, an assessment according to 2-1 and 3-2, or a gap analysis against 4-1 and 4-2, is the right starting point. Blue Panther carries out both and links the results directly to your obligations under the CRA and NIS-2. Get in touch, and we will clarify scope, effort and a sensible sequence in an initial consultation.

Frequently asked questions

Is IEC 62443 legally mandatory?

No. IEC 62443 is a standard, not a legal act. It becomes binding through contracts, tenders and certification. The CRA and the BSIG (NIS-2) require the state of the art, and in OT environments IEC 62443 is the recognised benchmark for it.

Which part of IEC 62443 applies to manufacturers?

Product suppliers work with Part 4-1 (secure development lifecycle) and Part 4-2 (technical component requirements). Both can be certified, for example through ISASecure SDLA and CSA, and serve as building blocks of evidence for Annex I of the CRA.

What does security level 2 or SL 2 mean?

SL 2 protects against intentional attacks using simple means by attackers with low resources and generic skills. SL 1 only covers casual or coincidental violations, while SL 3 and SL 4 address targeted attackers with IACS-specific knowledge and substantial resources. The level is expressed as a vector across the seven foundational requirements.

What are zones and conduits?

A zone groups assets with the same protection needs; a conduit is the communication channel between zones. Part 3-2 describes how to partition a plant into zones and conduits, assess the risk per zone and derive the target security level from it.

Does IEC 62443 certification replace CE marking under the CRA?

No. The conformity assessment under Article 32 CRA is still required. A certificate against 4-1 and 4-2 provides robust evidence for the technical documentation and shortens the assessment. A presumption of conformity only arises through harmonised standards, which as of 26 October 2026 have not yet been cited in the Official Journal.

Do operators under NIS-2 need to implement IEC 62443?

Section 30 BSIG requires risk management measures in line with the state of the art, including for production networks. IEC 62443-2-1 and 3-2 provide the structure for risk analysis, segmentation and a security programme in OT. Certification is not required for this; a documented assessment effectively is.

Glossary

IACS
Industrial Automation and Control Systems: control and automation systems including hardware, software, network and personnel that operate an industrial process.
OT
Operational Technology: hardware and software that monitors and controls physical processes, such as PLCs, control systems, field devices and industrial networks.
Asset owner
Operator of a plant who is responsible for its secure operation and defines the protection needs; addressed by IEC 62443-2-1.
Integrator
Service provider that designs, builds and maintains an automation system on behalf of the operator; addressed by IEC 62443-2-4 and 3-3.
Product supplier
Manufacturer of components such as controllers, HMIs, network devices or software; addressed by IEC 62443-4-1 and 4-2.
Zone
Group of logical or physical assets sharing common security requirements, for example a manufacturing cell or a safety system.
Conduit
Communication channel between two zones through which data flows are controlled and secured, such as a firewall boundary or a remote maintenance access.
Security level (SL)
Four-tier classification of the attacker class a system or component is protected against; expressed as a vector across the seven foundational requirements.
SL-T, SL-C, SL-A
Target (derived from the risk assessment), Capability (technical capability of a component or system) and Achieved (level actually reached in operation).
Foundational requirement (FR)
One of seven basic requirements (identification and authentication, use control, system integrity, data confidentiality, restricted data flow, timely response to events, resource availability) from which all technical requirements are derived.
ISASecure
Certification programme of the ISA Security Compliance Institute for development processes (SDLA, 4-1), components (CSA, 4-2), systems (SSA, 3-3) and automation solutions (ACSSA).
Defense in depth
Layered defence across several independent protection levels, implemented in IEC 62443 through zones, conduits and graded security levels.
Cite as: Blue Panther GmbH (David Kleinz): “IEC 62443: The Standard Series for OT Security in Industry and Critical Infrastructure”, panther.blue, as of 26 October 2026, https://panther.blue/en/iec-62443/

Sources and references

  1. ISA/IEC 62443 Series of Standards, ISA
  2. IEC 62443-3-3:2013, IEC Webstore
  3. IEC 62443-4-2:2019, IEC Webstore
  4. ISASecure Certification Programs
  5. BSI ICS Security Compendium (PDF, German)
  6. Regulation (EU) 2024/2847 (CRA), EUR-Lex
  7. Section 30 BSIG Risk management measures, gesetze-im-internet.de (German)
David Kleinz
David Kleinz
Founder and Managing Director, Blue Panther GmbH · CISSP · ISO/IEC 27001 Lead Auditor
Author profile →

Let's talk about your project.

A first assessment within days, without obligation and in confidence. Consulting in English and German.

Get in touch