Water and wastewater operators face a difficult combination: essential services that cannot stop, infrastructure built over decades, widely distributed assets, limited technical resources, and growing cyber exposure. A single utility may operate treatment plants, pumping stations, lift stations, reservoirs, and remote facilities across generations of PLCs, RTUs, HMIs, and SCADA systems.
Modernizing all of it at once is rarely realistic. The immediate challenge is more practical: know what is running, know when it changes, protect the configurations needed for recovery, and keep critical infrastructure operating when something goes wrong.
The operating profiles below are representative composites, not descriptions of individual AMDT customers.
A water utility operates treatment facilities alongside dozens of remote pumping, booster, and monitoring stations connected through radio, cellular, and other remote-access technologies. Its PLC and RTU estate has accumulated over several decades.
The risk is no longer theoretical. Between November 2023 and January 2024, Iranian-affiliated actors compromised at least 75 Unitronics devices, including at least 34 in U.S. water and wastewater facilities. According to a joint CISA, FBI, NSA, EPA and international advisory, attackers erased original ladder logic, replaced it with their own, renamed devices, restricted upload and download functions, and even reset software versions to older values to interfere with operators’ ability to communicate with the PLCs.
The same advisory makes the recovery requirement unusually explicit: operators should create and test strong backups of PLC logic and configurations and maintain replacement hardware for critical functions.
And the pressure has continued. In July 2026, a coordinated cyberattack targeted operational technology at more than 30 Minnesota community water systems. State and federal authorities responded, while affected communities reported disruptions to automated controls but no known impact on drinking-water quality.
The operational lesson is simple: if the controller itself is compromised, teams need an independent record of what should be running.
Octoplant turns PLC and automation backup into a managed, repeatable process. Supported configurations and programs are collected on defined schedules, historical versions are retained, and comparison capabilities help teams identify when the operational state differs from previous versions.
This matters when the information presented by the affected system itself can no longer be trusted. Instead of relying only on a project file found on an engineering workstation or the version reported by the controller, teams have a separate historical record from which to investigate the change and identify an appropriate recovery state.
Failed backup jobs and unexpected differences also become visible before the day they are needed.
For a water utility, recovery is not primarily about the value of the PLC. It is about restoring the process that PLC controls — pumping, pressure, treatment, storage, or wastewater movement. A trusted configuration history reduces one of the biggest uncertainties during that recovery: what exactly should this controller be running?
The device can be compromised. The knowledge needed to recover it shouldn’t be.
A municipal utility or water district operates a treatment facility and multiple remote assets with a small technical team. The same people responsible for SCADA and automation may also handle maintenance, vendors, cybersecurity requirements, documentation, and on-call incidents.
Many utilities do not have dedicated OT security teams or specialists for every generation of automation they operate. GAO identifies workforce shortages, older technology, and competition for limited financial resources as persistent barriers to improving water-sector cybersecurity.
That makes manual resilience processes particularly fragile. Backups may depend on someone remembering to connect an engineering laptop. Current programs may sit on local drives. A contractor may make a legitimate change during maintenance without that change becoming part of a central history.
And when something changes unexpectedly, the first challenge can simply be establishing whether it was an error, an authorized modification, equipment behavior, or malicious activity.
For a lean organization, adding another recurring manual process isn’t a sustainable answer. The process has to work when the experienced engineer is busy, unavailable, or eventually leaves.
Octoplant moves configuration backup and version history out of individual memory and into a repeatable operational process. Scheduled jobs maintain historical states across supported devices, while configuration comparison helps identify differences between versions.
Instead of asking engineers to manually document every device state, the technical history accumulates as part of normal operations. Teams gain a common reference for troubleshooting, maintenance, recovery, and investigating unexpected changes.
That is particularly valuable across remote infrastructure where the automation estate may be geographically distributed but the expertise required to maintain it is concentrated in only a few people.
Small technical teams do not need more administration. They need critical processes that continue without constant attention.
Automating backup and maintaining configuration history reduces dependence on individual knowledge, strengthens handovers between employees and contractors, and makes recovery information available when the person who normally knows the answer isn’t there.
Critical infrastructure shouldn’t depend on one person’s memory.
A wastewater operator manages treatment works, pumping stations, and distributed control systems while operating under environmental permits, discharge limits, reporting obligations, and increasing scrutiny of operational performance.
Wastewater operations do more than control physical processes. Their systems also support the operational context behind flow, level, dosing, pumping, treatment, and other information used to understand how facilities were operating.
When that operational state cannot be reconstructed, technical problems can become compliance problems.
The scale of that exposure is visible in enforcement. In 2021, Southern Water received a record £90 million fine after pleading guilty to 6,971 illegal sewage discharges lasting 61,704 hours. Importantly, the Environment Agency said the company had deliberately presented a misleading picture of compliance, hindering proper regulation.
The issue remains current. In July 2026, Southern Water received another £7.1 million fine following pollution incidents involving equipment failures, delayed reporting, and inadequate operational oversight.
Octoplant does not monitor water quality or replace environmental monitoring systems. But these cases illustrate a broader point: when regulators investigate what happened, the ability to establish how critical operational systems were configured can become part of the evidence.
What changes with Octoplant.
Octoplant maintains historical configuration information across supported automation systems, giving engineering teams a technical record of how those systems changed over time.
If a pump, dosing process, level control, PLC program, or other automation function comes under investigation, teams can compare historical configurations and establish whether the relevant control system changed during the period in question.
That history does not replace process data, environmental monitoring, operator records, or regulatory reporting. It adds another layer of operational evidence: what the automation was configured to do and how that configuration changed.
What it’s worth.
When an operational incident becomes a regulatory investigation, reconstructing the technical state after the fact is slow and uncertain.
Maintaining configuration history continuously gives operations, engineering, and compliance teams evidence they can use alongside process and environmental records — without beginning the investigation by searching engineering laptops and asking who remembers making a change.
Evidence is more valuable when it already exists before someone asks for it.
| The exposure | Why it matters | AMDT's answer | |
|---|---|---|---|
|
PLC manipulation | Attackers have demonstrated that they can replace ladder logic and interfere with the information operators use to understand a device | Historical versions and configuration comparison provide an independent operational record |
|
|
Recovery readiness | Pumps, treatment, pressure, storage, and wastewater movement cannot wait for configurations to be reconstructed | Automated backup preserves trusted historical states for supported systems |
|
|
Aging automation | Utilities often operate technology generations that cannot simply be replaced or secured like modern IT | Vendor-independent backup and version management bring supported legacy and modern systems into a common process |
|
|
Limited staffing | Small technical teams cannot sustain resilience processes that depend on repetitive manual work | Scheduled backup and centralized history reduce dependence on individual memory |
|
|
Remote infrastructure | PLCs and RTUs may be distributed across treatment works, pumping stations, lift stations, and other remote facilities | Centralized backup status and configuration history provide a common view across distributed assets |
|
|
Operational evidence | Investigations may require teams to reconstruct how critical control systems were configured at a particular time | Version history and comparison add configuration evidence alongside process and compliance records |
|
|
Enterprise visibility | Larger operators need to understand assets, lifecycle, backup coverage, vulnerabilities, and risk across facilities | Octovision extends trusted Octoplant data into a cross-site operational view |
| For water and wastewater operators, resilience means more than cybersecurity. It means keeping an essential service recoverable despite aging technology, distributed infrastructure, limited resources, equipment failure, human error, or cyberattack. | |||