Which existing processes does IEC 62443 plug into: plant operations, contractor management or product development?
IEC 62443 is a role-based series. You first need to know where you sit in the supply chain to know which processes to connect:
- Asset owners (plants, sites, infrastructure operators): IEC 62443-2-1:2024 sets security program policy and procedure requirements for asset owners. The processes to connect are plant change management, the equipment register, contractor access and remote maintenance, and maintenance shutdown windows. OT patching usually has to fit planned shutdowns and cannot simply follow IT’s rhythm.
- System integrators and maintenance service providers: IEC 62443-2-4:2023 sets the security processes service providers should offer when integrating and maintaining automation solutions. The processes to connect are project handover documents, remote access requests and change records.
- Product suppliers (equipment, controllers, software): IEC 62443-4-1:2018 defines a secure development lifecycle covering security requirements, secure design, secure implementation (including coding guidelines), verification and validation, defect management, patch management and product end-of-life. The processes to connect are engineering, releases and after-sales patching.
Many plants run equipment that is well over a decade old and cannot support new security functions. IEC 62443 allows a security requirement to be met by a compensating countermeasure, so existing lines can improve in stages instead of waiting for replacement. We flag these legacy systems first and work out a feasible hardening sequence with the equipment teams.
Which technologies implement IEC 62443 zones, security levels and OT monitoring, and what evidence do they leave?
Both system and component requirements in IEC 62443 are organised around seven foundational requirements (FR): FR1 identification and authentication control, FR2 use control, FR3 system integrity, FR4 data confidentiality, FR5 restricted data flow, FR6 timely response to events and FR7 resource availability. The first column follows the published abstracts; the implementation column is our good-practice recommendation.
| Requirement (clause / control) | Implementation technology | Evidence left behind |
|---|---|---|
| 62443-3-2: define the system under consideration (SUC), partition into zones and conduits, assess risk per zone, set SL-T | OT asset inventory (mainly passive discovery), network topology, zone design | SUC definition, zone/conduit diagram, risk assessment and SL-T records |
| 62443-3-3 FR5 restricted data flow | Industrial firewalls, DMZ between IT and OT, conduit access rules | Conduit rule table, firewall configuration baseline |
| 62443-3-3 FR1 and FR2 identification, authentication and use control | Personal accounts instead of shared ones, remote maintenance jump host, MFA, role-based rights | Account register, remote access logs |
| 62443-3-3 FR3 system integrity and FR6 timely response to events | OT network monitoring (passive traffic analysis, anomaly detection), central logging | Alert and response records, log retention records |
| 62443-3-3 FR7 resource availability | Backups of control programs and configurations, redundancy, restore tests | Configuration backup and restore records |
| 62443-4-1: secure development lifecycle | Security requirements and design reviews, coding guidelines, security testing, defect and patch management | Development process records, test reports, patch advisories |
| 62443-4-2: component requirements (CR) and capability level SL-C | Component security functions (authentication, encryption, logging) | Component requirement mapping, SL-C self-assessment or certification report |
| 62443-2-1:2024 and 62443-2-4:2023: asset owner and service provider security programs | Policies and procedures, contractor capability requirements, change management | Security program documents, service provider assessments |
A security level is not one number for the whole plant but a set for each zone and conduit. The security level of a zone or conduit is a vector across the seven foundational requirements, so the same zone may need a higher level for FR5 and a lower one for FR4.
As for sequence, we recommend finishing the asset inventory and zone diagram before discussing SL-T; without clear zones, a security level has nothing to attach to. Product suppliers should get their 4-1 process records running smoothly first, so the 4-2 component requirement mapping has evidence behind it.
How does IEC 62443 connect risk assessment to security levels, technical controls and monitoring metrics?
IEC 62443 is itself a chain from risk to control, and we connect it to your enterprise risk management:
- Risk identification: following 62443-3-2, define the system under consideration, partition it into zones and conduits and assess risk per zone. Example: a contractor laptop connecting remotely into the control network.
- Standard requirement: set a target security level (SL-T) for each zone and conduit, then select the system requirements from 62443-3-3 (or, for product suppliers, the component requirements in 62443-4-2) that must be met.
- Technical control: all remote maintenance goes through a jump host with MFA, conduits allow only necessary traffic, and OT monitoring alerts on abnormal connections.
- Monitoring metric: asset inventory coverage, share of cross-zone connections not covered by conduit rules, share of remote maintenance via the jump host, and the number of compensating countermeasures with their next review date.
Security levels reflect the strength of the attacker: SL 1 protects against casual or coincidental violation; SL 2 against intentional violation using simple means with low resources, generic skills and low motivation; SL 3 against intentional violation using sophisticated means with moderate resources, IACS-specific skills and moderate motivation; SL 4 against intentional violation using sophisticated means with extended resources, IACS-specific skills and high motivation. Set the level too high and the line cannot change; set it too low and the risk stays uncontrolled. Getting that trade-off right needs risk management, the standard and OT engineering in the same room.
At Winners, one team plans role and sub-standard scoping, risk assessment, technical controls and process improvement together, so one set of evidence serves several regulations and customer requirements. VP- and director-level consultants lead the work end to end, never outsourced.
Which departments, systems, data and evidence must be integrated vertically for IEC 62443?
OT security most often stalls between departments: plant engineering knows the equipment but not the network, IT knows firewalls but cannot stop the line, R&D knows the product but has never seen a customer plant’s topology. Vertical integration makes one asset inventory and zone diagram serve as the plant’s maintenance reference, IT’s rule base and the audit evidence at the same time.
| Department | System | Data | Evidence |
|---|---|---|---|
| Plant engineering / production (OT) | SCADA, HMI, historian, engineering workstations | Equipment register, network topology, maintenance windows | Asset inventory, zone/conduit diagram |
| IT / security | Industrial firewalls, jump hosts, OT monitoring, log platform | Connection rules, alerts, accounts | Conduit rule table, alert response records |
| Automation engineering | Control program repository, configuration backups | Control programs, configurations, firmware versions | Change records, backup and restore records |
| R&D (product suppliers) | Version control, build and test, defect tracking | Security requirements, test results, defects | 4-1 process records, 4-2 requirement mapping |
| Procurement / contractor management | Supplier master data, remote access requests | Contractor list, access periods | Service provider requirements, access approvals |
| Safety / quality | Change review and quality system | Impact of security measures on safety functions and processes | Joint change review records |
We usually start with the asset inventory and zone diagram, because every rule, monitoring setup and audit afterwards depends on them; then remote maintenance and contractor management, the most common intrusion path; and R&D’s 4-1 and 4-2 mapping last. Safety and quality must take part in change reviews so that security measures do not disturb processes or safety functions.
Each row needs a named owner and storage location; the zone/conduit diagram in particular needs a version and an approver, and must be updated whenever the line changes.
What does Ahura do in an IEC 62443 project, and how does the data flow?
The Ahura Enterprise Risk Management Platform is a Taiwan-born RegTech platform developed by Winners Consulting. It is currently at the POC (proof-of-concept) stage, and everything below describes the POC build. In an IEC 62443 project Ahura keeps and signs off evidence; it is not an OT monitoring tool and does not connect to the control network.
Data flow:
- Our role and sub-standard scoping, risk assessment and SL-T decisions, together with your asset inventory, zone/conduit diagrams, alert response records and R&D’s 4-1 process records, go into Ahura, deployed on your premises.
- Every sign-off enters the evidence chain, compatible with EU eIDAS certificates.
- Auditors, certification bodies or customer auditors retrieve evidence from that same chain.
Why on-premises matters: plant network topologies and zone diagrams are highly sensitive in themselves. Ahura is 100% on-premises; client documents and data never go to the cloud or leave your environment. A group-style distributed architecture keeps HQ policy uniform while each site stays locally compliant, and the interface supports EU languages such as German, French, Dutch and Czech, plus Traditional Chinese and English.
To be clear: an IEC 62443-specific module is planned under the modular extension design. For now Ahura focuses on the evidence chain, sign-offs and on-premises storage; document upload with compliance gap analysis, cross-standard comparison and regulatory change tracking are in development and will be released as the POC progresses.
What governance, risk, efficiency and continuous-compliance results does IEC 62443 integration produce?
We describe results in ways that can be checked:
- Governance: every zone and conduit has an owner, an SL-T and a recorded decision; management sees which zone’s risk was accepted and which relies on compensating countermeasures, rather than a single line saying “OT is isolated”.
- Risk: remote maintenance and contractor connections follow a fixed path, abnormal connections produce alerts with response records, and legacy equipment is managed through compensating countermeasures with a next review date.
- Efficiency: SL-T can go straight into purchasing specifications, asking equipment suppliers and integrators for matching capabilities; one asset inventory and zone diagram answers customer audits without being redrawn each time.
- Continuous compliance: equipment replacement, line expansion or new remote connections go through the same change review, and zones and rules are updated with them.
A note on the legal relationship: IEC 62443 is a useful reference for implementing the EU CRA Annex I requirements and for gap analysis, but IEC 62443 certification does not by itself give presumption of conformity with the CRA; that comes only from harmonised standards published in the Official Journal, common specifications or designated certification schemes (CRA Article 27). If your customer is an entity in scope of NIS2, the same zoning and access control records can also answer its supply chain requirements.
We start from the management system you already run and build IEC 62443 into your existing operations, change and development processes instead of setting up a separate one. Winners provides consulting only and does not issue certifications; certification is carried out by certification bodies. To find out which sub-standard to start with, contact us.
Continuous assurance & trusted supply chain: IEC 62443 Internal Audit Outsourcing & Supplier Audits
Technical integration for related services
Official sources
- IEC 62443-3-2:2020 — Security risk assessment for system design (zones and conduits, SL-T) — IEC Webstore
- IEC 62443-3-3:2013 — System security requirements and security levels — IEC Webstore
- IEC 62443-4-1:2018 — Secure product development lifecycle requirements — IEC Webstore
- IEC 62443-4-2:2019 — Technical security requirements for IACS components — IEC Webstore
- 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
- IEC SyC Smart Energy — IEC 62443 overview (foundational requirements, security levels, zones and conduits)
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 27 presumption of conformity — EUR-Lex
