Asset owner / operator
IEC 62443-2-1:2024
Security-program policies and procedures for an IACS in operation. The public scope explicitly recognises legacy-system limitations and compensating measures.
Read the IEC public scope ↗Framework guide · IEC 62443
IEC 62443: connect the requirement to the deployed system.
Start with the industrial system, the accountable roles and the decision being reviewed. Then connect risk, architecture and operational evidence rather than collecting product labels without their deployment context.
OT asset owners, engineering teams, integrators and industrial cybersecurity reviewers.
Start with the scope
Choose the part that matches the role and decision.
IEC 62443 is a family of industrial automation and control system security publications. Four useful starting points are the asset-owner programme, the service-provider programme, system-design risk assessment and system security requirements. These scopes are related but do not make the roles interchangeable.
The public IEC catalogue descriptions below explain the scope of those parts; the full requirements are in the licensed publications. Confirm the applicable part, edition, system boundary and contractual scope for the work. CUP's questions and case selections are engineering interpretation, not a conformity assessment.
IACS service provider
IEC 62443-2-4:2023
Security-related processes offered during integration and maintenance. Use its scope to make the asset-owner and integrator handoff explicit.
Read the IEC public scope ↗System-design risk assessment
IEC 62443-3-2:2020
System under consideration, zones and conduits, risk assessment, target security levels and documented security requirements.
Read the IEC public scope ↗System security requirements
IEC 62443-3-3:2013
Technical control-system requirements and capability security levels, applied with the zones, conduits and target levels for the system being considered.
Read the IEC public scope ↗CUP engineering interpretation
Turn the framework into a reviewable decision.
Define the actual system boundary
Record the assets, interfaces, dependencies and operational states in scope. A zone diagram should describe the deployed routes, including maintenance and engineering paths.
Bound the integrator's authority
Separate permission to connect from permission to change logic or configuration. Retain named ownership for approval, session termination and supplier exit.
Explain the security-level claim
Identify whether a record concerns a target or a capability and what system, component or configuration it covers. Do not turn a product claim into a plant-wide conclusion.
Exercise the degraded state
Review what happens when identity, connectivity or central monitoring is unavailable. Preserve accountable recovery and safety constraints while checking the remaining access paths.
Where a control label stops explaining the plant.
- A component or product claim is used as evidence for the entire installed system.
- The zone drawing omits a vendor tunnel, engineering workstation or alternate maintenance route.
- The integrator's responsibilities are documented, but the plant cannot revoke its operational access.
- A patch or recovery plan has no evidence for the configuration and operating state that will actually return to service.
5 selected analyses · newest first
IEC 62443 engineering questions in real cases.
The cases illustrate architecture and operational review questions; an incident description alone does not determine compliance with a particular part of IEC 62443.
26 Oct 2026 · OT & ICS · Industrial Engineering
Node-RED Deployment Security Must Survive a Compromised Workstation and an Offline Plant
Separate an authenticated maintenance route from authority to deploy logic, then examine recovery when central identity is unavailable.
14 Oct 2026 · OT & ICS · Third-Party Access
Third-Party ICS Access Is an Operational Trust Boundary, Not a VPN Problem
Review the integrator's identity, privileges, customer-data exposure and recovery obligations as one operational boundary.
24 Aug 2026 · OT & ICS · Industrial Network Security · Supply Chain
RUGGEDCOM Shows Why Industrial Firewalls Need Lifecycle Transparency
Trace the vulnerability lifecycle of embedded third-party software into the deployed industrial boundary device.
9 Aug 2026 · OT & ICS
Zero Trust in OT Should Mediate Authority, Not Modernise Every PLC
Use the surrounding architecture to mediate authority where legacy equipment cannot provide modern identity controls itself.
1 Aug 2026 · OT & ICS
The Restart Bottleneck Is Not the Backup. It Is the Evidence.
Distinguish restoring services from assembling enough independent evidence to authorise a return to production.
Apply the evidence
Take one decision into a working sheet.
Review OT remote access →
Twelve checkpoints for one integrator, one maintenance route and one operational task. Save locally or export CSV/PDF.
Map architecture evidence →
Record the system boundary, evidence owner and tests behind the control claim.
Review an SBOM / VEX claim →
Tie the component and product version to a scoped vulnerability claim, supporting evidence and an owned response decision.
Follow the Internet-Exposed OT reading path
Notes in the working sheets stay in your browser. You can export them without registering. The sheets organise evidence; they do not determine conformity.