From the Utility Management edition of October 29, 2026
Malicious Cyber Actors Targeting Water and Wastewater Sector Internet-Facing Programmable Logic Controllers, Causing Operational Disruptions
Federal Bureau of Investigation and U.S. Environmental Protection Agency · Water and wastewater operational technology · United States (utilities in at least seven states)
- Publisher
- Federal Bureau of Investigation
- Original publication
- 30 Jul 2026 (Public Service Announcement)
- Source retrieved
- 2026-10-30
- Event date
- 2026-07-27
What happened
Since 27 July 2026, water and wastewater utilities in at least seven states reported attacks on internet-exposed Rockwell/Allen-Bradley MicroLogix 1100 and 1400 PLCs; actors changed IP addresses and passwords, causing loss of view and in some cases control, and at least one victim found modified ladder logic. Reported effects included loss of pressure and flooding. Similar third-party network setups across victims may let attackers multiply successes. FBI and EPA recommend removing PLCs from internet exposure via secure gateways, strong unique passwords, access control lists, and securing cellular modems.
Why it matters
Any AI analytics or optimization that reads from or writes to utility OT expands the same attack surface; this alert sets the baseline controls municipal water systems must have before connecting AI to SCADA/PLC data.
Evidence and measured results
Federal PSA based on incident reports to the FBI; specific victims and counts per state not disclosed. The companion CISA alert reported boil water notices and sustained manual operations.
Limitations and uncertainty
The alert does not involve AI; it is included as a security precondition for AI-in-OT work. Dated July 2026, outside the immediate news window, but the campaign is recent and the first edition for this stream has no prior security baseline.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Water utilities have internet-exposed controllers and integrator-built remote access that attackers are exploiting.
- Stakeholders
- SCADA/OT manager
- CISO or IT director
- Utility director
- System integrator
- Discovery questions
- Do you know whether any PLCs are reachable from the internet?
- Which third parties have remote access to OT, and how is it brokered?
- How long can you run in manual operations?
- Value hypothesis
- Closing exposure first may let utilities adopt OT analytics without adding new attack paths.
- Potential engagement
- OT exposure and remote-access assessment ahead of any AI data integration.
- Unsupported claims
- That AI tools prevent PLC tampering
- Specific victim counts per state
Pre-sales engineering
Role takeaway
- Fit
- Mandatory precondition for any AI touching OT.
- Architecture and integration
- Brokered or one-way data paths from OT to analytics environments.
- Prerequisites
- OT asset inventory
- Network diagrams
- Integrator access list
- Constraints
- Small-utility staffing
- Legacy PLCs
- Security
- Remove inbound exposure, strong unique passwords, ACLs, monitored modems.
- Proof of value
- Exposure scan
- Architecture review of one analytics data flow
Delivery
Role takeaway
- Work
- Exposure discovery, hardening, gateway deployment and manual fallback testing.
- Dependencies
- Integrator cooperation
- Maintenance windows
- Ownership
- SCADA/OT manager with CISO.
- Skills and adoption
- Operators need refreshed manual-operation drills.
- Governance checkpoints
- Integrator access review
- Sign-off before new vendor OT connections
- Acceptance criteria
- Proposed: verified zero internet-exposed PLCs
- Proposed: tested manual operations procedure
- Risks
- Undocumented connections
- Service disruption during changes
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
OT connectivity for analytics, including AI platforms and remote vendor access, should be brokered through secure gateways with no inbound internet exposure and monitored modems.
Governance
Who approves, reviews and stays accountable for outcomes?
Third-party integrators' repeated network templates are a shared risk; utilities should review integrator and vendor remote-access arrangements before adding AI vendors.
Security and privacy
What data, permissions and controls need testing?
Direct: PLC tampering produced physical effects. AI projects needing OT data should not create new internet-facing paths.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Small systems may lack OT security staff; manual operations depend on trained operators.
Procurement
What should contracts, pricing and exit terms secure?
Integrator and AI vendor contracts should require secure remote-access patterns and disclosure of reused network templates.
Operating model
Which teams own the service once it runs?
Treat OT security sign-off as a gate in AI project intake.
Publication history
- 2026-10-29Utility Management · Issue 0110 resources
Stable resource ID: fbi-epa-psa-water-plc-attacks-2026