Complete toolkit ZIP
The starting guide, detailed guidance, duty reference, workbook, CSV files and controlled source data in one download.
Complete toolkit ZIPNew York Water Cybersecurity Toolkit
Give operators, assessors and water commissioners a clear account of what applies, what was examined and what needs action. Build the evidence behind your decisions, resolve gaps before deadlines arrive and bring GDF in when the work needs technical depth.
Entity, systems and period define the scope. Owners and sources build the evidence index, which connects exceptions and corrective work to verification.
Scope -> evidence -> finding -> verification.
One complete working set
A useful assessment connects each requirement to a scoped system, an examination and a decision. The November 18 toolkit gives your team 72 separate review records, an 11 sheet workbook, four reporting cards and two fictional examples showing how the records fit together. Download the files directly. No email or plant information is required.
The starting guide, detailed guidance, duty reference, workbook, CSV files and controlled source data in one download.
Complete toolkit ZIPRecord scope, evidence, examinations, corrective work, reporting and recurring reviews. Unknowns remain visible until examined.
Working workbookFollow the audit path and worked examples before assigning the records. The PDF is a reading copy; enter working records in the workbook.
Read the guideFrom operating facts to accountable decisions
Identify the facility, permit or public water system ID, population or design flow, connections and review period. Document the basis for every exclusion. A municipal water system and a private SPDES permittee may have different duties.
Connect inventories, remote access routes, account records, configurations, training and recovery tests to named owners. Use evidence references rather than copying sensitive plant records into the planning file.
Record the source criterion, examination method, sample, observation and limitation. Reading a policy or selecting Gathered in a planner does not establish that the control operates.
State the gap in plain language. Give the corrective action an owner, due date, dependency and interim measure. Keep statutory clocks and State directions separate from internal target dates.
Return to the affected control and record what was retested, when, by whom and with what result. A closed ticket is useful evidence only when it supports the required correction.
Show governing officials the operating risk, open work, resource request and responsible person. Retain the decision and supporting evidence. Keep unverified items visible in any certification preparation.
GDF can help establish the assessment scope, examine the technical evidence and identify the work needed next. Discuss your water assessment.
January 1, 2027
Covered community water systems have until January 1 to meet Appendix 5-E controls. Operator training and incident reporting are already effective. Confirm population, connections and each exclusion before assigning duties.
NYSDOH Appendix 5-E: Cybersecurity Requirements for Public Water Systems
March 11, 2027
POTW plans and controls have a separate implementation date. Incident reporting already applies to all SPDES permittees. Monitoring duties at design flows of at least 10 MGD include specific connection and device exceptions.
March 28, 2027
Prepare the first annual certification with the responsible municipal signatory and the records behind each statement. Keep operator training renewal periods and federal community water certification dates in their own records.
After a State significant deficiency notice, consult within 30 days. Within 120 days, correct the deficiency or comply with the applicable corrective action plan, following any earlier State required period to protect public health. The actual notice and direction control the working schedule. NYSDOH Subpart 5-1: Public Water Systems.
Record detection, awareness, identification and determination separately. One report does not close another authority’s task. Confirm the current agency channel before submitting.
NYSDOH Appendix 5-E: Cybersecurity Requirements for Public Water Systems: 5-E.1(c)(2); 5-E.5(e)
NYSDOH Appendix 5-E: Cybersecurity Requirements for Public Water Systems: 5-E.3(e); 5-E.9
NYSDEC adopted revised Part 750 express terms: 750-1.2(a)(27); 750-2.7(h)(1)
NYSDEC adopted revised Part 750 express terms: 750-2.7(h)(2)
The complete kit retains 71 requirements and one separately identified recommended exercise. These groups show the source and applicability for every record; the duty reference and workbook contain examination steps, acceptance descriptions and recurrence. Check your permit and any orders separately.
| Record and criterion | Duty and timing |
|---|---|
| Record the water system scopeNY-DW-SCOPE requirement 5-E.1(a); 5-E.2 | Community water systems serving more than 3,300 people; separate operator training scope. Determine coverage and any supported exclusion. The no connection exclusion retains incident response planning and incident reporting. Excluded municipal billing or other IT must not affect Subpart compliance. Timing: Before selecting duties; reassess when population, system boundaries or connectivity changes. Source: NYDOH-APP5E |
| Designate a qualified cybersecurity leadNY-DW-PERSONNEL requirement 5-E.4(a) | Covered systems serving a combined wholesale and retail population greater than 50,000, subject to applicable exclusions. The owner designates the responsible individual based on demonstrable cybersecurity knowledge and practical system protection or risk management experience. The rule does not require a named professional certification. Timing: By January 1, 2027 and while this scope applies. Source: NYDOH-APP5E |
| Put the cybersecurity lead in the emergency planNY-DW-LEAD-CONTACT requirement 5-E.4(a)(1) | Covered systems with combined wholesale and retail population greater than 50,000, subject to applicable exclusions. Include the designated individual's name and contact information in the water supply emergency plan. Timing: By January 1, 2027; keep current. Source: NYDOH-APP5E |
| Report program risks to the governing bodyNY-DW-BOARD-REPORT requirement 5-E.4(a)(2) | Covered systems with combined wholesale and retail population greater than 50,000, subject to applicable exclusions. The designated individual provides a confidential written report on the cybersecurity program and material risks to the governing body at least annually. Timing: At least annually after the January 1, 2027 compliance date. Source: NYDOH-APP5E |
| Complete the CVA and carry findings into the planNY-DW-CVA-PLAN requirement 5-E.1(c)(1); 5-E.5(a) | Covered water systems subject to the CVA provisions. Prepare and submit a cybersecurity vulnerability analysis and incorporate its findings into the water system emergency plan submitted to the State. Timing: By January 1, 2027; then follow review and submission triggers. Source: NYDOH-APP5E |
| Obtain the correct CVA approvalNY-DW-CVA-APPROVAL requirement 5-E.5(b) | Covered water systems subject to CVA provisions. An authorized representative approves the CVA. Above 50,000 combined wholesale and retail population, the designated cybersecurity lead approves it. Timing: When the CVA is completed or revised for approval. Source: NYDOH-APP5E |
| Assess risk to operations and protected informationNY-DW-CVA-RISK requirement 5-E.5(c) | Relevant IT, OT and nonpublic information that may affect Subpart compliance. Assess known vulnerabilities using likelihood of exploitation and consequences for normal operations. Timing: By January 1, 2027 and during CVA review. Source: NYDOH-APP5E |
| Evaluate controls across the water systemNY-DW-CVA-CONTROLS requirement 5-E.5(d) | Controls associated with supply, treatment, disinfection, pipes and valves, storage and operations management. Evaluate control effectiveness for maintaining Subpart compliance during a water supply emergency caused by a cyber incident. Timing: By January 1, 2027 and during CVA review. Source: NYDOH-APP5E |
| Report qualifying CVA vulnerabilitiesNY-DW-VULN-NOTICE requirement 5-E.1(c)(2); 5-E.5(e) | CVA vulnerabilities that may affect Subpart compliance, or a situation that may pose a public health risk. Report qualifying vulnerabilities or situations to NYSDOH in accordance with section 5-1.77. Timing: Within 48 hours of identification of the qualifying vulnerability or situation. Source: NYDOH-APP5E |
| Keep the CVA currentNY-DW-CVA-REVIEW requirement 5-E.1(c)(1); 5-E.5(f) | Covered systems subject to CVA provisions. Review and update the CVA for technology developments and evolving threats, including after major water facility infrastructure becomes operational. Timing: At least annually and within 30 days after major infrastructure changes become operational. Source: NYDOH-APP5E |
| Identify action for each vulnerabilityNY-DW-CVA-ACTIONS requirement 5-E.5(g) | Vulnerabilities identified by the CVA. Identify the actions needed to mitigate or remediate the vulnerabilities. Timing: During completion and review of the CVA. Source: NYDOH-APP5E |
| Use the department approved CVA formNY-DW-CVA-FORM requirement 5-E.5(h) | Covered systems subject to CVA provisions. Prepare the CVA in a form approved by NYSDOH. The GDF worksheets organize supporting work and do not replace that approved form. Timing: Before submission. Source: NYDOH-APP5E |
| Build the program from the CVA findingsNY-DW-PROGRAM requirement 5-E.6(a) | Covered systems subject to cybersecurity program provisions. Establish a cybersecurity program based on the findings of the system's CVA. Timing: By January 1, 2027 and maintained as risks change. Source: NYDOH-APP5E |
| Certify the program through the required submissionNY-DW-PROGRAM-CERT requirement 5-E.6(b) | Covered systems serving more than 50,000 combined wholesale and retail population, subject to applicable exclusions. The designated lead certifies compliance with 5-E.6(c) on a department approved form as part of the water system emergency plan submission. This is a program certification, not a professional credential. Timing: As part of the plan submission required by 5-1.33(e). Source: NYDOH-APP5E |
| Maintain separate reporting dutiesNY-DW-REPORTING-PROGRAM requirement 5-E.6(c)(1); 5-E.9 | Applicable statutory and regulatory reporting obligations. Make reporting part of the cybersecurity program and preserve other required notices alongside the DOH cyber incident notice. Timing: By January 1, 2027; incident reporting is already effective. Source: NYDOH-APP5E |
| Protect external access to operational technologyNY-DW-MFA requirement 5-E.6(c)(2)(i) | Individuals accessing covered OT from an external network. Require multifactor authentication unless the authorized representative or designated cybersecurity lead approves compensating controls in writing. Timing: By January 1, 2027 and for each access route. Source: NYDOH-APP5E |
| Limit access to assigned workNY-DW-LEAST-PRIVILEGE requirement 5-E.6(c)(2)(ii) | User access to OT and nonpublic information. Restrict privileges to those needed for the user's assigned tasks. Timing: By January 1, 2027 and when access is granted or changed. Source: NYDOH-APP5E |
| Separate OT and IT user accountsNY-DW-ACCOUNT-SEPARATION requirement 5-E.6(c)(2)(iii) | User accounts authorized for OT and IT. Separate accounts authorized to access OT from accounts authorized to access IT. Timing: By January 1, 2027 and during account administration. Source: NYDOH-APP5E |
| Give OT users unique credentialsNY-DW-UNIQUE-CREDENTIALS requirement 5-E.6(c)(2)(iv) | OT capable of supporting unique user credentials; compensating controls for incapable OT. Use unique credentials where supported. Implement compensating controls where not supported; above 50,000 combined population, the designated lead documents those controls in writing. Timing: By January 1, 2027 and when equipment or access changes. Source: NYDOH-APP5E |
| Review access at least annuallyNY-DW-ACCESS-REVIEW requirement 5-E.6(c)(2)(v) | All user access privileges within the covered program. Review privileges and remove or disable accounts and access no longer needed for the user's job. Timing: At least annually. Source: NYDOH-APP5E |
| Remove access immediately when it is no longer neededNY-DW-LEAVER-ACCESS requirement 5-E.6(c)(2)(v) | Departing users and users whose changed role no longer requires access. Immediately terminate unnecessary account access. Change shared credentials immediately or implement compensating controls that prevent the former user's unauthorized OT access. Timing: Immediately following the departure or relevant role change. Source: NYDOH-APP5E |
| Disable unnecessary remote accessNY-DW-REMOTE-NEED requirement 5-E.6(c)(2)(vi) | Remote access to covered OT. Disable remote access that is unnecessary for monitoring or operating the system. Timing: By January 1, 2027 and when need ends. Source: NYDOH-APP5E |
| Limit remote functionsNY-DW-REMOTE-FUNCTION requirement 5-E.6(c)(2)(vii) | Allowed remote access to covered OT. Limit remote functionality to what is necessary to monitor or operate the system. Timing: By January 1, 2027 and on configuration changes. Source: NYDOH-APP5E |
| Secure remote access protocolsNY-DW-REMOTE-CONFIG requirement 5-E.6(c)(2)(viii) | Protocols permitting remote access to OT or nonpublic information. Securely configure the protocols that permit remote access. Timing: By January 1, 2027 and throughout operation. Source: NYDOH-APP5E |
| Remove default OT passwordsNY-DW-DEFAULT-PASSWORDS requirement 5-E.6(c)(2)(ix) | All covered OT, including equipment with technically unchangeable passwords. Disallow default passwords. Where technology cannot change them, implement compensating controls. Timing: By January 1, 2027 and when equipment enters service. Source: NYDOH-APP5E |
| Maintain the cyber asset inventoryNY-DW-INVENTORY requirement 5-E.3(c); 5-E.6(c)(3) | OT reachable by management, control or communications protocols and IT physically or logically connected to OT. Maintain an inventory covering the defined cyber assets. Timing: By January 1, 2027 and maintained thereafter. Source: NYDOH-APP5E |
| Protect OT and nonpublic informationNY-DW-DEFENSIVE-ARCHITECTURE requirement 5-E.6(c)(4) | Covered OT and nonpublic information. Use defensive architecture, controls, compensating controls, policies and procedures against unauthorized disclosure, alteration or destruction. Timing: By January 1, 2027 and maintained thereafter. Source: NYDOH-APP5E |
| Assess internal and external threatsNY-DW-ONGOING-RISK requirement 5-E.6(c)(5) | OT and nonpublic information relevant to Subpart compliance. Identify and assess internal and external cybersecurity risks that may threaten the system's ability to comply. Timing: By January 1, 2027 and as risks change. Source: NYDOH-APP5E |
| Monitor and retain useful network logsNY-DW-LOGGING requirement 5-E.6(c)(6) | Covered systems above 50,000 combined wholesale and retail population. Apply the specific outward only device exception and relevant 5-E.2 exclusion using evidence. Monitor and log network activity and be prepared to produce the logs for examination after a cyber incident. Timing: By January 1, 2027 and maintained thereafter. Source: NYDOH-APP5E |
| Respond with operations and safety in viewNY-DW-RESPONSE requirement 5-E.6(c)(7) | Cybersecurity incidents affecting the covered system. Respond to reduce disruption, address compliance impacts and limit physical or structural damage. Timing: When responding to a cyber incident; prepare capability by January 1, 2027. Source: NYDOH-APP5E |
| Restore safe operations and servicesNY-DW-RECOVERY requirement 5-E.6(c)(8) | Covered system recovery following cyber incidents. Recover from cybersecurity incidents and restore normal operations and services. Timing: Prepare capability by January 1, 2027 and use it when needed. Source: NYDOH-APP5E |
| Complete approved operator cyber trainingNY-DW-TRAINING requirement 5-E.1(a) and (b); 5-E.7 | All drinking water operators certified under Subpart 5-4, independent of system population or isolation. Complete at least one hour of cybersecurity training using a curriculum approved by NYSDOH every three years. Timing: Already effective upon adoption; confirm each operator's applicable training period. Source: NYDOH-APP5E |
| Write the cyber incident response planNY-DW-IRP requirement 5-E.8; 5-E.2(a) | All covered water systems, including systems using the no connection exclusion. Establish a written plan describing tasks during and after a cyber incident to maintain or restore Subpart compliance, consistent with 5-1.33(b)(6). Timing: By January 1, 2027 and kept current. Source: NYDOH-APP5E |
| Notify DOH of a qualifying cyber incidentNY-DW-INCIDENT-NOTICE requirement 5-E.3(e); 5-E.9 | A defined cybersecurity incident that has created or may create a public health hazard, including at otherwise excluded covered systems. Notify NYSDOH using the prescribed 5-1.77(a) process. Preserve separate State and federal notification obligations. Timing: As soon as possible, no later than 24 hours after determining that the qualifying incident occurred. Already effective upon adoption. Source: NYDOH-APP5E |
| Consult after a State deficiency noticeNY-DW-DEFICIENCY-CONSULT requirement 5-1.71(c); Appendix 5-E.1(d) | State notification that a significant deficiency exists; section 5-1.71 also has broader public water system application. Consult with the State regarding corrective action after receiving its significant deficiency notice. Timing: Within 30 days of the State notification. Source: NYDOH-SUBPART51 |
| Correct the deficiency or comply with its action planNY-DW-DEFICIENCY-CORRECT requirement 5-1.71(c) and (d); Appendix 5-E.1(d) | State notified significant deficiency and any applicable public health hazard. Correct the deficiency or comply with a corrective action plan specifying needed changes. Public health hazards require State directed or approved action and Tier 1 notification; failure to correct or begin correction as required can be a treatment technique violation. Timing: Within 120 days of the State notice, or earlier when the State requires action to protect public health. Follow the actual State direction and plan. Source: NYDOH-SUBPART51 |
| Keep State emergency plan submissions currentNY-DW-ERP-RECURRENCE requirement 5-1.33(e) | Community water systems supplying more than 3,300 people; other systems may be directed to prepare a plan under 5-1.33(f). Keep the emergency plan current, submit it for State review and supply updated communication and notification information. Timing: Plan review submission at least every five years and within 30 days after major infrastructure changes have been made; contact information to the State by December 31 each year. Source: NYDOH-SUBPART51 |
| Handle plan comment and protected information correctlyNY-DW-ERP-PUBLIC-REVIEW requirement 5-1.33(d) and (h); Appendix 5-E.10 | Required emergency plan public review and submitted information. Before final plan submission, publish the required local notice in two successive weeks and accept comments for at least 14 days after first publication. Submit comments with the plan. Determine and handle security risk information under the applicable disclosure provisions. Timing: Before final emergency plan submission. Source: NYDOH-SUBPART51 |
| Record and criterion | Duty and timing |
|---|---|
| Separate permit reporting from POTW controlsNY-WW-SCOPE requirement 750-1.2(a)(27), (78), (94); 750-2.7(h); 750-2.9(d) through (f) | All SPDES permittees for reporting; POTWs for the additional plans and controls. Identify the permittee, permit, POTW status, design flow and systems holding SPDES program data before selecting obligations. Timing: Before planning and when permit or ownership facts change. Source: NYDEC-750-2026 |
| Report a wastewater cyber incident promptlyNY-WW-NOTIFY-ORAL requirement 750-1.2(a)(27); 750-2.7(h)(1) | All SPDES permittees when a defined cybersecurity incident occurs. Report orally to the regional water engineer. Current DEC instructions also require the initial online incident form followed immediately by oral notification; use the regional contact or DEC Dispatch if the regional contact cannot be reached. Timing: As soon as possible, no later than 24 hours from permittee awareness. Effective March 26, 2026. Source: NYDEC-750-2026 |
| Complete the written wastewater incident reportNY-WW-NOTIFY-WRITTEN requirement 750-2.7(h)(2) | All SPDES permittees after a defined cybersecurity incident. Provide the written report with discovery time and person, incident description, affected IT or OT, actual or expected disruption and duration, data or physical loss and remediation or mitigation measures. Use DEC's current online process. Timing: Within 30 days from permittee awareness of the incident. Source: NYDEC-750-2026 |
| Keep other incident notices openNY-WW-PARALLEL-NOTICES requirement 750-2.7(h)(3) | Other reporting and notification duties applicable under 750-2.7 and the permit. Complete other applicable reporting duties alongside the cyber incident reports. Review permit conditions and separate sewage, spill and municipal cyber reporting duties with the responsible specialist. Timing: Each applicable authority's own trigger and deadline. Source: NYDEC-750-2026 |
| Establish the wastewater emergency planNY-WW-ERP requirement 750-2.9(d)(1) | All POTWs. Establish, maintain and implement a written ERP. A plan existing before March 11, 2027 may qualify if it covers preparation and response strategies, resources and procedures plus responsible titles and contacts. Otherwise use the incorporated EPA template. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Update changed emergency contactsNY-WW-ERP-CONTACT requirement 750-2.9(d)(2) | Titles and contact information in the POTW emergency plan. Update the emergency plan after its responsible titles or contact details change. Timing: Within 30 days of the change. Source: NYDEC-750-2026 |
| Keep secure printed plans on and off siteNY-WW-ERP-COPIES requirement 750-2.9(d)(3) | POTW emergency plan including its incorporated cyber plan. Keep printed ERP copies in secure locations on and off the premises, accessible only to appropriate people under the access rules. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Certify the ERP requirements annuallyNY-WW-ERP-CERT requirement 750-2.9(d)(4); 750-2.9(f) | All POTWs. Certify compliance with ERP establishment, contact updating and printed copy requirements using the required authorized signer and filing process. Timing: By March 28 each year; first certification March 28, 2027. Source: NYDEC-750-2026 |
| Write and apply least privilege access rulesNY-WW-ACCESS requirement 750-2.9(e)(1)(i)(a) | OT, SPDES program data, IT permitting direct or indirect access to either, and the ERP. Establish, maintain and implement written access rules or procedures consistent with least privilege. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Set and implement password rulesNY-WW-PASSWORDS requirement 750-2.9(e)(1)(i)(b) | Authentication within the required access rules. Address password security, complexity and management using the incorporated documents. Record the selected method and any technical constraints rather than inventing one universal password rule. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Require MFA for allowed remote OT accessNY-WW-MFA requirement 750-2.9(e)(1)(i)(c) | Remote access to OT allowed under the POTW's access rules. Require multifactor authentication for permitted remote OT access. Do not import the drinking water rule's written compensating control exception into this wastewater criterion. Timing: By March 11, 2027 and for every allowed remote route. Source: NYDEC-750-2026 |
| Disallow preset and default credentialsNY-WW-DEFAULTS requirement 750-2.9(e)(1)(i)(d) | Assets covered by the POTW's access and authentication rules. Disallow preset or default credentials. Resolve incapable legacy equipment with the responsible authority rather than assuming a drinking water exception applies. Timing: By March 11, 2027 and on commissioning or reset. Source: NYDEC-750-2026 |
| Review access rules annuallyNY-WW-ACCESS-REVIEW requirement 750-2.9(e)(1)(i)(e) | Written access control and authentication rules or procedures. Review the access rules and procedures at least annually. Timing: At least annually by March 28, beginning in 2027. Source: NYDEC-750-2026 |
| Update access rules after an incident or assessmentNY-WW-ACCESS-UPDATE requirement 750-2.9(e)(1)(i)(f) | Written access control and authentication rules or procedures. Update the rules after a cyber incident or a cybersecurity assessment or audit. Timing: Within 90 days after the triggering incident, assessment or audit. Source: NYDEC-750-2026 |
| Include the full cyber asset inventoryNY-WW-INVENTORY requirement 750-1.2(a)(25); 750-2.9(e)(1)(ii)(a) | Reachable OT and IT connected to OT or serving as the system of record for SPDES program data. Include the defined cyber asset inventory in a written vulnerability management process. Relevant assets without IP addresses are not automatically excluded. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Identify remotely accessible assetsNY-WW-REMOTE-INVENTORY requirement 750-2.9(e)(1)(ii)(b) | Assets in the cyber asset inventory. Identify which inventoried assets can be accessed remotely. Timing: By March 11, 2027 and as access changes. Source: NYDEC-750-2026 |
| Identify known asset vulnerabilitiesNY-WW-VULNERABILITIES requirement 750-2.9(e)(1)(ii)(c) | Assets within the cyber asset inventory. Identify known cybersecurity vulnerabilities in inventoried assets. Timing: By March 11, 2027 and as vulnerability information changes. Source: NYDEC-750-2026 |
| Assess likelihood and operating consequencesNY-WW-RISK requirement 750-2.9(e)(1)(ii)(d) | Known vulnerabilities identified for inventoried assets. Assess the likelihood of exploitation and consequences for the POTW's normal operations. Timing: During vulnerability assessment and review. Source: NYDEC-750-2026 |
| Prioritize vulnerabilities by assessed riskNY-WW-PRIORITY requirement 750-2.9(e)(1)(ii)(e) | Known vulnerabilities with assessed risks. Prioritize vulnerabilities using the assessed risks. Timing: During vulnerability management. Source: NYDEC-750-2026 |
| Mitigate or remediate in risk orderNY-WW-REMEDIATE requirement 750-2.9(e)(1)(ii)(f) | Prioritized vulnerabilities. Mitigate or remediate vulnerabilities according to the established priority. Timing: As part of the implemented vulnerability process; use actual risk and authorized operational schedules. Source: NYDEC-750-2026 |
| Review the vulnerability process annuallyNY-WW-VULN-REVIEW requirement 750-2.9(e)(1)(ii)(g) | Written cybersecurity vulnerability management process. Review the written process at least annually. Timing: At least annually by March 28, beginning in 2027. Source: NYDEC-750-2026 |
| Update the process when assets or vulnerabilities changeNY-WW-VULN-UPDATE requirement 750-2.9(e)(1)(ii)(h) | Written vulnerability management process and cyber asset inventory. Update when inventoried assets are added or decommissioned, or a new vulnerability is identified for an inventoried asset. Timing: When the specified change occurs; the clause does not give a universal 90 day allowance. Source: NYDEC-750-2026 |
| Document and protect the network structureNY-WW-NETWORK requirement 750-2.9(e)(1)(iii) | POTW operational technology and its IT or external connections. Maintain and implement a written network description that protects OT through physical and logical separation or appropriate controls securing necessary connections. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Monitor and log the required network activityNY-WW-LOGGING requirement 750-2.9(e)(2) | POTWs with design flow at least 10 MGD unless the specific no connection or outward only device exception is supported. Implement, manage and maintain monitoring and logging. Verify any claimed exception using the actual connection design and device capability; the exception does not remove other POTW duties. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Incorporate the cyber response plan into the ERPNY-WW-IRP requirement 750-2.9(e)(3) | All POTWs. Establish, maintain and implement a cyber IRP and incorporate it into the ERP. A qualifying plan existing before March 11, 2027 may be used; otherwise use one of the two incorporated EPA cyber response templates. Timing: By March 11, 2027 and maintained thereafter. Source: NYDEC-750-2026 |
| Use the incorporated document editionsNY-WW-IBR requirement 750-1.25(j) through (o); 750-2.9(e)(1) and (4) | Establishing, maintaining and implementing the specified wastewater controls and plan options. Use the six incorporated documents as directed by the adopted clauses. Record the specified edition and relevant method. Separate additional guidance from these required references; not every recommendation in a document becomes a standalone universal legal rule. Timing: When developing and maintaining the required controls. Source: NYDEC-750-2026 |
| Certify the cybersecurity controls annuallyNY-WW-CYBER-CERT requirement 750-2.9(e)(5); 750-2.9(f) | Municipalities responsible for POTWs. Certify compliance with the controls, applicable logging and incorporated cyber response plan under 750-2.9(e)(1) through (3). Keep this distinct from the ERP certification. Timing: By March 28 each year; first certification March 28, 2027. Source: NYDEC-750-2026 |
| Use the authorized municipal signer and filing processNY-WW-CERT-AUTHORITY requirement 750-2.9(f)(1) through (3) | Required POTW ERP and cybersecurity certifications. Use DEC supplied or approved forms and the required certification. The signer is the principal executive officer, ranking elected official or a qualifying executive level municipal official authorized in writing. Submit that delegation to DEC. Timing: Before each certification submission. Source: NYDEC-750-2026 |
| Complete cybersecurity hours for operator renewalNY-WW-TRAINING requirement 650.8; 650.12(c)(2) | New York certified wastewater operators with certifications expiring on or after January 1, 2027. Complete approved cybersecurity training within the existing five year renewal hours: two hours for Grades 1, 1A, 2 and 2A; four hours for Grades 3, 3A, 4 and 4A. Confirm course approval and the individual renewal period. Timing: Within the operator's applicable five year renewal period before renewal; the January date is an expiration threshold. Source: NYDEC-650-2026 |
| Rehearse the response without affecting operationsNY-WW-EXERCISE guidance Cybersecurity Incident Response Plans, exercise question | POTW staff and response partners selected by the operating authority. Use a clearly labeled discussion exercise to rehearse decisions, communications and recovery. DEC recommends regular exercises, preferably annually; this is not stated here as an additional annual filing or certification requirement. Timing: Choose and record a practical exercise schedule. Source: NYDEC-IMPLEMENTATION |
| Record and criterion | Duty and timing |
|---|---|
| Complete the federal risk and resilience assessmentUS-DW-RRA requirement SDWA 1433(a); RRA requirements | Community drinking water systems serving more than 3,300 people. Assess malevolent acts and natural hazards, physical and automated systems including security, monitoring, financial infrastructure, chemicals, operations and maintenance. A cyber worksheet supports this broader assessment but does not replace it. Timing: Use the applicable population cohort and five year review cycle; the small system cycle RRA date was June 30, 2026. Source: USEPA-AWIA |
| Prepare the federal emergency plan from the assessmentUS-DW-ERP requirement SDWA 1433(b); ERP requirements | Community drinking water systems serving more than 3,300 people. Prepare or revise the ERP using RRA findings, with resilience strategies, response procedures and equipment, impact reduction measures and detection strategies. Coordinate with local emergency planning committees to the extent possible. Timing: No later than six months after actual RRA certification. December 31, 2026 is the latest listed small system date only when RRA certification occurred on June 30, 2026. Source: USEPA-AWIA |
| Submit the federal certifications by PWSIDUS-DW-CERTIFICATION requirement Electronic submission and certification statements | Each covered community water system's PWSID. Submit the appropriate signed RRA and ERP certification statements using an accepted EPA method. Keep the actual RRA and ERP at the system rather than submitting those sensitive documents with the certification. Timing: At the applicable RRA and ERP deadlines. Source: USEPA-AWIA-FILING |
| Retain the federal assessment and plan securelyUS-DW-RETENTION requirement ERP requirements; five year review requirements | RRA and ERP for each covered community water system. Keep a copy of the RRA and ERP for five years after certification and maintain the required review and revision cycle. Timing: At least five years after the relevant certification. Source: USEPA-AWIA |
The source register distinguishes adopted rules, agency guidance and the specific editions incorporated by New York. A newer document on an agency website does not silently replace an incorporated edition. Requirements are paraphrased; the examination and acceptance methods are GDF planning guidance.
NYSDOH Appendix 5-E: Cybersecurity Requirements for Public Water Systems
Sections 5-E.1 through 5-E.11
Adopted regulation
NYSDOH Subpart 5-1: Public Water Systems
Sections 5-1.33, 5-1.71 and 5-1.77; agency compilation revised October 8, 2026
Agency hosted regulation compilation
NYSDEC adopted revised Part 750 express terms
750-1.2(a), 750-1.25(j) through (o), 750-2.7(h), 750-2.9(d) through (f)
Adopted regulation; adoption published March 11, 2026
NYSDEC adopted Part 650 express terms
650.8 and 650.12
Adopted regulation; training details also checked against agency implementation guidance
NYSDEC adopted Part 616 express terms
616.7(c)(2)(viii)
Adopted regulation
NYSDEC adopted wastewater cybersecurity amendments
Notice of Adoption and rule making documents
Official adoption record
NYSDEC Wastewater Cybersecurity Resources
Effective dates, applicability, reporting, plans, training and annual certification questions
Agency implementation guidance; adopted text controls legal criteria
NYSDEC Wastewater Cybersecurity Regulations: Compendium of Resources
Pages 2 through 24 and regulatory appendices
Agency guidance mapping incorporated documents to adopted requirements
EPA Guidance on Improving Cybersecurity at Drinking Water and Wastewater Systems
EPA 817-B-23-001, August 2024; incorporated by 750-1.25(j)
Specified edition incorporated into NY wastewater regulation
EPA Wastewater Utility Emergency Response Plan: Template and Instructions
EPA 817-B-21-003, July 2021; incorporated by 750-1.25(k)
Specified edition incorporated into NY wastewater regulation; archived EPA edition. The older 2021 download URL now serves an October 2025 document and is not used as the edition reference.
EPA Incident Action Checklist: Cybersecurity
EPA 810-B-17-004, February 2021; incorporated by 750-1.25(l)
Specified edition incorporated into NY wastewater regulation; older URL filename is retained by EPA
NIST Guide to Operational Technology Security
NIST SP 800-82r3, September 2023; incorporated by 750-1.25(m)
Specified edition incorporated into NY wastewater regulation
NIST Security and Privacy Controls for Information Systems and Organizations
NIST SP 800-53, December 10, 2020; incorporated by 750-1.25(n)
Specified edition incorporated into NY wastewater regulation; do not silently substitute later releases
EPA Drinking Water and Wastewater Systems Cybersecurity Incident Response Plan Template Instructions
EPA 810-F-25-017, April 2025; incorporated by 750-1.25(o)
Specified edition incorporated into NY wastewater regulation; publication edition is April 2025 despite URL date
EPA AWIA Section 2013 / SDWA Section 1433
Risk assessment, emergency plan, certification deadlines and five year reviews
Federal agency explanation of statutory duties
EPA How to Certify Your Risk and Resilience Assessment or Emergency Response Plan
Certification statements, PWSID, filing methods and document retention
Federal agency filing instructions
Use the local audit planner to organize preparation, or return to the four sector New York resource library. The shared GDF kit carries the same complete November 18 edition on both sites.
On the free initial consultation, we review your system type, deadlines and available evidence, then discuss the technical scope and next steps. Bring the questions that need decisions. Keep plant records in your controlled repository.
Reviewed by Joseph Caruso, Founder, CEO and CTO, CISSP. Last reviewed .