Decision RecordActivePublished without chair review
CRT-2026-042124 Oct 2026AFTERNOON EDITIONDaily Roundtable
Water utility controller compromise response
Water utilities that identify unauthorized controller changes, operator lockouts, or matching compromise indicators should treat the event as an incident-response emergency. They should establish safe local operational control, restrict unnecessary remote access, preserve evidence, rotate affected credentials, and validate controller configurations against known-good engineering records.
Current public guidance · the full record
What to do now
At a glanceThe edition's authoritative action board carries no action for this record's subjects — no What to do now guidance.
Why now
Under reviewOn 24 October 2026, the roundtable reviewed reports of PLC password and IP-address changes that caused operator lockouts at U.S.
water systems. A lockout means operators may no longer have trustworthy administrative control even when process manipulation has not been demonstrated. Delay can prolong that loss of control, while indiscriminate isolation can remove OT visibility needed for safe operation.
The immediate priority is therefore to restore safe local control, preserve evidence, and then restrict unnecessary remote access. The missing direct CISA advisory limits attribution and scope claims, but it does not justify waiting when a utility observes the response triggers directly.
Who is affected
Under reviewWater and wastewater utilities that observe unauthorized PLC or controller password changes, IP-address changes, operator lockouts, or matching compromise indicators face an incident-response emergency because administrative control may be untrustworthy.
Treatment and distribution operators at those utilities must preserve safe local control and a safe operating envelope while containment proceeds.
OT engineers, controller administrators, and incident responders must preserve configurations and logs, rotate affected credentials, restrict unnecessary remote access, and validate controller state against known-good engineering records.
Utilities without matching indicators are not placed in incident containment by this decision; they should rapidly harden remote access and validate controller administration.
Communities served by the utilities belong in the impact assessment, but the packet does not establish contaminated water, unsafe treatment, or public-safety harm.
What supports this
SupportedSupport — The water-sector defender's 24 October 2026 assessment reports PLC password and IP-address changes that locked some operators out; this supports treating matching observations as an incident-response emergency, while its government attribution lacks a direct advisory in the packet.
Support — The moderator's synthesis says unauthorized PLC password and IP changes establish administrative-plane compromise but do not alone prove altered treatment logic or public-safety harm; this supports the decision's response threshold and evidence boundary.
Support — The defense architect's analysis places safe local control, independent communications, and a safe operating envelope before severing access that may carry OT visibility; this supports safety-led containment rather than indiscriminate disconnection.
Support — The final synthesis makes safe restoration of local control the first priority even without confirmed process manipulation. Evidence gap — The evidence assessment found the operational sequence consistently supported but found no primary CISA source for the underlying incident account.
How the Roundtable reached this
Under reviewThe operational scout identified unauthorized PLC or controller changes and operator lockouts as the threshold for emergency response.
The water-sector defender reported password and IP-address changes that locked operators out. The moderator separated this demonstrated administrative-plane compromise from unproven changes to treatment logic or public-safety impact.
The defense architect resolved the main operational tension—whether to disconnect immediately—by placing safe local control, independent communications, and a safe operating envelope before severing unnecessary remote access.
The evidence assessment found consistent support for that sequence but identified the missing direct government advisory. The boundary assessment therefore limited the conclusion to conditional response guidance rather than claiming government confirmation.
A linkage check found no matching prior record, and the arbiter selected a new operational decision record.
Positions are generated by AI specialist personas and chaired by Halil Öztürkci.
Panel composition
- Scout (AI panel role)Scout identified 7 candidate signals.
- Linker (AI panel role)Linker evaluated 7 relation judgments.
- Evidence Auditor (AI panel role)Evidence Auditor recorded 15 evidence signals; 9 gaps.
- Prediction Steward (AI panel role)Prediction Steward accepted 0 predictions and rejected 2 claims.
- Boundary Reviewer (AI panel role)Boundary Reviewer recorded 15 public/private findings.
- Arbiter (AI panel role)Arbiter produced 7 decision envelopes.
Key disagreement
Scout (AI panel role)
Administrative-plane compromise is established, but process manipulation, unsafe treatment conditions, and public-safety impact are not confirmed. Reported incident scale also combines separate accounts. | Merged related signal (candidate-6): When should Initia and affected rollups restart after the reported bridge and authorization failure? | Merged related signal (candidate-7): How broadly should X100 governance and treasury authority be disabled after the reported governance exploit? | Merged related signal (candidate-11): How should potentially affected BlackX systems be investigated and recovered? | Merged related signal (candidate-12): When should an iPhone exposed to DarkSword infrast
Arbiter outcome
Arbiter outcome: new decision record. The operational response is strongly supported, no matching prior record was found, and the missing primary advisory can be handled through cautious wording.
Candidates considered
Considered 7 candidates · opened 1 · 6 not opened (6 other)
Considered, not opened
Sign in to preview Considered-Not-Opened entries (moves to Pro at launch).
Sign in to preview practitioner entries.
What is uncertain
MissingThe available material establishes reported administrative access changes and operator lockouts, not whether attackers changed controller logic, treatment setpoints, alarms, or physical processes.
It does not establish contaminated water, unsafe treatment conditions, or a public-safety consequence. The identity and number of affected utilities remain uncertain because the reported totals combine separate accounts, and public attribution is not established in the packet.
These uncertainties limit impact and attribution claims; they do not remove the need for immediate response when a utility directly observes unauthorized controller changes, lockouts, or matching compromise indicators.
What evidence is missing
MissingThe packet does not contain the direct CISA advisory, citation URL, or another primary government source for the reported PLC password changes, IP-address changes, and operator lockouts.
It also lacks forensic evidence establishing altered treatment logic, unsafe setpoints, contaminated water, or public-safety impact. Reports of targeting above 100 systems and remediation across at least 12 states come from separate accounts and are not independently reconciled here.
No PLC vendors, controller models, firmware versions, remote-access products, site list, or complete compromise-indicator set is provided, so the precise technical scope cannot be enumerated.
What would change this
Under reviewEvidence that controller logic, treatment setpoints, alarms, process telemetry, or independent measurements were manipulated—or that safe local control was lost—would require escalation from administrative compromise to a process and safety incident.
A known-good comparison and log review showing no unauthorized controller changes, no lockout, and no matching compromise indicators would place a utility in rapid hardening and validation rather than emergency containment.
A direct CISA advisory or equivalent primary source could clarify attribution, affected scope, indicators, and product details; it would strengthen the incident account but would not change the conditional need to respond when a utility directly observes unauthorized changes or lockouts.
What to watch next
Under reviewAfter containment, continuously compare process telemetry, controller logic, setpoints, alarms, and independent physical measurements with known-good engineering records.
Watch for renewed password or IP-address changes, recurring operator access failures, unexpected controller-state differences, and loss of safe local control.
Escalate the impact classification immediately if these checks show process manipulation, unsafe operating conditions, or loss of reliable control.
Maintain the administrative-compromise classification when review finds only unauthorized access changes and no process deviation, while continuing credential recovery, evidence preservation, and configuration validation.
Evidence basis
Sara’s confirmed PLC password/IP changes and operator lockouts make water safety the first gate, even without proof of process manipulation. I challenge Alex’s “isolate every k0t-positive appliance immediately” only where that appliance car…
The clearest shift is from headline severity to evidence-based response thresholds. In the water-sector case, unauthorized PLC password and IP changes—and resulting operator lockouts—establish compromise of the controller’s administrative p…
**FACT:** CISA confirms attackers changed PLC passwords and IP addresses, locking out some operators. Reporting puts the targeting above 100 systems and remediation across at least 12 states, although those figures come from separate report…
Summary: CISA’s report of operator lockouts at U.S. water systems makes safe restoration of local control today’s first priority, even without confirmed process manipulation. CISA KEV listings put Collabora Online CVE-2026-110447 and Arista…
Public value history
- 24 Oct 2026Initial public guidanceCurrent guidance
Created the first public value version for this Decision Record.
Source RoundtableAfternoon roundtableConvened 24 Oct 2026Methodology
How the panel reaches a Public Decision Record.