Security teams should assume breach and contain compromise as early as possible, especially in critical infrastructure. The priority is to reduce blast radius by isolating affected systems, segmenting operational environments, and preserving essential services while investigation continues. In water facilities, resilience depends on limiting lateral movement and keeping core operations running even when one site or network segment is impacted.
How to contain a multi-site critical infrastructure attack without losing control of operations
When multiple facilities are affected, containment has to be coordinated at the portfolio level, not just site by site. The right move is to assume the compromise may be moving through shared identity, network, remote access, or management layers, then isolate what is affected while preserving the minimum functions needed for safe operation. The goal is to stop spread without creating a second outage.
That usually means separating impacted sites from shared administration paths, constraining east-west traffic between facilities, and using a tiered response so critical services remain available even if one site must be taken partially offline. In operational environments, containment should be designed around control boundaries, not just around the asset that first triggered the alert.
For teams responsible for essential services, the most effective containment plans are pre-built. They define which systems can be segmented quickly, which control channels stay open, and which local operators can continue running safely if central access is disrupted.
Why blast-radius control is different in interconnected infrastructure
Critical infrastructure often depends on shared identity, remote access, vendor connectivity, monitoring, and management networks. If an attacker reaches one facility, those same pathways can let them pivot into others unless the environment is deliberately segmented. A Critical Infrastructure Identity Security Guide is useful here because containment depends as much on access boundaries as on network boundaries.
The practical issue is that many organisations optimise for central visibility and central control, then discover that those efficiencies create common failure paths. Shared credentials, flat trust between sites, and always-on remote administration can turn one compromised location into a fleet-wide problem. Containment should therefore treat identity paths, operator access, and management planes as part of the same exposure surface.
Where facilities are coupled, the biggest mistake is assuming the first affected site is the only site at risk. Shared tooling, replicated configurations, and identical access patterns can create correlated compromise, so teams need to decide early whether they are dealing with a local incident or a distributed one.
What containment should prioritise during the first response window
Initial actions should focus on isolating the blast radius, preserving evidence, and keeping essential operations stable. If a control network or management plane is suspected, disable only the paths that are needed for spread, not the paths that keep the plant safe. If the compromise appears to involve stolen access, rotate or revoke the relevant access paths first, then evaluate whether the same identities are used elsewhere.
The attacker path matters because multi-site events often reuse the same entry point across locations. Colonial Pipeline ransomware attack shows how a single remote-access weakness can create an outsized operational impact when access hygiene is poor. In a multi-facility scenario, that lesson extends to every shared remote channel, not just the one that appears compromised first.
Teams should also preserve the ability to operate in degraded mode. That may require local override procedures, offline procedures for essential functions, and separation between supervisory access and routine business access. If segmentation is too coarse, you risk stopping the spread but also stopping the service.
Risk and Threat Considerations
Multi-facility incidents raise the risk of correlated compromise, where the same credential, remote path, or shared management control lets an attacker expand across sites faster than the response team can isolate them. In critical infrastructure, the danger is not only loss of confidentiality or integrity, it is loss of safe operational continuity if containment is too blunt.
Failure mechanism: Common administration routes, shared trust relationships, and replicated configurations let compromise propagate laterally from one facility to another before defenders can separate the environments. If containment is delayed, the attacker may also reach backup, monitoring, or recovery systems that were assumed to be outside the blast radius.
Impact: The result can be simultaneous disruption across multiple sites, longer restoration time, and a harder decision between preserving operations and preserving clean recovery paths. In the worst case, responders may be forced to choose between partial outage and wider contamination.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication, and Access Control | Multi-site containment hinges on limiting shared access paths between facilities. |
| PR.SC-07 — Supply Chain Risk Management | Shared vendors and managed connections can propagate compromise across facilities. | |
| RS.MA-01 — Incident Management | Early containment and coordinated isolation are core incident-response actions here. | |
| Recommendation — Limit cross-facility access paths and revoke shared credentials before spread widens. Constrain third-party access routes that can extend an incident across sites. Execute coordinated containment actions that isolate affected sites while preserving essential services. | ||
| NIST SP 800-53 Rev 5 | AC-4 — Information Flow Enforcement | Segmentation and controlled inter-site flows are central to containing lateral movement. |
| IA-5 — Authenticator Management | Shared or stolen credentials can let one compromise reach multiple facilities. | |
| SC-7 — Boundary Protection | Boundary controls are the main technical mechanism for blast-radius reduction. | |
| Recommendation — Enforce boundaries that block unauthorized traffic between affected environments. Rotate or revoke exposed authenticators and service credentials across impacted sites. Strengthen internal boundaries to isolate the incident and preserve safe operations. | ||
| CIS Controls v8 | CIS-12 — Network Infrastructure Management | Network segmentation and controlled administration paths are essential to containment. |
| CIS-17 — Incident Response Management | The question is about coordinated containment across multiple affected sites. | |
| Recommendation — Segment shared networks and restrict administrative paths between facilities. Use incident playbooks that define rapid isolation and continuity steps for multi-site events. | ||
Practitioner Guidance
What to prioritise: Start by identifying which access paths and management channels are shared across the affected facilities, then isolate those first. If the same credential or administrative plane can reach more than one site, treat it as a high-priority containment target even before full root-cause analysis is complete.
What to verify: Confirm that segmented sites can still operate safely with local control, local visibility, and a known fallback path for essential functions. A containment plan is not ready if it depends on central systems that may already be compromised.
Practitioner takeaway: In critical infrastructure, containment succeeds when you separate trust domains fast enough to stop spread, while still preserving the smallest viable operating mode for each affected facility.
Related resources from NHI Mgmt Group
- How should security teams prioritize patching when multiple unauthenticated critical CVEs land in core infrastructure libraries at once?
- How should security teams contain AI-speed attacks once the first exploit lands?
- How should security teams contain agentic AI attacks once execution starts?
- How should critical infrastructure teams contain ransomware once attackers have gained an initial foothold?
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 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org