
Utilities are often asked to show that their operational technology is protected, and the paper trail for that showing usually starts with a supplier. A vendor letter, a product datasheet, or a conformance sheet can read like evidence. It is closer to a claim. Before a utility files one as proof of anything, it helps to know what was tested, under which conditions, and by whom.
What the regulatory signal covers
Water Finance and Management reported that the National Association of Water Companies (NAWC) commended a resolution from the National Association of Regulatory Utility Commissioners (NARUC), with the resolution "flagging several cybersecurity concerns pertaining to water systems." As summarized, that report describes a concern being raised and endorsed. It does not describe a test method, a pass threshold, or a vendor obligation, and a utility should not assume that any of those exist yet. A flag of this kind tells you where attention is expected. It does not tell you what counts as adequate.
Four gaps a claim can hide
Scope comes first. A test on one product version, one firmware build, or one standalone unit says little about the same model installed behind a remote access gateway or joined to a shared network. Ask which version was tested and which configuration it ran in.
Conditions come second. An attestation may describe controls that the product supports but that the buyer must enable, or that default settings leave off. The letter does not show that your installation turned them on. Compare the controls named in the claim with the controls your own staff have verified in the field.
Dates come third. A letter signed for one release can outlive the code it describes. Record the release identifier next to the date, and treat any claim whose release does not match your installed version as unverified until someone confirms the match.
Independence is the fourth gap. An attestation written by the party that sells the product is a different kind of document from a test run by a third-party laboratory, and the two should not share a column in the record. A laboratory report usually names its methods, equipment, and limits in ways a sales letter often does not. Neither is automatically sufficient, but the log should show which one is in hand.
Configuration drift is the quiet risk
Even a well-scoped test describes a moment. Once a system is installed, staff change passwords, add remote users, apply firmware updates, and adjust alarm thresholds. Each change can move the system away from the tested state. The attestation stays fixed while the installation moves.
A practical response is periodic reconciliation. At a set interval, or after any change the utility records as significant, compare the installed version and enabled controls against the logged claim. Where they differ, reopen the entry. The cost is staff time and a short list of questions for the vendor. The benefit is a record that describes the system as it runs, not as it was sold.
A filing rule for the asset record
Log each attestation with four fields: product and installed version, scope of the test, party that performed it, and date of the test. An entry missing any of the four is filed as claim only, a label that tells a reviewer the paper exists but the evidence does not yet. The label accuses no one. It keeps the record honest about what the utility knows.
Expect pushback. Vendors may resist sharing full test reports, citing confidentiality, and may offer summaries instead. A summary can be useful, but it moves the scope question back to the utility. If the summary does not name a version and a configuration, the log should say so plainly rather than filling the gap with the product name.
There is a tradeoff here. Demanding full reports adds procurement time and may narrow the pool of vendors willing to bid. A utility that accepts only summaries accepts more uncertainty. Neither choice is free, and the record should state which one was made.
Close the claim before it closes the question
A vendor attestation is a useful starting point for a cybersecurity review and a poor end point. Its value depends on the scope, conditions, and date it carries, and on whether a utility has checked those against what is installed. Until that check is written down, the paper says the vendor made a statement. It does not say the system was tested as operated.