Water Quality Wire

The National Association of Water Companies (NAWC) commended a resolution passed by the National Association of Regulatory Utility Commissioners (NARUC), according to a report by Andrew Farr at Water Finance and Management. The summary of that report says the NARUC resolution is "flagging several cybersecurity concerns pertaining to water systems." The summary does not list those concerns, quote the resolution's operative language, or name a compliance date, so nothing below assumes any of them.

Read the chain of authority before reading the headline. An association resolution states a position that member commissions and other bodies may consider. By its own force, it does not change a utility's permit conditions, tariff, or contract. Binding obligations usually arrive later, through a commission order, a state rule, a procurement term, or a condition attached to a financing agreement. Each of those has its own text, scope, and effective date, and each may apply to some utilities and not others.

Where a broad concern lands inside a utility

A cybersecurity concern written at the commission level rarely arrives as a single task. It lands on records a utility already keeps, or should keep. The first is an inventory of operational technology: programmable controllers, supervisory software, sensors with network interfaces, and the servers that collect their data. The second is an access register showing which employees, contractors, and vendor accounts can reach those systems, from where, and under what approval. The third is a change record covering firmware updates, configuration edits, and password resets, with dates and the name of the person who made each change. The fourth is the incident path: who declares an event, who notifies the state agency, and who can isolate a system without stopping treatment.

Each file answers a different question, and a gap in one does not show up in the others. A complete access register with no current inventory tells a reviewer who can reach devices that may no longer be documented. A detailed inventory with no change record tells a reviewer what is connected but not whether it has been altered.

The tradeoffs in building the record

Building these files costs staff time that many small systems do not have to spare. The inventory is usually the hardest part, because the list of connected devices is often assembled from several sources that disagree, including older drawings, procurement files, and vendor portals. A utility that builds a complete list may also create a detailed map that should not circulate widely. The security group should hold the full version, while management and commissioners receive a summary that shows coverage without exposing addresses, network layouts, or credentials.

Vendor remote access creates a separate tradeoff. Remote support lets a small utility reach a qualified technician quickly, which matters during an outage. The same channel is a path that security reviewers routinely examine, because an unapproved session can reach a control system from outside the plant. Restricting remote access may slow repairs, while leaving it open gives an unknown party a route in. No single setting removes both costs. The practical decision concerns who approves each session, how long access remains open, and whether the session is logged.

What to write now, before a proceeding asks

Write the answers down before a commission staff member, auditor, or board member asks for them. Start with three questions. Which controllers could a network intrusion reach, and which of them could change treatment or pressure? Which accounts can reach those controllers today, and when was each one last reviewed? If an alarm sounded tonight, who would decide to disconnect a system, and who would call the regulator?

Then record the uncertainty. If the inventory is incomplete, say so and date the gap. If the vendor list is unclear, name the missing item and the person assigned to close it. A written gap with an owner is more useful to a reviewer than a clean document that cannot be checked against the plant.

The resolution does not tell a utility what its own answers should be. It makes the questions more likely to be asked. Until the resolution's full text and any follow-on commission action are read, no utility can know which records will be required, in what format, or by when. The sensible course is to prepare the four files described above, keep each one current, and treat the first version as a draft that will need correction.