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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is IEC 62443-3-3?

IEC 62443-3-3 sets out the system security requirements for an industrial automation and control system, organised under seven foundational requirements and mapped to four security levels.

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

What Is IEC 62443-3-3?

What Is IEC 62443-3-3?

Of all the documents in the IEC 62443 series, 3-3 is the one that gets printed and left on a desk. It answers the question an engineer actually asks: given that this zone needs to resist a particular kind of adversary, what must the system be able to do? It does that by listing system requirements, grouping them under seven headings, and tying each one to a security level.

The Seven Foundational Requirements

Everything in the document hangs off seven categories, usually written as FR1 to FR7:

  1. Identification and authentication control. Knowing who or what is asking, for human users, software processes, and devices.
  2. Use control. Enforcing what an authenticated identity is permitted to do, including on shared and emergency accounts.
  3. System integrity. Protecting software, firmware, and information from unauthorised change, including protection of the communication path.
  4. Data confidentiality. Preventing disclosure of information at rest and in transit.
  5. Restricted data flow. Segmentation, zone boundary protection, and the conduits between zones. This is where network architecture lives.
  6. Timely response to events. Audit logging, log protection, and the ability to act on what the logs show.
  7. Resource availability. Denial of service resistance, backup, recovery, and management of communication loads.

The ordering is deliberate and tells you something. Confidentiality is fourth of seven, and availability closes the list as the requirement that underpins everything else in a plant. An IT practitioner reading the document for the first time should notice that.

System Requirements and Enhancements

Under each foundational requirement sit numbered system requirements, each written as a capability the system must provide, and most with one or more requirement enhancements that raise the bar. Familiar examples include SR 1.1 on human user identification and authentication, SR 1.5 on authenticator management, SR 2.1 on authorisation enforcement, SR 3.1 on communication integrity, SR 3.4 on software and information integrity, SR 5.1 on network segmentation, SR 5.2 on zone boundary protection, SR 6.1 on audit log accessibility, SR 7.1 on denial of service protection, SR 7.3 on control system backup, and SR 7.4 on recovery and reconstitution.

The requirement enhancements are what distinguish one security level from the next. SR 1.1 at level 1 means users are identified and authenticated. The enhancements add multi-factor authentication for untrusted networks at the next level, and for all interfaces at the level above. The document’s central table maps every requirement and enhancement to the levels at which it applies, which is the part people photograph.

Security Levels and the SL Vector

The four levels are defined by adversary capability rather than by control count: casual or coincidental violation at SL 1; intentional violation with simple means and low resources at SL 2; sophisticated means, moderate resources, and system-specific skills at SL 3; and extended resources with high motivation at SL 4.

Because the seven foundational requirements are independent, a zone’s target is expressed as a vector rather than a single number, for instance SL-T (2,2,2,1,3,2,2). That notation lets a design say what it really means: restricted data flow matters most here, and confidentiality matters least. Three variants are used in practice. SL-T is the target derived from risk assessment in 62443-3-2. SL-C is the capability a product or system can provide, which suppliers state in their documentation. SL-A is what is actually achieved on site once everything is configured, patched, and operated, and the gap between SL-C and SL-A is the subject of most assessments.

Using It Without Drowning

For boundary requirements under FR5, hardware-enforced options such as a data diode are one way to demonstrate a high achieved level on a one-way conduit, and conventional network segmentation covers the rest. The companion documents are described under IEC 62443 and IEC 62443-4-1.

At Privia Security, we carry out zone-level assessments against these requirements through our Regulation and Compliance Services.

FAQ – Frequently Asked Questions

What Is an SL Vector?

A seven-element notation giving the security level for each foundational requirement in a zone, written for example as (2,2,2,1,3,2,2). It exists because the seven areas are independent: a zone may need strong restricted data flow and weak confidentiality. Vectors come in target, capability, and achieved forms, and comparing the capability of installed equipment against the target is the core design activity.

What Is the Difference Between 62443-3-3 and 62443-4-2?

3-3 states what a system must be able to do within a zone; 4-2 states what an individual component, such as a controller, application, or network device, must provide. The two are aligned requirement by requirement. Use 3-3 for design and assessment of an installation, and 4-2 for writing procurement specifications and evaluating supplier claims.

Can Legacy Equipment Meet These Requirements?

Often not directly, and the standard anticipates that. Where a device cannot provide a required capability, the zone may still achieve its target level through compensating countermeasures, such as boundary enforcement, protocol filtering, monitoring, or physical control, provided the reasoning and residual risk are documented. This is the mechanism that makes the standard usable on plants built decades ago.

Do UK Regulators Require IEC 62443-3-3?

No standard is mandated by name. UK operators of essential services are assessed against outcomes in the NCSC Cyber Assessment Framework. A documented 62443 zone and conduit model with per-zone requirement assessments is one of the most convincing ways to evidence those outcomes in an industrial environment, and sector regulators are generally familiar with the notation.

Related Terms

You May Be Interested In These

What Is the SOC Maturity Model?

Cybersecurity Terms

17 November 2026

What Is the SOC Maturity Model?

Read More
What Is S3 Object Lock and Immutable Backup?

Cybersecurity Terms

17 November 2026

What Is S3 Object Lock and Immutable Backup?

Read More
What Is eBPF?

Cybersecurity Terms

17 November 2026

What Is eBPF?

Read More