Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An IEC 62443 security level states which class of attacker a zone must withstand, from casual misuse at SL 1 to a well-resourced state actor at SL 4, and drives the requirements that apply.

What Is a Security Level in IEC 62443?
IEC 62443 avoids rating industrial systems on a scale of good to excellent. Instead it asks a sharper question: who are you defending this zone against? A security level describes the attacker a zone must withstand, characterised by four attributes — means, resources, skills, and motivation. Everything else in the standard follows from the answer.
| Level | The adversary it addresses |
|---|---|
| SL 0 | No specific requirement; no meaningful consequence from compromise |
| SL 1 | Casual or coincidental violation: an operator error, a curious contractor, a worm that arrived by accident |
| SL 2 | Intentional violation using simple means, low resources, generic skills, and low motivation — commodity malware and opportunistic criminals |
| SL 3 | Intentional violation using sophisticated means, moderate resources, system-specific skills, and moderate motivation — organised crime and capable groups who understand industrial systems |
| SL 4 | Intentional violation using sophisticated means, extended resources, system-specific skills, and high motivation — state-sponsored operations |
The jump from SL 2 to SL 3 is where cost rises steeply, because SL 3 assumes the attacker knows what a PLC is and has studied your equipment. SL 4 is reserved for targets whose compromise would have national consequence, and very few zones in a typical plant justify it.
The standard uses three variants of the same scale, and mixing them up is the most common error in practice.
A controller certified to SL-C 2 installed in a flat network with shared credentials achieves SL-A 1 at best. Certification describes potential; assessment describes reality.
Levels are not assigned as a single number in isolation. IEC 62443 defines seven foundational requirements, and a zone can carry a different level against each: identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events, and resource availability. A safety zone may demand SL 3 for system integrity while SL 1 is ample for data confidentiality, which produces a vector rather than a scalar and reflects how industrial risk actually distributes.
IEC 62443-3-3 then lists the system requirements, each with requirement enhancements that apply as the level rises. At SL 1, identification and authentication may be satisfied by a shared account on a human-machine interface. At SL 2 it needs individual accounts. At SL 3 it needs multi-factor authentication for access from untrusted networks and hardened credential management. The standard is explicit about what each step costs you.
The process sits in IEC 62443-3-2. Define the system under consideration, perform an initial high-level risk assessment, partition it into zones and conduits, and then run a detailed risk assessment per zone that yields SL-T. The driver is consequence: a zone whose compromise releases a hazardous substance earns a higher target than one whose compromise loses a shift of production data, regardless of how the two are connected.
This is also where safety and security meet. A safety integrity level is a probability band derived from random failure rates; a security level is a statement about an adversary. They are deliberately different scales and must not be mapped onto one another, but they describe the same equipment, so the hazard study and the security risk assessment should be run with both teams present.
Put SL-T in your procurement documents, because asking a supplier for equipment capable of SL-C 2 is concrete in a way that asking for secure equipment is not. Use the SL-A assessment to prioritise remediation, and expect the answer to be uncomfortable the first time. UK operators of essential services will find the NCSC’s Cyber Assessment Framework asks outcome-based questions that an IEC 62443 zone model answers neatly, since both frameworks start from consequence rather than from technology.
At Privia Security, our Cyber Risk Analysis Services run the partitioning and target-setting exercise with your engineering teams and measure what the plant achieves today.
No, and attempting it wastes money that would buy more risk reduction elsewhere. Targets follow consequence: a safety zone or a zone controlling a hazardous process may justify SL 3, while a historian replication zone is usually well served at SL 1 or SL 2. A uniform target across a plant generally indicates the risk assessment was skipped.
Assurance that the product can meet the requirements for that level when configured properly, assessed against IEC 62443-4-2 by an accredited body. It does not guarantee your installation achieves anything, because achieved level depends on configuration, network design, credential practice, and monitoring. Treat certification as a procurement filter, not as evidence of posture.
They measure different things on the same equipment and should never be converted into each other. SIL is a probability band for random and systematic failures. SL describes the capability of a deliberate attacker. A high SIL function in a poorly protected zone is still easy to defeat deliberately, which is why both assessments are required.
Yes, and the standard expects it. A zone’s security level is properly expressed as a vector across the seven foundational requirements, so you might require SL 3 for system integrity and restricted data flow while accepting SL 1 for data confidentiality. This keeps spending aligned with what compromise would actually cost the process.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.