Zones group assets that share security requirements; conduits describe controlled communication between those zones. A useful workbook turns that concept into an inventory, diagrams, allowed flows, risk decisions, controls, tests, and owners that remain traceable as the industrial network changes.
The short answer
Start with the real assets and required communications, not with VLAN names. Group assets only when their risk, function, lifecycle, and required security level justify the same zone. Define every conduit by endpoints, direction, protocol, purpose, identity, availability need, owner, and monitoring. Then trace the resulting controls and tests back to the risk assessment.
- Inventory assets, firmware, roles, locations, critical functions, dependencies, and responsible owners before drawing boundaries.
- Separate safety, basic control, supervisory, engineering, vendor access, and enterprise responsibilities where their risks differ.
- Permit only documented flows and record why each flow is operationally necessary.
- Treat segmentation as one control within a larger system of identity, hardening, monitoring, backup, recovery, and change management.
Decision guide
| Workbook element | Question to answer | Review evidence |
|---|---|---|
| Zone register | Which assets share function and security requirements? | Asset list, boundary rationale, target requirements, owner |
| Conduit register | What communication must cross a boundary? | Source, destination, direction, service, purpose, authentication, availability |
| Architecture | Where are physical, logical, wireless, remote, and temporary paths? | Current diagrams matched to configuration and site inspection |
| Verification | Do deployed controls enforce the approved design? | Ruleset review, reachability tests, monitoring, failover and recovery results |
A practical workflow
- 01
Define system scope, essential functions, risk method, assumptions, and accountable security and operations roles.
- 02
Build an asset and communication inventory using configuration exports, drawings, interviews, and controlled observation.
- 03
Propose zones from shared risk and function, then enumerate every necessary conduit and prohibited path.
- 04
Select proportionate technical and procedural controls, including secure remote and maintenance access.
- 05
Test the deployed state, record deviations and compensating measures, approve the baseline, and repeat after material change.
Evidence and acceptance
The approved package should include scope, asset inventory, zone and conduit registers, current diagrams, risk rationale, target security requirements, firewall and access-control references, remote-access paths, monitoring ownership, test cases, results, deviations, approvals, and a review trigger. A colored network drawing without an underlying register is not enough.
Common mistakes
- Equating a zone directly with a subnet or VLAN without documenting the security rationale.
- Omitting temporary laptops, engineering workstations, wireless links, vendor paths, and shared infrastructure.
- Allowing broad bidirectional rules because an application dependency was not investigated.
- Designing segmentation without safe degraded operation, redundancy, diagnostics, or recovery access.
- Leaving the workbook disconnected from network changes and acceptance testing.
Engineering and security boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Is every VLAN an IEC 62443 zone?
No. A VLAN can help implement a boundary, but a zone is defined by shared security requirements and risk. One zone may use several network segments, and a VLAN does not prove the required controls.
What should a conduit record contain?
At minimum: connected zones, endpoints, direction, protocol and service, purpose, identity, authorization, availability, encryption where applicable, monitoring, owner, and verification result.
How often should the workbook be reviewed?
At an agreed interval and whenever assets, firmware, topology, remote access, business interfaces, risk, or required security controls materially change.
Does AutoNexit certify IEC 62443 compliance?
No. It keeps evidence and change history organized; qualified parties determine requirements, design controls, test them, and make compliance decisions.