Security teams should separate OT, ICS, and business networks into tightly controlled zones, then monitor traffic between them continuously. Segmentation reduces lateral movement, while logging and anomaly detection help spot unusual access before it spreads. For critical infrastructure, the goal is not only blocking intrusion but preserving safe operation, recovery speed, and the ability to isolate affected systems quickly.
How to Segment Critical Infrastructure Networks Without Breaking Operations
Critical infrastructure segmentation works best when it reflects operational reality, not just topology. Separate OT, ICS, safety, and business environments into distinct trust zones, then define the allowed conduits between them. The important design question is not whether traffic is blocked in general, but whether each communication path is justified, logged, and narrow enough to limit lateral movement.
Good segmentation also has to support recovery. In a plant, utility, or transport environment, an over-fitted boundary can create the same disruption as an intrusion if operators cannot reach the systems they need during maintenance, incident response, or failover.
A useful starting point is to align zone boundaries with function and criticality, then treat any crossing as an exception that needs explicit ownership. The Network Segmentation Guide is useful here because it frames zones, east-west control, and rollout as an operational programme rather than a diagram exercise.
What Monitoring Needs to Catch in OT and ICS Traffic
Segmentation alone does not reduce blast radius if east-west traffic is invisible. Continuous monitoring between zones should look for unusual command paths, unexpected remote administration, new service-to-service relationships, and changes in protocol behaviour that do not fit the baseline. In critical infrastructure, anomalous access is often more important than a single blocked event because early abuse may look like ordinary operational traffic.
Monitoring should therefore combine logging, protocol-aware inspection, and anomaly detection that understands normal plant or infrastructure rhythms. A zone crossing may be legitimate, but if the source, timing, command type, or destination changes, teams need enough context to tell whether the event is maintenance, misconfiguration, or an active intrusion.
For network-layer enforcement, Network Access Control (NAC) Guide is relevant because device profiling, quarantine VLANs, and dynamic policy are often what make segmentation enforceable at scale. For access mediation and accountability, the AAA Security Guide is the better fit when the concern is authentication, authorisation, and auditability across administrators and managed devices.
Designing for Containment, Recovery, and Controlled Exceptions
The best critical-infrastructure segmentation plans assume two things at once: some traffic must be allowed, and some systems will eventually need emergency access. That means designing for containment and controlled exception handling, not for perfect isolation. Break-glass paths, remote support channels, and management access should be more restricted than normal operations, with tighter logging and fast revocation when they are used.
Teams should also validate the failure modes before an incident. If a firewall rule fails closed, can operators still supervise the process safely? If monitoring degrades, can the environment still keep essential services running long enough to recover? The answer should be based on tested pathways, not assumptions about who will be available during a real outage.
When critical access depends on remote administration or vendor support, the Critical Infrastructure Identity Security Guide helps connect segmentation to the access controls that actually protect essential services, including privileged access, device identity, and supplier access.
Risk and Threat Considerations
Critical infrastructure networks are attractive because a single weak segment boundary can let an attacker move from a low-value zone into operational systems, safety functions, or shared management planes. The main risk is not just intrusion, but propagation: once access is gained, poorly bounded east-west trust can turn one compromised host into a broad operational disruption.
Failure mechanism: Flat or loosely segmented networks allow lateral movement, while weakly monitored zone crossings hide the early signs of abuse. Remote access paths, shared credentials, and unmanaged exceptions often become the easiest route around the intended boundary.
Impact: An incident can expand from a single compromised endpoint into loss of visibility, unsafe operator workload, degraded recovery speed, and longer service interruption. In critical infrastructure, that can mean the difference between containing an event and forcing partial shutdown.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-12 — Network Infrastructure Management | Covers secure network zoning, device hardening, and managed connectivity for critical networks. |
| Recommendation — Centralise network management, harden infrastructure, and enforce secure admin paths between zones. | ||
| NIST SP 800-53 Rev 5 | SC-7 — Boundary Protection | Directly addresses controlling and monitoring traffic across system boundaries and zones. |
| Recommendation — Enforce boundary filtering and monitor inter-zone flows for anomalous or unauthorized communication. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication, and Access Control | Applies where segmentation depends on controlled privileged and remote access between critical zones. |
| DE.CM-01 — Networks and network services are monitored to find anomalous events | Matches the need for continuous monitoring of traffic between OT, ICS, and business zones. | |
| Recommendation — Require strong authentication and access control for any cross-zone administrative or vendor access. Continuously monitor inter-zone traffic and alert on deviations from the established baseline. | ||
Practitioner Guidance
What to prioritise: Start with the crossings that can reach control, safety, or management systems, then verify that every exception has an owner, a business reason, and a logging path. If a connection exists but no one can explain why it is needed, it is already a segmentation weakness.
What to verify: Confirm that the monitoring stack sees zone-to-zone traffic, not just internet egress, and that alerts can distinguish maintenance from abnormal access. A segmentation design is only credible if it can show who talked to what, when, and under which approved route.
Practitioner takeaway: The goal is not maximum isolation, it is bounded exposure with visible, testable recovery paths so an attack or fault cannot spread beyond the zone that actually needs to fail.
Related resources from NHI Mgmt Group
- RADIUS
- How should security teams reduce blast radius in critical infrastructure environments that still rely on aging, unsupported systems?
- How should life sciences security teams segment supply chain networks to reduce ransomware blast radius?
- How should security teams reduce blast radius in flat enterprise networks?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org