sothware

IEC 62443 risk assessment explained: zones, conduits and security levels

· 5 min read · Sothware

A plain-English guide to how IEC 62443-3-2 structures an OT cyber risk assessment, from defining the system to zones, conduits and target security levels.

If you run or secure an industrial site, sooner or later someone will ask whether your control systems are "aligned with IEC 62443". This guide explains what that means in practice, focusing on the part most organisations start with: the security risk assessment in IEC 62443-3-2.

It is written for operations and engineering managers rather than security specialists. The standards themselves are paywalled and precise; treat this as a map, not a substitute.

What IEC 62443 is

IEC 62443 is the international series of standards for the security of industrial automation and control systems (IACS): the PLCs, SCADA, HMIs, engineering workstations and networks that run physical processes.

The series is organised in four groups:

  • General (62443-1-x): concepts, terminology and models, including the seven foundational requirements.
  • Policies and procedures (62443-2-x): what asset owners and service providers need in place, such as a security programme and patch management.
  • System (62443-3-x): security for a whole system, including the risk assessment (3-2) and the system security requirements and security levels (3-3).
  • Component (62443-4-x): secure product development and the technical requirements for individual devices and software.

If you own and operate a site, 3-2 and 3-3 are where the practical work happens.

The core idea: zones and conduits

Most industrial networks grew over decades. Many are "flat": once you are on the network, you can reach almost everything. IEC 62443 replaces that with structure.

  • A zone is a group of assets that share the same security requirements. A packaging line's controllers might be one zone, the plant's safety systems another, the historian and reporting servers a third.
  • A conduit is the logical grouping of communication channels that connects zones and shares common security requirements. Every path between zones goes through a conduit, so you can see and control what crosses the boundary.

Partitioning a system this way lets you protect each part to the level it actually needs, instead of applying the same controls everywhere and hoping.

Security levels: SL-T, SL-C and SL-A

IEC 62443 describes protection in security levels from 1 to 4. Paraphrasing the commonly cited definitions:

LevelProtects against
SL 1Casual or coincidental violation
SL 2Intentional violation with simple means, low resources, generic skills and low motivation
SL 3Intentional violation with sophisticated means, moderate resources, IACS-specific skills and moderate motivation
SL 4Intentional violation with sophisticated means, extended resources, IACS-specific skills and high motivation

The same level is used in three ways:

  • SL-T (target): the level a zone or conduit needs, decided by the risk assessment.
  • SL-C (capability): the level a system or component is able to provide.
  • SL-A (achieved): the level the system as built actually delivers.

The goal is simple to state: for every zone and conduit, the achieved level should meet the target. Where a component cannot reach it on its own, compensating countermeasures can close the gap, as long as they are documented.

Security levels are also expressed per foundational requirement, so a zone can need a higher level for one area than another. The seven foundational requirements are identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events, and resource availability.

The risk assessment workflow in IEC 62443-3-2

IEC 62443-3-2 sets out the assessment as a sequence of "zone and conduit requirements" (ZCRs). In outline:

  1. Identify the system under consideration (SUC). Draw the boundary of what you are assessing, and identify its perimeter and access points.
  2. Run an initial risk assessment. A high-level view of the worst realistic consequences if the system were compromised.
  3. Partition the system into zones and conduits. The standard calls out groupings to keep separate, including business and control assets, safety-related assets, temporarily connected devices, wireless devices, and devices connected through external networks.
  4. Compare the initial risk with tolerable risk. If it is already tolerable, the detailed step can be lighter.
  5. Perform a detailed risk assessment for each zone and conduit. Identify threats and vulnerabilities, determine consequences, likelihood and unmitigated risk, set the target security level, account for existing countermeasures, and work out the residual risk and any further countermeasures needed.
  6. Document the security requirements, assumptions and constraints. Including the zone and conduit drawings, the operating and threat environment, tolerable risk and regulatory requirements.
  7. Get asset owner approval. The people accountable for the system sign off the results.

The output is not just a report. It is a structured description of the system, its zones and conduits, and a target security level for each, which then drives the technical requirements in 62443-3-3.

Describing threats: MITRE ATT&CK for ICS

Step 5 asks you to identify threats, and teams often describe them inconsistently. MITRE ATT&CK for ICS helps. It is a public knowledge base of the tactics and techniques adversaries use against industrial control systems, organised into twelve tactics, from Initial Access and Execution through to Inhibit Response Function, Impair Process Control and Impact.

Mapping each threat in your register to ATT&CK for ICS techniques gives engineers, security staff and auditors the same vocabulary, and makes it easier to check which threats your countermeasures actually address.

Where it goes wrong

The method is sound. The problems are usually practical:

  • The asset list, threat list and risk register live in different documents. They drift apart, and the register stops describing the real system.
  • Zones are drawn on paper but not enforced on the network. A conduit only means something if traffic between zones really goes through controlled paths.
  • Scoring is inconsistent. Different assessors rate likelihood and impact differently. A defined risk matrix (3-2 includes examples) and one method applied every time fix this.
  • It is treated as a one-off. Systems change. The assessment should be revisited when the system does.

This is why we are building an IEC 62443 risk assessment tool that keeps assets, zones, an ATT&CK-mapped threat register, scoring and the final risk register in one model.

The UK context

In the UK, operators of essential services fall under the NIS Regulations 2018, and the NCSC's Cyber Assessment Framework (version 4.0, published August 2025) is the usual way to show how you meet them. The Cyber Security and Resilience Bill, which amends the NIS Regulations, was still going through Parliament in October 2026.

IEC 62443 is not a UK legal requirement in itself, but it gives a recognised, defensible structure for the OT parts of that work.

Getting started

If you have never assessed your control systems, you do not need to start with the full standard. A sensible first pass is to:

  1. Draw the boundary of one important system and list its assets and connections.
  2. Group the assets into candidate zones and mark every path between them.
  3. Ask, for each zone: what is the worst realistic outcome if this were compromised?

That alone usually shows where the biggest gaps are. If you would like help turning it into a full IEC 62443-aligned assessment, see our OT and industrial security work or get in touch.

Have a project in mind?

Book a free 30-minute call, tell us what you're trying to build, and we'll tell you honestly whether we're the right fit.

Book a call