Controls engineering / Article / Architecture study 01
A reference design for separating business systems, plant controls and remote pump stations—without sacrificing the operator’s ability to run the process.
Published 5 November 2026 · v1.0 · No live utility represented
The operating brief
Actual assets, protocols, water-quality limits, interlocks, redundancy and fail-safe behavior must be established with utility operators and the responsible engineers. “Stop every pump” is not a universal safe state.
Engineering heuristics / Review lens
Use these proposed heuristics during design reviews. They are not a compliance checklist or universal operating instructions. The source-to-decision register below distinguishes published guidance from this reference design.
Identify what failure or manipulation would do to water quality, supply, pressure and operator visibility.
Group assets by operational need and consequence. Shared Ethernet does not imply shared access.
Record endpoints, service, purpose, approving owner, review date and the consequence of blocking it.
Use replicated reporting; distinguish read, command and programming permissions. A port allowlist alone cannot enforce all three.
Scope accounts, engineering workstations and remote sessions to assigned systems. Review shared infrastructure as a common failure path.
Define services retained, local procedures, staffing, abort limits and decision authority before an incident.
Pair each negative security check with successful alarms, control or maintenance. Unspecified thresholds mean Not ready.
Restore version-identified configurations on isolated equipment and verify behavior; successful backup jobs are not sufficient evidence.
Record a named owner, rationale, compensating measures, expiry and retest. Do not let temporary broad access become permanent.
Process first / Network second
This simplified surface-water treatment example connects process stages to controls and consequences. Other treatment methods and site layouts will differ. Chemical storage, detailed piping, interlocks, bypasses and instrument loops are deliberately not specified.
Cell placement is a proposed refinement of the overview: disinfection needs its own reviewed boundary. It is not an assertion that Cell B or a separate safety instrumented system fits every facility.
Download process diagram · SVGOperation / Containment / Recovery
Each mode is a pre-engineered policy, not a command to disconnect equipment. Restrictions should target affected services while preserving only the paths operations can still trust and safely use.
Download operating modes · SVG
Record the incident or precaution, affected paths and authority. Validate local staffing, alarm availability and approved fallback. Apply the rehearsed policy; monitor process trends.
Establish containment and configuration provenance. Validate replacements, credentials and restored logic on isolated systems. Prevent replay of stale supervisory commands.
Reconnect in stages. Witness security and functional checks, record exceptions and obtain named signoff. Unexpected behavior stops restoration and triggers the approved rollback or isolation plan.
Named decision-maker, time, policy/configuration version, trusted paths retained, alarm and process baseline, owner-approved tolerances, rollback trigger and operator acknowledgment. Tests T03, T05, T06, T08, T10 and T11 provide the existing review hooks. None has been executed.
These modes apply NCSC isolation-planning guidance to the reference utility; the particular retained paths and transition gates are our proposed design.
Worked example / PS-01 remote pump station
Follow the control responsibility—not just the network cable.
PS-01 is an illustrative distribution booster station with a local pressure sensor, pump drive, RTU and local operator interface. These identifiers belong only to this walkthrough; they are not a real asset inventory. The site-specific hydraulic design, pump arrangement and protection remain unresolved.
PT-01 pressure feedback → RTU-01; LOP-01 local operator panel ↔ RTU-01. Local control stays at PS-01. Arrows show conceptual communication, not wiring or a deployable configuration.
PT-01 supplies local pressure feedback. RTU-01 executes the approved control sequence and permitted commands to VFD-01/P-01. SCADA-01 displays values, quality, operating mode and alarms through GW-01.
Operator: checks fresh telemetry and authority before an approved supervisory command. Programming is a separate F06 maintenance activity.
Evidence: baseline trends, command acknowledgments, access decisions and configuration versions. Verify an approved command works while an unauthorized programming attempt is denied on lab endpoints.
After the approved timeout, SCADA-01 marks remote values stale and raises the configured communications alarm. RTU-01 follows its engineered loss-of-link behavior using valid local inputs; WAN loss alone does not define whether a pump should stop or continue.
Operator: follows the approved response and local staffing plan. Local alarms may remain available, but delivery to central SCADA cannot be assumed during the outage.
Evidence: simulator timeline, stale indication, local trends and response record. If PT-01 also fails, this is a separate fault requiring an approved response—not the same fallback.
Confirm the cause is resolved and GW-01/RTU-01 configurations are trustworthy. Reconcile data quality, timestamps, current mode, active alarms and pending commands. Stale commands must not execute merely because the link returns.
Operator: witnesses current state before supervisory control is released under an approved sequence. A cyber incident also invokes the restricted-mode approval gates above.
Evidence: command lifecycle results, restored alarm delivery, access logs and named acceptance. Unexpected actuation or missing alarms stops the exercise and invokes the approved contingency.
Evidence status: Proposed. Simulator-tested: no. Site-verified: no. This narrative describes expected behavior, not an executed simulation.
Requirements → decisions → evidence
R-PS identifiers are proposed requirements for this example. Flow IDs refer to the existing communication matrix; T IDs refer to the acceptance plans. Each row remains Proposed / NOT RUN.
| Need / requirement | Decision & connection | Verification: denial + useful operation | Evidence / accountable role | Open acceptance gate |
|---|---|---|---|---|
| R-PS01 Local operation during WAN loss | RTU-01 owns the approved local sequence; F07 carries supervision. | T06 / T08: isolate the simulated WAN; confirm approved local behavior and operator access. | Logic version, trend and outage timeline / Controls + operations | Fallback envelope, timeout and supported outage duration TBD. |
| R-PS02 Trustworthy operator visibility | SCADA-01 shows freshness and quality; no silent use of stale values. | T06: missing updates produce stale status and alarm within the approved limit; current values return with validated quality. | Timestamped HMI captures and alarm record / SCADA owner | Freshness limit, alarm latency and acknowledgment procedure TBD. |
| R-PS03 Limit changes to authorized engineers | Separate operational F07 from time-bound F06 programming; deny D01 office access. | T01 / T04: unauthorized engineering access denied; approved monitoring and scoped maintenance still function in the lab. | Rule counters, access logs, project diff / Controls + network | OEM enforcement of read/write/program permissions and endpoints TBD. |
| R-PS04 No unexpected actuation on recovery | Validate command freshness, current authority and pending state before release. | T06: stale/expired commands do not execute; a newly authorized command works in the simulator. | Command and acknowledgment timeline / Controls + operations | Protocol-specific expiry, queue and restart semantics TBD. |
| R-PS05 Recover known configurations | F11 protected backups for RTU, HMI and gateway; isolated restore first. | T10: restore to spare/simulator, verify versions and expected control/alarm behavior. | Hashes, restore duration and functional results / Recovery owner | Recovery time/point targets and compatible spare hardware TBD. |
| R-PS06 Retain required process protection | Define local protective functions and sensor-fault handling through hazard review. | T11 / T06: specialist-reviewed simulation demonstrates approved response; access restrictions do not impair protection. | Hazard review, cause/effect record and test traces / Process + controls | Protection design and independent validation required; ordinary RTU is not assumed safety-rated. |
Guidance basis: existing NIST/NCSC decision register. These requirements and test mappings are our proposed application of that guidance, not quoted mandates.
Commissioning / Witnessed acceptance
A review checklist with gates, evidence and a stop rule—not a live switching procedure.
Current state: NOT READY. Named owners, limits and evidence are unassigned. All checks below are unexecuted. Marking a document complete cannot substitute for witnessed test results.
Gate: signed scope and limits. Owner: operations + controls lead.
Gate: restoration rehearsed; evidence retained. Owner: recovery + operations.
Gate: witnessed results accepted; simulator limitations recorded. Owner: controls + network + operations.
Gate: paired security and process evidence meets signed criteria. Owner: site operations + change lead.
Gate: recovery tests pass without unexpected actuation. Owner: controls + operations; incident lead when applicable.
Gate: no unresolved safety-critical failure; named acceptance and handover. Owner: accountable utility owner.
Requirement/test ID · environment (simulator or site) · equipment and configuration versions · approved expected result and threshold · observed result · pass/fail/not run · UTC/local timestamps · tester and witness · evidence location · deviation and corrective action · signoff and next review date.
Keep actual site addresses, logic, credentials and detailed operating limits in the utility’s controlled records. A future public case study should contain only approved, sanitized evidence.
01 / Trust boundaries
The industrial DMZ provides controlled exchange services. Behind it, the site operations, engineering, management and process zones have distinct access policies. Facilities, guest devices and safety-related systems do not inherit general production access.
On a small screen, scroll the diagram horizontally for detail. Arrows show selected connection initiators, not all data directions. The flow matrix below includes engineering, logging and recovery paths omitted from this overview.
Download presentation diagram · SVGVLANs define groups; enforced routing policy defines access. Avoid dual-homed workstations, unmanaged cellular routers and vendor tunnels that bypass the boundary. Boundary devices and management paths need their own tested recovery and redundancy design.
02 / Communication contract
This is a proposed allowlist, not a deployable firewall configuration. All unlisted inter-zone traffic is denied by default after dependencies are discovered and approved. “TBD” entries are unresolved design gates; do not substitute broad port ranges. Replies on an established session are different from permission to initiate a new session.
| ID | Initiator → destination | Decision / service | Restriction | Accountable owner | Test |
|---|---|---|---|---|---|
| F01 | Reporting users → DMZ replica | Allow: HTTPS 443, named application/users | Read replicated metrics only; no control API. | IT + data owner | T01 / T02 |
| F02 | OT historian exporter → DMZ broker | Allow: TLS-protected replication; exact port TBD | New sessions originate in OT; stateful replies allowed. Data export is not a hardware one-way boundary. | OT + data owner | T02 |
| F03 | Approved vendor → DMZ access broker | Conditional: HTTPS 443 + MFA | Named identity, device posture, site approval, short access window; no routed vendor VPN into OT. | OT access owner | T03 |
| F04 | DMZ broker → OT jump host → assigned engineering station | Conditional: product-specific session transport | Separate allowlists on each hop. No broad desktop access or general file transfer; broker compromise remains a risk. | OT engineering | T03 / T04 |
| F05 | SCADA server → assigned cell PLC/RTU | Allow: exact OEM control protocol, port and endpoints TBD | Only approved operational reads/writes. Verify direction with actual protocol. Port filtering alone does not distinguish read from write. | Process + controls | T01 / T05 |
| F06 | Assigned engineering station → assigned controllers | Conditional: exact OEM engineering services TBD | Approved change ticket, backup, local operator authorization and time-bound access. No programming from office machines. | Controls lead | T04 |
| F07 | SCADA master → remote RTUs through telemetry gateways | Allow: selected telemetry protocol inside authenticated tunnel where supported | Site-specific addresses; no general branch-to-branch access. Legacy radio/serial requires protocol and latency review. | Telemetry lead | T06 |
| F08 | OT update/transfer service → DMZ staging | Conditional: approved HTTPS retrieval | Validate signature/hash, malware checks, compatibility and change approval. Staging does not authorize installation. | OT maintenance | T07 |
| F09 | OT assets → local DNS / time / identity | Allow: individually documented infrastructure services | Do not share corporate privileged accounts. Specify ports and authentication behavior from real dependencies, not a generic all-services rule. | OT platform owner | T08 |
| F10 | OT collectors → DMZ log relay → enterprise SIEM | Allow: approved TLS log transport | Buffer locally; no SIEM-initiated management path back into controllers. Avoid loading fragile endpoints with agents. | SOC + OT | T09 |
| F11 | OT backup service ↔ approved OT assets | Conditional: documented backup transport | Dedicated credentials and endpoints; protected offline/immutable recovery copy. Validate backup load and restore on spare equipment. | Recovery owner | T10 |
| D01 | Enterprise / public internet / facilities → PLC or RTU | Deny | Includes IPv6, wireless, cellular, alternate VPNs and dual-homed laptops. | Network owner | T01 |
| D02 | Cell A ↔ cell B; remote site ↔ remote site | Deny unless explicitly engineered | Document process dependencies before enforcement. No any-to-any lateral route. | Controls + network | T05 |
| D03 | General OT / vendor sessions → safety engineering | Deny by default | Status-only interfaces and maintenance access require separate safety review; never assume an ordinary PLC is a safety system. | Process safety owner | T11 |
Roles are proposed; named owners remain unassigned. For production, add exact addresses, protocol versions, rule IDs, change tickets, rule expiry, IPv6 policy and documented dependencies.
03 / Resilience walkthrough
These are design expectations and evidence requirements, not simulated test results.
Corporate IT unavailable
Design expectation: local PLC control and required OT services continue within the approved operating envelope. Business reports may become stale and must show that clearly.
Prove it in a lab: remove simulated corporate identity/WAN dependencies, exercise operator sign-in and verify alarms, time synchronization and subsequent recovery. Do not disconnect a real plant as a demonstration.
Pump-site WAN lost
Design expectation: the RTU follows approved loss-of-communications logic; central SCADA flags stale telemetry. A local operating procedure addresses conditions that exceed that fallback.
Prove it in simulation: verify timeout, stale flags, safe local control, operator response and reconnection. Evaluate queued commands; do not assume automatic replay is safe.
Vendor access revoked
Design expectation: revoking a vendor session stops remote maintenance access while local operators retain monitoring and control.
Prove it on a test workstation: expire the approved window, attempt reconnection and measure revocation delay. Confirm no persistent tunnel, unmanaged account or scheduled tool remains.
04 / Prove both sides
Each test needs a security result and a positive operational result. Establish numerical targets for alarm latency, data freshness, packet loss, recovery time, access revocation and process limits before execution. Unspecified targets mean Not ready, not Pass. Emergency access must remain auditable and must not bypass safety controls.
Lab, then approved boundary check
From a designated IT test host, attempt one approved connection to a safe test endpoint representing the controller zone; inspect rule counters. Do not scan a production PLC.
Lab → observation
Show a changing synthetic process value on the DMZ replica and dashboard; attempt a forbidden reverse session to the isolated test endpoint.
Lab → approved maintenance session
Try an unapproved user, then an approved named user to a test workstation; expire and revoke the session.
Lab / spare controller only for writes
Use an approved engineering station to back up and perform a harmless lab change; confirm another workstation is blocked.
Lab; production change window only after signoff
Use synthetic endpoints across cells to verify deny rules; observe actual approved SCADA traffic passively.
Simulator first; controlled exercise only
Simulate WAN loss and recovery; verify RTU loss-of-link logic, alarm delivery/stale indication and reconnection.
Lab / staging only
Transfer an approved signed package and a harmless hash-mismatched sample; do not install updates on live controls.
Lab / tabletop, then approved resilience window
Model corporate identity, WAN and cloud unavailability; exercise local OT sign-in and the documented emergency-access process.
Passive observation
Generate one benign boundary-denied test and verify delivery to the monitoring team; compare controller/network load against baseline.
Isolated spare / simulation
Restore a selected PLC project, HMI configuration and firewall policy to nonproduction equipment; verify versions and expected behavior.
Safety specialist-led review / simulator
Review safety interfaces and maintenance access; simulate loss of supervisory communications without manipulating a live protective function.
05 / Change without losing control
Inventory equipment and every access path. Capture passive traffic over representative operating and maintenance cycles. Confirm the process owner’s limits and dependencies.
Test rules, remote access, loss of services and restoration in an isolated environment. Resolve every TBD and preserve a known-good configuration.
Use an approved window and a limited boundary. Operator stays in control. Observe alarms and process trends; stop and restore the approved configuration on any abort trigger.
Review paired security and continuity evidence. Obtain operations and engineering signoff. Recheck after material changes and on an owner-approved schedule.
Keep UTC and local timestamps, tester and witness, approved scope, asset/configuration versions, baseline and post-change trends, firewall decisions, alert/session records, rollback outcome and unresolved exceptions. Store sensitive plant detail in the utility’s controlled repository, not a public portfolio.
Teaching boundary: the separate pump demonstration illustrates failure and recovery concepts. It does not validate this architecture or any plant acceptance test. Site-specific engineering, hazard analysis and independent acceptance evidence remain necessary.
Decision register / Source-backed review
These government publications are stronger foundations than a vendor brochure. They support principles, not certification of this design. Exact topology, protocols, equipment and acceptance thresholds remain engineering decisions.
| Decision | Primary publication | How we apply it | What it does not establish |
|---|---|---|---|
| Industrial DMZ and process zones | NIST SP 800-82 Rev. 3 · Final, September 2023. Full publication PDF. See network segmentation discussion and Figure 16. | Separate enterprise, exchange services and process control. Our F01–F07 paths make permitted communication explicit. | Does not prescribe our exact number of zones or firewall rules. Revision 4 is an initial public draft as of this review, not the final baseline. |
| Brokered maintenance access | NIST SP 1800-45 — Water and Wastewater Build Architecture (OT Remote Access) · Final, June 24, 2026. Full publication PDF. | The publication demonstrates three representative remote-access implementations for utilities of different capacities. Use it to evaluate F03/F04 against actual staffing and support needs; test authentication, scope and expiry in T03. | We have not reproduced its vendor configurations or validated a specific product. A demonstrated example is not a complete security assessment of our utility design. |
| Contain compromise inside OT | NCSC secure connectivity, Principle 6 · Official guidance. Full principles PDF. | Keep treatment cells and engineering access separately controlled; test the lateral restrictions in T04/T05. Protect gateways as significant shared dependencies. | Segmentation cannot make an already-authorized malicious control command safe. Application permissions and process protection remain necessary. |
| Isolation without blind shutdown | NCSC secure connectivity, Principle 8 — Establish an isolation plan · Official guidance. | Prepare and rehearse service-specific isolation and continued local operation. T06/T08 test dependencies and recovery before any live exercise. | No universal safe pump state, outage duration or automatic permission to disconnect telemetry. Utility operators and responsible engineers approve these choices. |
Verified 29 October 2026. These links lead to the publishers; no third-party paper has been rehosted. The reference topology, flow matrix and acceptance plans are our original interpretation and remain unvalidated.
Sources & interpretation
This original reference design uses segmentation and controlled remote access principles. The topology, flow IDs, acceptance tests and scenario expectations are proposed engineering choices for this example, not requirements quoted from a standard.
Sources checked 29 October 2026. No assertion of certification, compliance, a complete threat model or security of any actual facility.