Midwest Water News

Covering the water that covers the Midwest

Infrastructure

Who Holds the Keys to the Pump Controls? Questions Midwest Towns Can Ask About Water Cybersecurity

A recent resolution from state utility regulators has put cybersecurity on the table, and a Midwest reader can test a local water system's readiness with a few plain questions.

By Staff ·

Midwest Water News

When a water system fails, most customers picture a broken main or a pump that stopped running. A growing share of the risk sits somewhere a customer never sees: in software that opens valves, starts pumps, and reports chemical levels back to an operator's screen. A recent resolution from the National Association of Regulatory Utility Commissioners, the group that brings together state utility commissioners, has drawn attention for that reason. The National Association of Water Companies publicly commended it, and Water Finance and Management's report on the NAWC endorsement says the resolution is "flagging several cybersecurity concerns pertaining to water systems."

Where the risk sits in a small system

A typical town water system has a treatment plant, wells or an intake, storage tanks, and a network of pumps and valves. Many of those pieces report to a central screen through control software, sometimes over telephone lines, radio links, or the internet. Operators use that connection to watch levels, change settings, and respond to alarms. The same connection can become a path for an outsider if it is set up poorly, and the office computers that run billing, payroll, and email can be targets too.

Small utilities face this problem in a specific way. Many rural and small-town systems share staff with a road crew or a city hall, and they often rely on one outside contractor for computer support. Nothing about that arrangement is careless on its own. It does mean that a single shared password, an old remote login, or an unpatched device may not belong to anyone's full-time job.

Questions a Midwest reader can actually ask

You do not need to read code to ask useful questions. Start with who can reach the system from outside the plant, and how. Ask whether remote access requires a separate login for each person, whether shared or default passwords have been replaced, and whether someone reviews who still has access when staff or contractors leave.

Next, ask what happens if the computers stop. A system that can run by hand is more resilient than one that cannot. Ask whether operators have written procedures for running the plant manually, and whether those procedures have been practiced. A printed page kept inside the control building is a simple sign that someone planned for a bad day.

Then ask who is responsible and who gets told. Ask whether the utility has a written plan for responding to an attack or a suspicious outage, who makes the call to the state, and whether the local board or council receives a briefing at least once a year. If the answer is that the contractor handles it, ask to see the contract section that covers security responsibilities.

What a resolution does and does not do

A resolution from a national association of commissioners is a statement of position. It can shape what state regulators discuss, what utilities are asked about, and what standards may later be written, but it does not by itself change a town's systems or its budget. The real decisions happen in state rules, rate cases, capital plans, and local board votes. That is where a reader can follow the issue.

Oversight differs from state to state, and some small systems fall outside routine state commission review depending on how they are organized. A reader who wants to see how their own system fits into that picture can start with the utility's annual report, the state agency that regulates drinking water, and the minutes of the board meeting where the budget is discussed. If cybersecurity appears in none of them, that absence is itself a useful question to bring to the next meeting.

Keep the question specific

Cybersecurity can sound abstract, which makes it easy to shrug off or to fear without acting. A more practical approach is to ask for concrete answers in plain language: who has access, what is backed up, what is written down, and who gets the call. A utility that can answer those four questions clearly is likely in better shape than one that offers only general reassurance. A utility that cannot answer them has given the community its first useful item for the next agenda.