Topic starter
27/10/2026 7:07 pm
TL;DR: Juneau’s water utility says a supply-chain incident and undocumented remote nodes exposed how lean OT teams can lose control of critical infrastructure, while visibility and segmentation improved uptime from roughly 85% to 99.99%, according to Dragos. The lesson is that operational memory is not a security control when access paths, asset inventory, and response decisions depend on a handful of people.
Editorial analysis by NHI Mgmt Group, based on content published by Dragos: “How Juneau’s Water Utility Closed Its OT Blind Spots”.
Key questions
Q: What breaks when OT environments rely on undocumented assets and operator memory?
A: Containment breaks first.
Q: What breaks when default passwords remain on OT systems?
A: Default passwords turn critical infrastructure devices into easy entry points, especially when those systems are internet-exposed or poorly monitored.
Q: How should critical infrastructure teams prioritise visibility over emergency response tools?
A: Prioritise visibility first when the team cannot confidently answer what exists, how it communicates, or what can be isolated.
Practitioner guidance
- Build a complete OT asset-and-flow inventory Document every remote node, communication path, and operational dependency before making further segmentation changes or control decisions.
- Eliminate default and shared credentials in field systems Find every login system that still relies on common passwords or local operator knowledge, then replace it with managed authentication and revocation processes.
- Map containment zones to the real network graph Use the actual communication pattern to define which nodes can be isolated or quarantined during an incident, rather than relying on legacy diagrams.
Bottom line: The article shows that OT blind spots are not a theoretical problem when undocumented paths, weak credentials, and lean staffing meet critical services.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →