Review your assessment scope with GDF
Agree on the system boundary, the people who can authorize work and the output your operators and management will actually use.
A preparation guide for water operators, engineering and security teams
An assessment goes well when the operator has already decided what is in scope, who can authorize work and which records exist. This guide walks a water or wastewater team through those decisions and the records to gather before the first site visit.

Use the planning materials to organize your own questions first, or bring the decision in front of you to a free scoping conversation with an examiner who will have to stand behind the findings later.
Agree on the system boundary, the people who can authorize work and the output your operators and management will actually use.
Preview the pack contents on this page, then request download access by email.
Read what a water or wastewater assessment report should contain before you agree on the engagement.
This preview is open to every reader. The examples are fictional and written for illustration.
Inside the pack
Water: connect remote access, treatment dependencies, monitoring and recovery records to RRA and ERP questions.
Inside the pack
Record the process boundary, approved methods, exclusions, stop conditions, recovery support and corrective owner. Fill the PDF locally after downloading it.
Question: Can a vendor account reach assets beyond its support task?
Evidence: Account approval, access group membership, jump host rules and a dated firewall configuration.
Verification: Pair configuration review with a reachability check.
Next step: Assign an owner and agree an operations approved verification method. Record the relevant RRA scenario and ERP dependency.
Eight page PDF with printable scope and action worksheets. Download it after a successful request.
Your email and selected pack go to GDF, and that is the whole of the request. Keep completed worksheets in your own records.
Request this planning pack by email
Use this supporting reference to organize the preparation records and questions for your engagement.Start by recording which system the scope concerns: drinking water treatment and distribution, wastewater collection and treatment, industrial water systems or a defined combination of them. Name the facility owner, the operator, the remote sites and the people responsible for engineering, IT and cybersecurity, because the assessment team will ask for each of them on the first call, and record the PWSID or permit number beside each system so that every later duty can be counted from it. A utility with twelve remote pump stations that lists one site owner has already shown the examiner where the first corrective action sits.
Then describe the decision the assessment has to support. It may be an initial assessment, an open finding from earlier work, a vendor connection, a planned change or a recovery question. Bring the existing assessment summaries and action lists with you, so the new work builds on what was already done and goes straight to the items still open.
The records an assessment draws on usually exist somewhere in the utility already. Gather the available plant and remote site network diagrams and asset records, together with the inventories of engineering workstations, historians, telemetry and vendor access. Add the account approvals, the remote access records and the relevant network configurations with their export dates, the backup inventories, the record of the last actual restoration, the key software and vendor dependencies for the SCADA servers and the dosing controllers, and the existing incident and emergency plan responsibilities, exercise records and open actions. The examiner reads the restore record before the backup policy and the last vendor account revocation before the access policy, because those two show whether the paper is followed.
The assessment team agrees with you which of these records are necessary and how they will be exchanged. This is a preparation list for your own use, and sensitive material moves by the exchange method you agree with the team. The list commonly surfaces a cellular telemetry link waiting for an owner, a vendor account that has outlived its project and an emergency response plan kept only on the corporate file share, which belongs in a copy operators can reach during the incident it was written for; record each one, because they are the first corrective actions.
Identify the sensitive equipment, the allowed methods, the maintenance windows, the person who can stop work and the recovery arrangements, and state them in operations' own terms: every setpoint, dosing rate, alarm limit and controller mode stays where operations set it, and the operator defines the baseline indicators that call a stop. Operations and engineering approve any active validation in writing, naming the exact target, method, tool version and window, and a concern is validated on a laboratory or representative system while the production controller keeps running the plant.
Population served, service connections, customers and treatment plant design flow are different measures, and the program that applies to your system depends on which one its rules use. Record each figure with its own evidence, confirm the applicable program with the responsible owner and advisers, and then sign each row of the applicability record. A technical cybersecurity review is one defined workstream that contributes to the risk and resilience assessment, the emergency response plan or the certification, and the report names which contribution it makes.
Set the facilities, the evidence, the report audience, the boundaries, the action owners and the proposed follow up before work begins, so the report lands with the people who will act on it. The Water and Wastewater Assessment Deliverables guide describes what to expect. Global Digital Forensics has supported businesses since 1992, and the conversation that sets those terms is free.
Download the four sector packs and the companion covering all fifty states, or build a workbook set for your own states, ownership and operating scope.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .