Decision RecordActivePublished without chair review
CRT-2026-044029 Oct 2026AFTERNOON EDITIONDaily Roundtable
Contain internet-exposed industrial VNC access
Enter a safety-focused incident posture, increase local supervision, verify process values and alarms, preserve relevant evidence, block direct VNC exposure without disrupting control communications, and replace it with brokered remote access using strong authentication and named accounts.
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
Partially supportedThe October 29, 2026 analysis identifies direct internet-facing VNC sessions as a path to operator-level control of industrial processes.
Because false, missed, or suppressed commands can affect refrigeration, pumps, ventilation, or treatment equipment, discovery of the exposure—not a calendar deadline—is the trigger for immediate local supervision, verification, evidence preservation, and safe containment.
The reported history of physical effects remains unverified in this packet and is not required to justify the response.
Who is affected
WeakThis applies to industrial deployments where VNC exposes operator consoles or HMIs directly to the internet, including water, refrigeration, ventilation, pumping, and treatment processes.
Operators face the risk of unauthorized or suppressed commands affecting process control. Personnel supervising refrigeration, pumps, ventilation, and treatment equipment face the consequence of equipment being tripped or an unsafe process continuing.
Network and remote-access administrators must remove the exposure without interrupting control communications and replace it with brokered access. No VNC vendor, product, or version boundary is supplied, so applicability is determined by the direct-exposure configuration rather than a named version.
What supports this
WeakSupport — Sara Kovacs’s October 29, 2026 industrial-control analysis identifies unauthorized operator-level control as the immediate safety risk.
It states that a false command can trip refrigeration, pumps, ventilation, or treatment equipment, while a missed or suppressed command can leave an unsafe process running.
Support — The supporting evidence assessment confirms that the cited analysis directly recommends a safety incident posture, increased local monitoring, evidence preservation, removal of direct VNC exposure without disrupting control communications, and replacement with monitored remote access using strong authentication and named accounts.
Evidence gap — A separate assessment finds that claims about reported physical damage and process disturbances are attributed to government sources but cannot be independently checked from this packet because those publications are not attached.
That gap limits the historical claims, not the independently stated operational response.
How the Roundtable reached this
WeakThe decision scout identified direct internet-facing VNC access to industrial operator consoles as an operational safety question and proposed local supervision, process verification, evidence preservation, careful containment, and brokered remote access.
The record linker found no prior Decision Record to update. One evidence assessment supported that response directly; another found that reported physical damage and process disturbances lacked the underlying authoritative publications.
The boundary review found the operational guidance public-safe because it includes safeguards against disrupting control communications.
The arbiter resolved the evidence limitation by treating the historical impact claims as supplemental rather than necessary and 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 12 candidate signals.
- Linker (AI panel role)Linker evaluated 12 relation judgments.
- Evidence Auditor (AI panel role)Evidence Auditor recorded 27 evidence signals; 15 gaps.
- Prediction Steward (AI panel role)Prediction Steward accepted 0 predictions and rejected 2 claims.
- Boundary Reviewer (AI panel role)Boundary Reviewer recorded 17 public/private findings.
- Arbiter (AI panel role)Arbiter produced 12 decision envelopes.
Key disagreement
Scout (AI panel role)
Not every claimed physical consequence was independently validated, and changing industrial segmentation or manual controls can itself create hazards if not performed under approved procedures.
Arbiter outcome
Arbiter outcome: new decision record. The evidence supports a safety-focused operational response to direct internet exposure of industrial operator consoles, and no existing record was identified.
Candidates considered
Considered 12 candidates · opened 1 · 11 not opened (11 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
ConflictingThe packet does not establish which sites currently expose VNC, whether unauthorized access occurred at a particular site, or whether any process value, alarm, controller logic, or setting changed.
Reported physical consequences were not independently validated because the underlying authoritative publications are absent.
Containment also carries operational risk: changing segmentation, remote access, or manual controls can create hazards if performed outside approved procedures or without safely validating control communications.
What evidence is missing
ConflictingThe packet does not include the cited CISA and Rewards for Justice publications needed to verify reports of physical damage, minor process disturbances, or a water operator switching to manual operation.
It also provides no site inventory, VNC product or version boundaries, VNC configuration details, access records, process and alarm histories, controller-logic comparisons, or known-good engineering records.
Those omissions limit conclusions about particular deployments and past consequences, but they do not remove the configuration-based trigger for the containment action.
What would change this
WeakA verified inventory showing that a site has no direct internet-facing VNC path to an industrial operator console would remove the immediate containment trigger for that site.
If safe validation shows that blocking the path would interrupt control communications, the implementation must be resequenced under approved operating procedures rather than performed as an abrupt disconnection.
Remote control may resume after brokered, authenticated access and command integrity are confirmed. Attaching the cited authoritative publications could strengthen or contradict the historical impact context, but the current safety response does not depend on those claims.
What to watch next
WeakOn the next day, inventory every site for comparable direct internet-facing VNC access to operator consoles and HMIs.
Compare controller logic and process settings with known-good engineering records, continue checking process values and alarms, and safely validate each network change.
Keep remote control disabled wherever authenticated access or command integrity remains unconfirmed; restore it only after both checks pass.
Evidence basis
The immediate safety risk is unauthorized operator-level control: a false command can trip refrigeration, pumps, ventilation, or treatment equipment; a missed or suppressed command can leave an unsafe process running. **Fact:** CISA says th…
Public value history
- 29 Oct 2026Initial public guidanceCurrent guidance
Created the first public value version for this Decision Record.
Source RoundtableAfternoon roundtableConvened 29 Oct 2026Methodology
How the panel reaches a Public Decision Record.