Key takeaways
- 62443 splits responsibility across three roles: asset owner, service provider/integrator and product supplier. Know which parts apply to you and which you should demand from others.
- The risk assessment in 62443-3-2 produces zones, conduits and a target security level (SL 1 to 4) for each. That model is the backbone of everything else.
- Security levels describe the attacker a zone must resist. Maturity levels describe how well a process is run. Do not mix them up in contracts.
- Every new AI or analytics connection is a new conduit. Treat it with the same risk assessment and change control as any other path into a control zone.
- A three-plant company can apply 62443 proportionately: one program, one zone model template, SL 2 as a common baseline and SL 3 only where the risk justifies it.
ISA/IEC 62443 is a family of standards for securing industrial automation and control systems (IACS): the PLCs, HMIs, SCADA, DCS, historians and engineering workstations that run your lines. It is long, expensive to buy in full, and written for every industry from oil refineries to packaging lines. The good news for a mid-market manufacturer is that you do not need all of it. You need to know which parts are yours, which parts belong to your integrators and OEMs, and how to turn the core ideas into a plan your team can run.
How the series is organized
The series is grouped into four tiers. The part numbers tell you where a document sits.
| Tier | Example parts | What it covers | Who uses it most |
|---|---|---|---|
| 1. General | 1-1 | Terminology, concepts, models | Everyone |
| 2. Policies and procedures | 2-1, 2-3, 2-4 | Security programs for asset owners and service providers, patch management | Asset owner, integrators |
| 3. System | 3-2, 3-3 | Risk assessment, zones and conduits, system security requirements and security levels | Asset owner, integrators |
| 4. Component | 4-1, 4-2 | Secure product development, technical requirements for components | Product suppliers |
Editions differ between the ISA and IEC catalogs. As of November 2026, IEC lists 62443-2-1 Edition 2.0 (August 2024) and 62443-2-4 Edition 2.0 (December 2023). Always name the exact edition in contracts and audit scopes.
The three roles
62443 assigns responsibilities to roles, not job titles. A mid-market manufacturer is mostly the asset owner, but you will deal with all three.
- Asset owner. You. You own and operate the IACS, carry the risk and run the security program. Parts 2-1 and 3-2 are written for you.
- Service provider / integrator. The system integrator who designs and commissions a line, and the service company that maintains it. Part 2-4 sets requirements for their security program. Part 3-3 is what they design a system against.
- Product supplier. The PLC, drive, HMI, robot or IIoT gateway vendor. Part 4-1 covers their secure development lifecycle and 4-2 the technical capabilities of each component.
Plant-floor reality: In many mid-market plants the OEM owns more of the control system than you do. Packaged equipment arrives with its own PLC, its own remote access and its own idea of what "secure" means. 62443 gives you the vocabulary to put requirements on that OEM before the purchase order, not after the FAT.
The parts that matter most to an asset owner
2-1: your security program
62443-2-1 sets requirements for the asset owner's IACS security program. The 2024 IEC edition restructured the requirements into security program elements, removed overlap with an information security management system, and added a maturity model for evaluating requirements. It also acknowledges that long-lived legacy systems may only cover a subset of requirements, with compensating measures documented in policy. That fits brownfield plants well.
If you already run ISO/IEC 27001, the 2024 edition is easier to adopt alongside it. See ISO 27001 vs IEC 62443 for how to run both.
2-4: what to require from integrators and service providers
62443-2-4 defines security capabilities a service provider should have when it integrates or maintains your systems: things like hardening, account management, remote access practices, patch and malware handling, and backup and restore. Use it as a checklist in integrator contracts and RFQs. You do not need the integrator to be certified to ask that they meet named requirements.
3-2: risk assessment, zones and conduits
This is the most practical part for a plant team. 62443-3-2 describes how to:
- Define the system under consideration (a line, a building, a site).
- Run an initial high-level risk assessment.
- Partition assets into zones (groups that share security requirements) and identify conduits (the communication paths between zones).
- Compare the initial risk with your tolerable risk.
- Where it is exceeded, run a detailed risk assessment per zone and conduit and set a target security level (SL-T) for each.
- Document the cybersecurity requirements, assumptions and constraints so they can drive design and procurement.
- Get asset owner approval of the result.
Enterprise zone (ERP, email) Level 4-5
| conduit C1: firewall, DMZ
Site operations zone (MES, historian) Level 3
| conduit C2: filtered, one-way where possible
Line 1 control zone (PLC, HMI) Level 1-2
| conduit C3: safety network, no routing
SIS zone Level 1
Our zones and conduits guide walks through a worked example. The zones-and-conduits worksheet gives you a template.
3-3: system requirements and security levels
62443-3-3 lists system security requirements and requirement enhancements, organized under seven foundational requirements:
| FR | Name | Plant example |
|---|---|---|
| FR1 | Identification and authentication control | No shared "operator" logins on engineering workstations |
| FR2 | Use control | Operators can acknowledge alarms but not download logic |
| FR3 | System integrity | Detect unauthorized PLC program changes |
| FR4 | Data confidentiality | Protect recipes and credentials in transit and at rest |
| FR5 | Restricted data flow | Segment zones; control traffic through conduits |
| FR6 | Timely response to events | Logs reach someone who looks at them |
| FR7 | Resource availability | Backups, redundancy, protection against resource exhaustion |
Each requirement maps to security levels 1 to 4. In plain terms, SL 1 protects against casual or accidental violation. SL 2 protects against intentional attack using simple means and generic skills. SL 3 covers sophisticated attack with moderate resources and IACS-specific skills. SL 4 covers sophisticated attack with extended resources and high motivation.
The standard distinguishes three values. SL-T is the target from your risk assessment. SL-C is the capability a component or system can deliver when properly configured. SL-A is what is actually achieved on site. Gaps between SL-T and SL-C are closed with compensating countermeasures such as an extra firewall or tighter procedures.
4-1 and 4-2: what product suppliers should prove
You do not implement 4-1 or 4-2 yourself. You ask suppliers for evidence. 4-1 covers the supplier's secure development lifecycle: threat modeling, secure coding, security testing, vulnerability handling and patch delivery. 4-2 covers the technical capabilities of components (embedded devices, host devices, network devices and software applications) against the same seven FRs.
Maturity levels vs security levels
These two get confused in RFQs.
- Security level (SL) is about a technical capability: how strong an attacker a zone, system or component can resist.
- Maturity level (ML) is about a process: how consistently a supplier, integrator or asset owner runs a required practice. Parts 2-4 and 4-1 use maturity levels, and the 2024 edition of 2-1 adds a maturity model for asset owners.
A supplier can have a mature development process and ship a component that only reaches SL-C 1. An integrator can claim SL 3 capabilities but run them ad hoc. Ask for both, separately.
Certification options
The ISA Security Compliance Institute runs the ISASecure programs:
- CSA: component certification against 62443-4-2.
- SSA: system certification against 62443-3-3.
- SDLA: certification of a supplier's development lifecycle against 62443-4-1.
- ICSA: certification of IIoT devices and gateways, based on 62443-4-2 with additional requirements.
- Site assessment: a program aimed at operating sites.
IECEE also offers 62443 certification schemes. For most mid-market asset owners, the value is in buying certified components and systems, not in certifying the plant. Certify a site only if a customer or regulator asks for it.
What to ask of OEMs and integrators
Put these in the RFQ, not the punch list. The OT and AI vendor security questionnaire has a fuller version.
- Which 62443 parts and editions do you claim conformance to? Is it certified, and by whom?
- What SL-C does the controller, HMI and network gear reach per 4-2? Show the evidence.
- Is your development process assessed against 4-1? What maturity level?
- How do you handle and disclose vulnerabilities? How long will you supply security patches?
- How is remote access delivered? Can we own and switch off the access path?
- Can you deliver a zone and conduit drawing and a hardening record at FAT/SAT?
- Will you meet named 2-4 requirements during commissioning and maintenance?
Watch out: "Designed according to IEC 62443" on a datasheet tells you very little. Ask which part, which edition, which security level and who checked.
How AI and analytics connections fit
Predictive maintenance, energy analytics, vision quality inspection and cloud historians all need data from the control zones. In 62443 terms, each one adds or changes a conduit. That is a design change, and it should go through your 3-2 risk assessment and your MOC process.
Practical rules:
- Pull data out through a DMZ or an edge gateway at Level 3.5. Do not let a cloud service reach a PLC directly.
- Prefer one-way or read-only paths for analytics. Any write-back (setpoint changes, closed-loop optimization) raises the conduit's target SL.
- Treat the edge device as a component. Ask for 4-2 evidence or ISASecure ICSA certification.
- Log what the AI integration does, and who can change it.
See securing AI in OT networks and the Purdue model and AI for architectures that work.
A proportionate approach for a three-plant company
Say you have three plants, about 600 people, one IT manager, a controls engineer per site and no dedicated OT security staff. A sensible first year looks like this:
| Quarter | Focus | Effort (rough) |
|---|---|---|
| Q1 | Asset inventory per site; draft one security program on 2-1 lines | 2 to 4 weeks of engineer time per site |
| Q2 | One zone and conduit model as a template; apply to the highest-risk site first | 1 to 2 workshops per site |
| Q3 | Set SL-T (SL 2 baseline, SL 3 where justified); close the biggest conduit gaps such as remote access and IT/OT firewall | Capital spend on firewalls and remote access |
| Q4 | Put 2-4 and 4-2 requirements into purchasing templates; review with OEMs | Procurement and engineering time |
Do not try to meet every 3-3 requirement on day one. Close the conduits that matter, document compensating measures for legacy kit, and fix the rest during planned outages and line upgrades. You can't patch a PLC on a Tuesday, and 62443 does not ask you to.
Common mistakes
- Buying the whole series and reading it cover to cover before doing anything.
- Setting SL 3 everywhere because it sounds safer. It drives cost without a risk case.
- Drawing zones on paper but leaving the network flat.
- Treating OEM remote access as the OEM's problem.
- Adding an AI or cloud connection without updating the zone model.
- Confusing a maturity level claim with a security level claim.
Where to start: Monday-morning checklist
- Pick one site and one line. Write down what is on it and how it talks to the outside.
- Draw the zones and conduits as they are today, not as they should be.
- Mark every remote access path and every cloud or analytics connection.
- Agree a baseline target SL with operations and EHS.
- Add three 62443 questions to your next equipment RFQ.
- Run the OT security maturity assessment to set priorities across sites.
Standards and certification schemes change. Check editions with ISA or IEC before you cite them in contracts, and confirm any regulatory use with counsel.
Sources and further reading
- ISA/IEC 62443 Series of Standards (ISA)
- IEC 62443-2-1:2024 Security program requirements for IACS asset owners (IEC Webstore)
- IEC 62443-2-4:2023 Security program requirements for IACS service providers (IEC Webstore)
- ISASecure certification programs (ISA Security Compliance Institute)
- ISASecure ICSA certification for IIoT devices and gateways
This guide is general information for manufacturers, not legal advice. Confirm regulatory obligations with qualified counsel.
FAQ
Frequently asked questions
Is IEC 62443 mandatory for manufacturers?
Not by itself. IEC 62443 is a voluntary consensus series. It becomes contractual when customers or insurers require it, and it is widely used as a way to show you meet broader legal duties such as the NIS2 risk-management measures or, for product makers, the EU Cyber Resilience Act. Many manufacturers adopt it because it is the common language of OEMs, integrators and auditors.
Can a factory be certified to IEC 62443?
Product and process certification is the most established route. ISASecure certifies components against 62443-4-2 (CSA), systems against 62443-3-3 (SSA) and supplier development processes against 62443-4-1 (SDLA), and it also runs a site assessment program. Asset owners more often get an independent assessment against 62443-2-1 and 3-2 than a formal certificate. Ask what your customer actually needs before buying a certificate.
Which security level should a mid-sized plant target?
There is no default answer, because the target comes out of your 62443-3-2 risk assessment. In practice many mid-market plants use SL 2 (protection against intentional attack with simple means) as a baseline for most zones and reserve SL 3 for zones where compromise could cause safety, environmental or major production consequences, such as SIS-adjacent networks or remote access paths.
What is the difference between IEC 62443 and ISA 62443?
They are the same series published by two bodies. ISA publishes the ANSI/ISA-62443 documents and IEC publishes them as IEC 62443, with some parts released at different times. Edition years can differ between the two catalogs, so check the exact edition when you write a contract or audit scope.
Related guides
Frameworks
ISO 27001 vs IEC 62443: which one a manufacturer needs, and how to run both
ISO/IEC 27001 is a certifiable management system standard for information security across the whole company.
Guide · 7 min read
Frameworks
Cyber Resilience Act for industrial manufacturers: what makers and plants need to do
The EU Cyber Resilience Act (Regulation (EU) 2024/2847) sets cybersecurity requirements for products with digital elements sold in the EU, from PLC-based machines to IIoT gateways.
Guide · 7 min read
OT Security
IEC 62443 zones and conduits: a walkthrough for a mid-size plant
Zones group assets that share security requirements; conduits are the controlled paths between them.
Guide · 8 min read
Frameworks
NIST SP 800-82 Rev. 3: how a plant actually uses the OT security guide
NIST SP 800-82 Rev.
Guide · 7 min read