A deliverables guide for operators, engineering and security teams

Water and Wastewater Deliverables Your Operators Can Act On

A findings list becomes a deliverable when it tells an operator which treatment step is exposed, what evidence supports the finding and who owns the fix. This guide sets out the records and reports to agree before the assessment begins.

Illustrative water treatment infrastructure.

A Report That Connects Every Finding to Operations

The written scope defines the facilities, the methods, the records and the outputs, and the deliverables follow from it. The sections below set out the contents a water or wastewater owner agrees before work starts, and each one names the record an operator, a compliance owner or a regulator will look for. Together they form a planning outline, and the engagement defines which of them you receive.

System and Responsibility Map

The map identifies the treatment and remote sites, the supporting IT services, the engineering access, the vendor connections and who owns each part of the scope, down to the cellular telemetry link and the dosing controller vendor. It records the dependencies that matter to pumping, treatment, monitoring or recovery in enough detail to act on, marks each relationship as observed, exported or reported, and holds sensitive architecture in the restricted technical record, apart from the document that will circulate.

Findings With Traceable Evidence

Each agreed finding records the observed condition, the source and date of the supporting record, the operational dependency it affects and the confidence the evidence supports. It states whether the conclusion rests on configuration review, interviews, records or authorized validation, so a reader knows how much weight it will bear, and it uses Observed, Suspected and Unresolved as defined states rather than impressions. That is the same discipline a forensic examiner applies to a report that may be questioned later, and it is why a finding that a vendor account can reach the dosing controller is written as an allowed path, an observed session or a demonstrated reach with the specific evidence behind it.

Corrective Action Register

Every entry carries an assigned owner, a practical next step, an agreed priority and the evidence needed to judge whether the correction worked. Recommendations stay separate from implementation work and from verified results, each with its own date, and the areas outside this round of testing stay on the register as named items for the next round. The register sequences the work the way a utility can actually do it, so the replacement vendor support path the operators rely on is in place before the old remote access is cut.

Recovery and Incident Readiness Record

The record documents the selected function's configuration, software, communications, backup and vendor dependencies, along with any exercise or approved test, its result, its boundaries and the further work it points to. It distinguishes a restore that was demonstrated from one that was described, lists the preservation responsibilities and records the coverage of the relevant logs and time sources, because that coverage shapes what an examiner can reconstruct after an incident.

Two Reporting Levels That Serve Different Readers

Management receives the operating consequences, the decisions in front of them and the residual risk they are being asked to accept. Restricted technical detail goes to the operators, engineering and security staff responsible for the corrective work, with configuration versions and the exact closure criteria. Handling and retention of both follow the requirements agreed in the engagement.

Where the Report Fits in Your Compliance Work

A technical report is one defined input to the AWIA risk and resilience assessment, the emergency response plan or a state certification, and acceptance of each rests with the regulator that reviews it. The engagement identifies the contribution the report makes, names the party responsible for each remaining piece of work and lists the requirements assigned to other workstreams, so the compliance owner can see every open item beside its owner. Global Digital Forensics has served businesses since 1992, and the conversation that defines that contribution is free.

Read the preparation guide next, or open the water and wastewater assessment service to agree on the deliverables with us.

Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .

Privacy center

Choose your site settings

Optional technology stays off until you choose otherwise. You can change these browser settings at any time. Access to the core site does not depend on optional technologies.

Technology preferences
Sale or cross-context sharing: not used GDF does not sell or share website personal information for cross-context behavioral advertising.