Water Quality Wire

The National Association of Water Companies has added its voice to a cybersecurity question that regulators have begun raising. In a report by Andrew Farr for Water Finance and Management, the association is described as commending a resolution from another body, the National Association of Regulatory Utility Commissioners, which the summary describes as "flagging several cybersecurity concerns pertaining to water systems." The summary available for this article does not list the individual concerns, so this piece does not restate them. It asks a narrower question that the resolution raises for operators: what does a plant still do when its digital controls cannot be trusted? For the original report, see Water Finance and Management's coverage of the NAWC endorsement of the NARUC cybersecurity resolution.

A resolution sets attention, not a control design

A commission resolution and an association endorsement are both statements of position. They tell utilities which issues have reached the table. They generally do not, by themselves, change a pump station's logic, a valve's authority, or a vendor's login. Binding duties arrive through rules, orders, contract terms, and statutes, and the timing and wording of those instruments vary by jurisdiction. An operator reading a resolution should treat it as a signal to check its own assumptions, not as a finished requirement.

Why the manual path is the test

Most modern water systems rely on supervisory control and data acquisition, in which a central screen issues commands to programmable logic controllers at pumps, valves, and chemical feeds. The efficiency gain is real, but so is the dependence. If the network is isolated after a suspected intrusion, operators need to know which local controls still work, which setpoints can be changed at the panel, and whether pumps and feeders hold a safe state without a remote signal. Those answers are often assumed rather than tested.

There is a tradeoff. Cutting remote access reduces the paths an intruder can use, but it also removes the remote alarms and trend data operators use to spot abnormal conditions. A plant that isolates its network in a hurry may find that it is blind as well as protected. A procedure written in advance can specify which functions stay on local control, which are held in a safe state, and who is authorized to make each decision.

A drill that does not require an attack

Testing manual operation does not require simulating a threat. A utility can schedule a planned exercise during ordinary hours, announce it to the operations team, and take the remote connection down for a defined window with a documented rollback. The exercise should record three things: which local controls respond as expected, how long the plant takes to reach a safe condition, and which step required someone to make a call that was not written down. The last item is usually the most useful.

Several limits apply. A drill carries its own risk, so the operator should confirm that the plant can ride through the window and that a supervisor can end the exercise early. Some functions may depend on vendor support or on a credential held outside the utility, and those dependencies belong on the record too. The outcome also depends on how each plant was built, which the resolution does not address and this article cannot judge for any specific system.

What to do with the signal

The useful reading of the NAWC and NARUC attention is practical. Before the next commission question or budget cycle, a utility can reconcile three documents that often sit in different offices: the list of connected control assets, the list of remote access paths and the people who hold them, and the manual operating procedure for each critical process. When those three disagree, the gap is the item to fix first. None of this settles the broader policy question, which remains open. It does give a plant manager a concrete test to run.