CISA and Five Eyes agencies release joint OT isolation blueprint amid active water utility attack

What Happened

CISA, joined by cybersecurity agencies from the UK, Australia, Canada, and New Zealand, published "CI Fortify," a six-step blueprint for isolating operational technology (OT) during cyberattacks. The guide instructs critical infrastructure operators to build dedicated isolation points into vital systems so essential services can continue even when networks are deliberately cut off from the outside.

The release lands alongside two active incidents cited in coverage: CAF Bank suspended online services after a third-party software vulnerability, and a coordinated attack disrupted OT systems at more than 30 Minnesota water utilities. Minnesota's water utilities and CAF Bank both show what happens without a fallback communication layer during forced isolation: coordination breaks down at the exact moment it matters most.

Minnesota Water Utilities: What We Know

• Attack window: July 26-27, 2026. Minnesota IT Services (MNIT) confirmed the intrusion publicly on July 28 and activated a statewide cybersecurity incident response.

• More than 30 community water and wastewater systems were affected; Braham, Plymouth, South St. Paul, and Maple Plain publicly disclosed impact to automated control functions.

• Contingency procedures kept water and wastewater service running in most affected communities. The Minnesota Department of Health reported no municipality issued a change-in-use advisory to residents.

• Attribution is unconfirmed as of July 29. MNIT is coordinating with CISA, the EPA, and the FBI, and has noted access-pattern similarities to intrusions seen in other states and sectors without naming a responsible actor.

• Federal context: CISA Advisory AA26-097A, updated in the same window, tracks Iranian-affiliated actors exploiting programmable logic controllers (PLCs) across U.S. critical infrastructure. Reporting has noted the timing aligns with that broader activity, though no formal link to the Minnesota attacks has been established.

• Structural risk factor: the U.S. has roughly 150,000-170,000 water systems, most of them small and under-resourced. A 2024 EPA Office of Inspector General audit found the majority of water systems reviewed were not current on required risk assessments and emergency response plans.

The Six Steps

1. Identify vital systems and networks

2. Identify critical customers

3. Identify common levels of criticality and trust for networks and hosts

4. Identify potential isolation points and map connections to vital systems

5. Build effective separation and isolation points

6. Create and test an isolation plan

Why It Matters

The guide's central instruction is blunt: organizations must build physical isolation points into vital systems and treat carrier-provided networks as untrusted and potentially hostile. That requirement creates an immediate operational gap. If an agency isolates its OT or IT network, how does it keep personnel informed and coordinated during the isolation event itself?

This is a mass notification and emergency communication problem before it is anything else. The guide assumes operators can isolate infrastructure; it does not solve how command staff, field personnel, and affected customers stay in contact once that isolation happens. That gap is where the BlackBerry portfolio sits.

How BlackBerry Fits the Blueprint

Recommended Actions Based on the Blueprint

• Pair any OT/IT isolation plan with a communication continuity plan. Isolation without a coordination channel just delays the disruption, it doesn't prevent it.

• Inventory which emergency and command communications currently depend on the same carrier or IT infrastructure being isolated. That dependency is the gap CI Fortify doesn't close.

• Test the isolation plan and the communication fallback together. The guide's own six-step process ends with "create and test an isolation plan"; notification and coordination should be tested as part of that same exercise, not separately.

• Prioritize out-of-band, multi-channel notification for any zone identified as a candidate for graduated isolation, so command visibility survives the isolation event itself.

BlackBerry Perspective

"CI Fortify" tells agencies to isolate their networks. It doesn't tell them how to stay connected once they do. The consequences of Minnesota's water utilities and CAF Bank both show what that gap costs in practice: services down, no clear fallback for command and coordination. BlackBerry AtHoc is built for exactly that gap: verified, multi-channel emergency communication that operates independently of the infrastructure it's reporting on.