IEC 62443 is the international family of standards for the security of industrial automation and control systems. It runs to more than ten separate documents, so many people never even try to use it. Its practical value rests on a few core concepts, though, and you can understand those without reading the whole thing.
This article explains the part a plant actually uses.
Why OT needs its own standard
ISO 27001 covers the information security management system and works well in IT environments. OT is different:
- availability and human safety come first, ahead of confidentiality,
- equipment stays in service for 15-25 years, not 3-5,
- patching needs a planned shutdown and is often impossible,
- the protocols have no concept of authentication.
IEC 62443 starts from these characteristics. It also gives the plant engineer, IT, the auditor, and the equipment supplier a shared language, and that is worth at least as much as the technical content.
How the family is structured
It splits into four groups, and most organizations need only two of them.
| Part | Who it is for | Content |
|---|---|---|
| 62443-1-x | everyone | Concepts, models, terminology |
| 62443-2-x | asset owners | Security program, policies, supplier management |
| 62443-3-x | system designers | Zones, conduits, Security Levels, system requirements |
| 62443-4-x | manufacturers | Secure development, product requirements |
If you are an asset owner, 2-1 (security program) and 3-2 (risk assessment and zone design) are the two documents you will work with. Part 4 comes up when you buy equipment and want to know what security capabilities to demand from the supplier.
The zone and conduit model
This is the most important practical tool in the standard.
Zone: a group of assets that share the same security requirements. Assets are grouped by risk and function, regardless of where they physically sit. All the controllers on a production line, for example, go into one zone, because they run the same process at the same criticality.
Conduit: the communication between zones. A conduit is more than cabling. It is a defined, restricted, and controlled data path. For every conduit you record what traffic may cross it, in which direction, and which control protects it.
The basic rule: anything not explicitly permitted on a conduit is denied. Zero Trust microsegmentation follows the same principle; the standard simply stated it in industrial terms, two decades earlier.
Three layers from top to bottom: IT, industrial DMZ, and OT. The IT layer holds the office network and the supplier. At the IT/OT boundary, two conduits lead to the intermediate systems in the DMZ: from the office network you can only reach the DMZ, not the plant directly; supplier remote access enters through a single point protected by MFA and logged. From the DMZ, separate conduits in the OT layer lead to production line 1, production line 2, and the safety systems (SIS), which are subject to the strictest rules. There is no conduit between the two production lines; they cannot reach each other.
- Conduit
- A controlled gateway between two zones. Only the defined traffic passes, in the defined direction.
- ✕No conduit
- The two zones cannot reach each other.
- Traffic
- Allowed traffic is inspected at the gate; blocked traffic stops.
How to define zones
The levels of the Purdue model are a good starting point, but zones are more fine-grained than that.
- Start with the IT/OT boundary. This is the most important zone boundary. The industrial DMZ goes here, holding the replicated historian, the jump server, and the file transfer system. There is no direct traffic between the office network and the plant.
- Separate the production lines or cells. If one line is compromised, the attack should not spread to the next.
- Pull out the safety systems (SIS). They always get their own zone, with the strictest controls.
- Handle remote access separately. The supplier maintenance conduit is a path of its own, tightly controlled.
Security Level: how strong it needs to be
The standard defines five levels, based on how capable an attacker the zone has to withstand.
| Level | Protects against | Example |
|---|---|---|
| SL 0 | No requirement | Non-critical auxiliary system |
| SL 1 | Accidental error, negligence | Pressing the wrong button, misconfiguration |
| SL 2 | Simple means, low motivation | Opportunistic attacker, malware |
| SL 3 | Targeted attack, IACS-specific knowledge | Organized crime, industrial espionage |
| SL 4 | State level, significant resources | Nation-state actor |
The standard distinguishes three variants: SL-T (the target you want to reach), SL-A (what the assets actually achieve), and SL-C (what the product is capable of). The gap analysis is the difference between SL-T and SL-A.
In practice most industrial zones are SL 2, while critical process control and safety systems are SL 3. SL 4 is rare and typically found in national critical infrastructure. Not every zone needs a high level, which is what keeps the program affordable: the money goes where the risk is.
Where a plant should start
The order below is realistic, and every step produces a measurable result.
1. Asset inventory and communication matrix. Built through passive discovery from mirrored traffic. Without it, every later step is guesswork.
2. Risk assessment (per 62443-3-2). Process criticality, potential impact, threat scenarios. This tells you which SL-T each zone needs.
3. Zone and conduit design. In drawings and tables: which asset belongs to which zone, which conduits exist, and what may cross them.
4. Gap analysis for each zone.
5. Action plan. Industrial DMZ, segmentation, routing remote access through conduits, monitoring, asset hardening. Prioritized, because you cannot do everything at once.
How it relates to NIS2
If your organization falls under NIS2 and runs industrial environments, you do not have to choose between the two frameworks: on the OT side, IEC 62443 provides the technical language for implementing NIS2.
| NIS2 measure | IEC 62443 counterpart |
|---|---|
| 1. Risk analysis | 62443-3-2 risk assessment methodology |
| 4. Supply chain | 62443-2-4 supplier requirements |
| 5. Vulnerability management | 62443-2-3 patch management |
| 9. Access control, asset inventory | 62443-3-3 system requirements |
The auditor checks against NIS2, while the plant engineer thinks in 62443 terms, so with the mapping both sides have something to work with.
If you want to find out where you stand, our OT security assessment starts with an asset inventory and a communication map and continues with a full-depth risk analysis. OT network segmentation covers putting the zone model in place. We looked at the broader OT security picture in our ICS/SCADA article.