Industry
Utilities
Water, gas, and municipal utilities need cybersecurity that supports reliable service and safe operations. Legacy controls, remote sites, limited staffing, and supplier access make prioritization essential: start with the pathways that could affect treatment, distribution, dispatch, or the ability to recover.
Field notes · 01
Make remote sites and control assets visible
Create an inventory covering control systems, operator workstations, telemetry, remote terminals, communications links, and vendor-managed equipment. Record who operates each asset and whether it can be safely scanned, patched, or disconnected. Include cellular gateways and remote-access devices that may sit outside ordinary office management.
Use Librarian to organize asset information and identify missing ownership. Validate the inventory with operations personnel before drawing conclusions from network observations. Passive monitoring may be preferable for sensitive systems, and any new collector or integration should undergo a review for performance and operational impact.
- Remove unnecessary direct internet exposure.
- Document the approved path for every external maintenance connection.
Field notes · 02
Control changes without compromising safety
Limit administrative access to named users and separate everyday office work from control-system administration. Where older equipment cannot support modern authentication, protect the access path through managed gateways and restrictive network rules. Review changes to configurations and operating parameters with people who understand the process.
Shield + SHADE can support detection and remediation planning within agreed boundaries. Do not equate automation with permission to change operational equipment. Operators must approve any consequential action, including account revocation or network isolation, when service delivery or physical safety could be affected.
- Revoke temporary vendor access after maintenance.
- Keep emergency-access procedures usable when normal authentication services fail.
Field notes · 03
Prepare a recovery plan staff can actually use
Maintain protected copies of approved configurations, contact lists, restoration instructions, and required software or licensing information. Test how the utility would operate during loss of business systems, communications, or a major supplier. Manual procedures must be reviewed for safety and feasibility rather than assumed to be available.
Dewey can help organize response activities, and Growler can support evidence preservation. Utility leadership, operators, counsel, and relevant authorities should agree on incident roles and reporting responsibilities. For water systems, use sector-specific guidance alongside broader operational technology practices; requirements and available support vary by utility type and jurisdiction.
- Exercise a remote-site incident with operations and the maintenance provider.
- Track recovery gaps through assigned corrective actions and follow-up testing.
Further reading
These links are background sector guidance, not validation of every recommendation or Aktoh capability. Aktoh role descriptions outline possible workflows; confirm supported connections, access, and scope before relying on them. The sources do not endorse Aktoh. Requirements depend on your organization, contracts, and jurisdiction; this page is not legal advice.
What we see here
Use the sector guidance above to identify critical systems, access risks, and recovery priorities. Coverage depends on the systems you connect and the workflows you configure.
How the fleet responds
Agents investigate and prepare recommendations in parallel. System-changing actions require approval by default; you choose which action classes can run automatically.
What you get back
Review plain-language findings and available audit records. Relevant agents can help organize evidence; your team remains responsible for compliance decisions.
Why there are no logos on this page
We do not identify customers without permission. Security scenarios on this site are illustrative unless accompanied by verified supporting evidence; they are not proof of customer outcomes or performance guarantees.
Start free. Add credits only when the work justifies it.
Run the whole fleet across unlimited nodes at zero platform fee — you pay only for tokens. Move to a pooled plan when the usage justifies the lower rate.