From the Utility Management edition of November 6, 2026
EPA advisory: AI service providers requesting water/wastewater SCADA and operational logs via public records
U.S. Environmental Protection Agency Office of Water (Emergency Response and Cybersecurity) · Water and wastewater utilities / federal advisory · United States
- Publisher
- EPA Office of Water GovDelivery bulletin
- Original publication
- 2026-06-05
- Source retrieved
- 2026-11-07
What happened
EPA’s 5 June 2026 advisory warns water and wastewater systems about disclosing sensitive operational information after multiple public-records requests from AI service providers, as reported by WaterISAC and AWWA. In at least one instance, an AI provider requested all SCADA logs for 2026 for treatment, distribution and wastewater systems, plus daily/hourly historical logs for flows, water-quality baselines, reservoir/tank levels and energy or equipment run-times. EPA concurs that aggregating such operational data across utilities could reveal patterns and vulnerabilities usable to disrupt service. Utilities are urged to make risk-informed decisions consistent with state information-protection laws. Why now: NARUC’s 8-11 Nov WC-1 draft seeks FOIA protections for cyber-incident sharing and WRRO minimums amid the same OT data-exposure risk surface.
Why it matters
Direct OT/AI security control for U.S. SLED water utilities: treat AI vendor data requests for SCADA/process historian extracts as high-risk even when framed as research or model training. Newly relevant alongside this week’s NARUC WRRO/CISA draft.
Evidence and measured results
Opened the EPA GovDelivery bulletin text dated 06/05/2026 09:50 AM EDT from Office of Water Emergency Response and Cybersecurity.
Limitations and uncertainty
Advisory dated June 2026 (older than last run) included for why-now linkage to NARUC WC-1 vote week. Does not name the requesting provider or quantify how many utilities received requests.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- AI vendors and public-records requesters seeking bulk OT logs create cyber exposure.
- Stakeholders
- CISO
- Utility counsel/records officer
- Plant superintendent
- State primacy agency
- Discovery questions
- Have you received AI-related SCADA or historian requests?
- Who approves public-records releases involving OT data?
- What redaction standards exist today?
- Value hypothesis
- A triage and minimisation playbook reduces breach-via-FOIA risk without blocking legitimate analytics.
- Potential engagement
- OT data-classification and request-triage workshop aligned to EPA advisory.
- Unsupported claims
- Federal ban on all AI data requests
- Named threat actor attribution
- Automatic FOIA exemption without state law
Pre-sales engineering
Role takeaway
- Fit
- Controls and data-governance overlay—not an AI model deploy.
- Architecture and integration
- Classify historian/SCADA exports; provide feature stores or aggregates instead of raw logs for AI POCs.
- Prerequisites
- Asset/data inventory
- Legal review channel
- Logging of records requests
- Constraints
- State public-records variation
- June advisory date
- No technical control catalogue in the bulletin
- Security
- Deny bulk multi-system SCADA log releases by default; require risk review.
- Proof of value
- Triaged request log
- Zero unconstrained SCADA dumps in pilot window
- Documented redaction examples
Delivery
Role takeaway
- Work
- Draft SOP, train records/cyber staff, tabletop an AI vendor request scenario.
- Dependencies
- Counsel availability
- WaterISAC/AWWA guidance uptake
- Executive sponsorship
- Ownership
- Records officer executes releases; CISO owns cyber risk decision.
- Skills and adoption
- Short training for customer service/records staff who first see requests.
- Governance checkpoints
- SOP legal review
- First live request after-action
- Annual playbook refresh
- Acceptance criteria
- Signed SOP
- Request log template in use
- Escalation path tested
- Risks
- Political pressure to over-release
- Inconsistent state law interpretation
- Shadow AI POCs bypassing SOP
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?
Segment and classify SCADA/historian exports; require legal and CISO review before fulfilling broad AI-related records requests; prefer redacted aggregates over raw logs.
Governance
Who approves, reviews and stays accountable for outcomes?
Align public-records response playbooks with cyber risk reviews; coordinate with counsel on state disclosure laws versus security exceptions.
Security and privacy
What data, permissions and controls need testing?
Bulk SCADA and process logs enable reconnaissance; aggregation across utilities amplifies sector risk as EPA states.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Small utilities without counsel or CISO capacity need shared playbooks via WaterISAC/state associations.
Procurement
What should contracts, pricing and exit terms secure?
AI vendor contracts and POCs must forbid unconstrained SCADA-log collection; require data-minimisation clauses.
Operating model
Which teams own the service once it runs?
Records and cyber teams must jointly triage AI-related information requests before release.
Publication history
- 2026-11-06Utility Management · Issue 097 resources
Stable resource ID: epa-advisory-ai-providers-requesting-water-scada-logs-2026