{
  "edition": "2026-11-18",
  "verifiedOn": "2026-11-18",
  "title": "New York Water Cybersecurity Toolkit",
  "scope": "Cybersecurity planning for New York drinking water and wastewater systems. The federal track covers the related community water risk assessment and emergency planning duties. Permit conditions, enforcement orders and other applicable laws require separate review.",
  "interpretation": "Requirement text paraphrases the cited authority. Evidence requests, examination steps and acceptance descriptions are GDF planning methods, not regulator approval. Unknown scope or unexamined evidence stays unresolved. A completed worksheet does not certify compliance.",
  "sources": [
    {
      "id": "NYDOH-APP5E",
      "title": "NYSDOH Appendix 5-E: Cybersecurity Requirements for Public Water Systems",
      "url": "https://healthweb-back.health.ny.gov/regulations/nycrr/title_10/part_5/docs/appendix_5e.pdf",
      "locator": "Sections 5-E.1 through 5-E.11",
      "status": "Adopted regulation",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDOH-SUBPART51",
      "title": "NYSDOH Subpart 5-1: Public Water Systems",
      "url": "https://healthweb-back.health.ny.gov/regulations/nycrr/title_10/part_5/docs/subpart_5-1.pdf",
      "locator": "Sections 5-1.33, 5-1.71 and 5-1.77; agency compilation revised October 8, 2026",
      "status": "Agency hosted regulation compilation",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDEC-750-2026",
      "title": "NYSDEC adopted revised Part 750 express terms",
      "url": "https://dec.ny.gov/sites/default/files/2026-03/6nycrr_part750_et_rev.pdf",
      "locator": "750-1.2(a), 750-1.25(j) through (o), 750-2.7(h), 750-2.9(d) through (f)",
      "status": "Adopted regulation; adoption published March 11, 2026",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDEC-650-2026",
      "title": "NYSDEC adopted Part 650 express terms",
      "url": "https://dec.ny.gov/sites/default/files/2026-03/6nycrr_part650_et.pdf",
      "locator": "650.8 and 650.12",
      "status": "Adopted regulation; training details also checked against agency implementation guidance",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDEC-616-2026",
      "title": "NYSDEC adopted Part 616 express terms",
      "url": "https://dec.ny.gov/sites/default/files/2026-03/6nycrr_part616_et.pdf",
      "locator": "616.7(c)(2)(viii)",
      "status": "Adopted regulation",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDEC-ADOPTION-2026",
      "title": "NYSDEC adopted wastewater cybersecurity amendments",
      "url": "https://dec.ny.gov/regulatory/regulations/proposed-emergency-recently-adopted-regulations/water-revisions/adopted-amendments-to-6-nycrr-parts-616-650-750",
      "locator": "Notice of Adoption and rule making documents",
      "status": "Official adoption record",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDEC-IMPLEMENTATION",
      "title": "NYSDEC Wastewater Cybersecurity Resources",
      "url": "https://dec.ny.gov/environmental-protection/water/water-quality/wastewater-treatment-resources/wastewater-cybersecurity-resources",
      "locator": "Effective dates, applicability, reporting, plans, training and annual certification questions",
      "status": "Agency implementation guidance; adopted text controls legal criteria",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "NYDEC-COMPENDIUM",
      "title": "NYSDEC Wastewater Cybersecurity Regulations: Compendium of Resources",
      "url": "https://dec.ny.gov/sites/default/files/2026-03/wastewatercyber_compendium.pdf",
      "locator": "Pages 2 through 24 and regulatory appendices",
      "status": "Agency guidance mapping incorporated documents to adopted requirements",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "IBR-EPA-CYBER-2024",
      "title": "EPA Guidance on Improving Cybersecurity at Drinking Water and Wastewater Systems",
      "url": "https://www.epa.gov/system/files/documents/2024-08/epa-guidance-on-improving-cybersecurity-at-drinking-water-and-wastewater-systems-1.pdf",
      "locator": "EPA 817-B-23-001, August 2024; incorporated by 750-1.25(j)",
      "status": "Specified edition incorporated into NY wastewater regulation",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "IBR-EPA-WWERP-2021",
      "title": "EPA Wastewater Utility Emergency Response Plan: Template and Instructions",
      "url": "https://nepis.epa.gov/Exe/ZyPURL.cgi?Dockey=P1012S6R.txt",
      "locator": "EPA 817-B-21-003, July 2021; incorporated by 750-1.25(k)",
      "status": "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.",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "IBR-EPA-INCIDENT-2021",
      "title": "EPA Incident Action Checklist: Cybersecurity",
      "url": "https://www.epa.gov/sites/default/files/2017-11/documents/171013-incidentactionchecklist-cybersecurity_form_508c.pdf",
      "locator": "EPA 810-B-17-004, February 2021; incorporated by 750-1.25(l)",
      "status": "Specified edition incorporated into NY wastewater regulation; older URL filename is retained by EPA",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "IBR-NIST-80082R3",
      "title": "NIST Guide to Operational Technology Security",
      "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final",
      "locator": "NIST SP 800-82r3, September 2023; incorporated by 750-1.25(m)",
      "status": "Specified edition incorporated into NY wastewater regulation",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "IBR-NIST-80053R5",
      "title": "NIST Security and Privacy Controls for Information Systems and Organizations",
      "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final",
      "locator": "NIST SP 800-53, December 10, 2020; incorporated by 750-1.25(n)",
      "status": "Specified edition incorporated into NY wastewater regulation; do not silently substitute later releases",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "IBR-EPA-CIRP-2025",
      "title": "EPA Drinking Water and Wastewater Systems Cybersecurity Incident Response Plan Template Instructions",
      "url": "https://www.epa.gov/system/files/documents/2025-10/250414_cybersecurity-incident-response-plan-template-instructions_508c_0.pdf",
      "locator": "EPA 810-F-25-017, April 2025; incorporated by 750-1.25(o)",
      "status": "Specified edition incorporated into NY wastewater regulation; publication edition is April 2025 despite URL date",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "USEPA-AWIA",
      "title": "EPA AWIA Section 2013 / SDWA Section 1433",
      "url": "https://www.epa.gov/waterresilience/awia-section-2013",
      "locator": "Risk assessment, emergency plan, certification deadlines and five year reviews",
      "status": "Federal agency explanation of statutory duties",
      "verifiedOn": "2026-11-18"
    },
    {
      "id": "USEPA-AWIA-FILING",
      "title": "EPA How to Certify Your Risk and Resilience Assessment or Emergency Response Plan",
      "url": "https://www.epa.gov/waterresilience/how-certify-your-risk-and-resilience-assessment-or-emergency-response-plan",
      "locator": "Certification statements, PWSID, filing methods and document retention",
      "status": "Federal agency filing instructions",
      "verifiedOn": "2026-11-18"
    }
  ],
  "scopeRules": [
    {
      "id": "dw-covered",
      "track": "drinking-water",
      "title": "Community water cybersecurity controls",
      "basis": "Community water system serving more than 3,300 people. Evaluate Appendix 5-E.2 exclusions against documented physical and logical connections. Municipal ownership alone is not an exclusion.",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(a), 5-E.2"
    },
    {
      "id": "dw-large",
      "track": "drinking-water",
      "title": "Additional duties above 50,000 people",
      "basis": "Covered community water system with combined wholesale and retail population greater than 50,000. Do not substitute service connections or customer accounts for population.",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(a), 5-E.4, 5-E.5(b), 5-E.6(b), 5-E.6(c)(2)(iv), 5-E.6(c)(6)"
    },
    {
      "id": "dw-all-covered",
      "track": "drinking-water",
      "title": "Covered water systems including isolated systems",
      "basis": "Written incident response planning and qualifying incident reporting continue for covered systems using the no connection exclusion. Operator training also remains applicable under its own scope.",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(a), 5-E.2(a), 5-E.8, 5-E.9"
    },
    {
      "id": "dw-all-operators",
      "track": "drinking-water",
      "title": "Certified drinking water operators",
      "basis": "All drinking water operators certified under Subpart 5-4. Population and Appendix 5-E.2 exclusions do not remove this training duty.",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(a), 5-E.7"
    },
    {
      "id": "ww-all-spdes",
      "track": "wastewater",
      "title": "All SPDES permittees",
      "basis": "Cyber incident reporting applies to all SPDES permittees, including private facilities. Apply the defined incident criteria rather than assuming every security alert is a reportable incident.",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.2(a)(27), 750-2.7(h)"
    },
    {
      "id": "ww-potw",
      "track": "wastewater",
      "title": "Publicly owned treatment works",
      "basis": "ERP and cybersecurity controls apply to POTWs of all sizes. Contracting operations does not transfer the municipality's responsibility for compliance.",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.2(a)(78), 750-2.9(d) through (f)"
    },
    {
      "id": "ww-large",
      "track": "wastewater",
      "title": "Network monitoring at larger POTWs",
      "basis": "Design flow at least 10 million gallons per day. The specific no connection and outward only device exceptions concern monitoring and logging, not the other POTW controls.",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(2)"
    },
    {
      "id": "ww-operators",
      "track": "wastewater",
      "title": "Certified wastewater operators",
      "basis": "Part 650 training requirements apply by operator grade and certification renewal period. January 1, 2027 is the expiration date threshold, not a universal course completion date for every operator.",
      "sourceId": "NYDEC-650-2026",
      "section": "650.8, 650.12"
    },
    {
      "id": "federal-cws",
      "track": "federal",
      "title": "Federal community water assessment and planning",
      "basis": "Community drinking water systems serving more than 3,300 people, separately identified by PWSID. Wastewater systems do not become subject to these federal certification duties merely by using the toolkit.",
      "sourceId": "USEPA-AWIA",
      "section": "SDWA 1433"
    }
  ],
  "requirements": [
    {
      "id": "NY-DW-SCOPE",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Record the water system scope",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(a); 5-E.2",
      "scope": "Community water systems serving more than 3,300 people; separate operator training scope.",
      "duty": "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.",
      "owner": "System owner with the responsible technical reviewer",
      "evidence": "PWSID, population basis, network diagram, connection inventory and signed scope decision.",
      "test": "Compare drawings with approved configuration records and interview the operator about vendor and remote paths.",
      "acceptance": "Each selected or excluded duty has a supported scope decision; unknown connections remain unresolved.",
      "recurrence": "On material scope or connection changes; review with the CVA."
    },
    {
      "id": "NY-DW-PERSONNEL",
      "track": "drinking-water",
      "scopeKey": "dw-large",
      "kind": "requirement",
      "title": "Designate a qualified cybersecurity lead",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.4(a)",
      "scope": "Covered systems serving a combined wholesale and retail population greater than 50,000, subject to applicable exclusions.",
      "duty": "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.",
      "owner": "System owner",
      "evidence": "Designation, qualification basis, duties and current contact details.",
      "test": "Read the designation and compare documented experience with responsibility for the system's program.",
      "acceptance": "An owner designated, qualified individual is responsible for the program.",
      "recurrence": "On role or personnel changes."
    },
    {
      "id": "NY-DW-LEAD-CONTACT",
      "track": "drinking-water",
      "scopeKey": "dw-large",
      "kind": "requirement",
      "title": "Put the cybersecurity lead in the emergency plan",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.4(a)(1)",
      "scope": "Covered systems with combined wholesale and retail population greater than 50,000, subject to applicable exclusions.",
      "duty": "Include the designated individual's name and contact information in the water supply emergency plan.",
      "timing": "By January 1, 2027; keep current.",
      "owner": "Emergency plan owner",
      "evidence": "Current controlled emergency plan and contact verification record.",
      "test": "Compare the designation with the plan and verify contact details without making an emergency report.",
      "acceptance": "The current designated individual can be identified and reached from the plan.",
      "recurrence": "On personnel or contact changes."
    },
    {
      "id": "NY-DW-BOARD-REPORT",
      "track": "drinking-water",
      "scopeKey": "dw-large",
      "kind": "requirement",
      "title": "Report program risks to the governing body",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.4(a)(2)",
      "scope": "Covered systems with combined wholesale and retail population greater than 50,000, subject to applicable exclusions.",
      "duty": "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.",
      "owner": "Designated cybersecurity lead",
      "evidence": "Dated report, controlled distribution record and governing body receipt.",
      "test": "Confirm the report covers the program and material risks and was delivered to the correct governing body.",
      "acceptance": "A timely confidential report has a documented recipient and evidence supported conclusions.",
      "recurrence": "At least annually."
    },
    {
      "id": "NY-DW-CVA-PLAN",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Complete the CVA and carry findings into the plan",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(c)(1); 5-E.5(a)",
      "scope": "Covered water systems subject to the CVA provisions.",
      "duty": "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.",
      "owner": "Authorized system representative and assessment lead",
      "evidence": "CVA edition, emergency plan cross references and State submission receipt.",
      "test": "Trace selected material findings from the CVA into the submitted emergency plan.",
      "acceptance": "The CVA exists, was submitted, and its findings inform the emergency plan.",
      "recurrence": "With updated CVA findings and plan submissions."
    },
    {
      "id": "NY-DW-CVA-APPROVAL",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Obtain the correct CVA approval",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.5(b)",
      "scope": "Covered water systems subject to CVA provisions.",
      "duty": "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.",
      "owner": "Authorized representative or designated cybersecurity lead",
      "evidence": "Approval date, approver identity, authority and CVA version.",
      "test": "Compare the recorded population and designation with the CVA approval record.",
      "acceptance": "The correct authorized person approved the identifiable CVA edition.",
      "recurrence": "Each CVA approval."
    },
    {
      "id": "NY-DW-CVA-RISK",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Assess risk to operations and protected information",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.5(c)",
      "scope": "Relevant IT, OT and nonpublic information that may affect Subpart compliance.",
      "duty": "Assess known vulnerabilities using likelihood of exploitation and consequences for normal operations.",
      "timing": "By January 1, 2027 and during CVA review.",
      "owner": "Assessment lead with plant operations",
      "evidence": "Asset and information scope, vulnerability register, likelihood and operational consequence rationale.",
      "test": "Trace representative treatment and support dependencies into the risk analysis using records and interviews.",
      "acceptance": "Relevant vulnerabilities have supported likelihood and consequence assessments; missing evidence is visible.",
      "recurrence": "During CVA review and material changes."
    },
    {
      "id": "NY-DW-CVA-CONTROLS",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Evaluate controls across the water system",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.5(d)",
      "scope": "Controls associated with supply, treatment, disinfection, pipes and valves, storage and operations management.",
      "duty": "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.",
      "owner": "Assessment lead and operations owner",
      "evidence": "Control tests, sample basis, observed results and unexamined dependencies.",
      "test": "Review approved records and safe demonstrations; agree operational limits before any live test.",
      "acceptance": "The analysis evaluates effectiveness across relevant functions rather than only listing policies.",
      "recurrence": "During CVA review."
    },
    {
      "id": "NY-DW-VULN-NOTICE",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Report qualifying CVA vulnerabilities",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(c)(2); 5-E.5(e)",
      "scope": "CVA vulnerabilities that may affect Subpart compliance, or a situation that may pose a public health risk.",
      "duty": "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.",
      "owner": "Authorized reporting lead with the operator",
      "evidence": "Identification time and timezone, criteria decision, submitted report and receipt.",
      "test": "Trace the recorded trigger to the reporting deadline and evidence of delivery.",
      "acceptance": "The qualifying trigger is preserved and the required report is timely; an ordinary security finding is not automatically assigned this clock.",
      "recurrence": "Each qualifying identification."
    },
    {
      "id": "NY-DW-CVA-REVIEW",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Keep the CVA current",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(c)(1); 5-E.5(f)",
      "scope": "Covered systems subject to CVA provisions.",
      "duty": "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.",
      "owner": "CVA owner and change manager",
      "evidence": "Review history, change commissioning dates, updated CVA and approval.",
      "test": "Compare the last review and major operational changes with recorded CVA updates.",
      "acceptance": "Both the annual and change driven deadlines are met and their results are documented.",
      "recurrence": "Annual and each qualifying infrastructure change."
    },
    {
      "id": "NY-DW-CVA-ACTIONS",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Identify action for each vulnerability",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.5(g)",
      "scope": "Vulnerabilities identified by the CVA.",
      "duty": "Identify the actions needed to mitigate or remediate the vulnerabilities.",
      "timing": "During completion and review of the CVA.",
      "owner": "CVA owner and assigned action owners",
      "evidence": "Finding IDs, proposed actions, operational dependencies and assigned responsibility.",
      "test": "Follow each identified vulnerability to a specified action or documented unresolved decision.",
      "acceptance": "The CVA states what action is needed for the identified vulnerabilities.",
      "recurrence": "When a vulnerability or its treatment changes."
    },
    {
      "id": "NY-DW-CVA-FORM",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Use the department approved CVA form",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.5(h)",
      "scope": "Covered systems subject to CVA provisions.",
      "duty": "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.",
      "owner": "CVA owner",
      "evidence": "Approved form version or written department approval and submitted CVA.",
      "test": "Compare the form used with the department's current approved submission instructions.",
      "acceptance": "The submission format has department approval.",
      "recurrence": "Each submission and form change."
    },
    {
      "id": "NY-DW-PROGRAM",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Build the program from the CVA findings",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(a)",
      "scope": "Covered systems subject to cybersecurity program provisions.",
      "duty": "Establish a cybersecurity program based on the findings of the system's CVA.",
      "timing": "By January 1, 2027 and maintained as risks change.",
      "owner": "System owner and program lead",
      "evidence": "Program edition, CVA mapping, procedures and allocated responsibilities.",
      "test": "Trace material CVA findings into program decisions and work assignments.",
      "acceptance": "The program addresses the system's actual CVA findings.",
      "recurrence": "When CVA findings or program design changes."
    },
    {
      "id": "NY-DW-PROGRAM-CERT",
      "track": "drinking-water",
      "scopeKey": "dw-large",
      "kind": "requirement",
      "title": "Certify the program through the required submission",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(b)",
      "scope": "Covered systems serving more than 50,000 combined wholesale and retail population, subject to applicable exclusions.",
      "duty": "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).",
      "owner": "Designated cybersecurity lead",
      "evidence": "Approved form, supported certification, signatory and submission receipt.",
      "test": "Trace certification statements to the program's supporting evidence and the correct signer.",
      "acceptance": "The required signed form accompanies the submission and does not claim unsupported compliance.",
      "recurrence": "With required emergency plan submissions."
    },
    {
      "id": "NY-DW-REPORTING-PROGRAM",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Maintain separate reporting duties",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(1); 5-E.9",
      "scope": "Applicable statutory and regulatory reporting obligations.",
      "duty": "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.",
      "owner": "Reporting lead and legal or compliance owner",
      "evidence": "Notification register with separate authority, trigger, recipient and receipt fields.",
      "test": "Walk through an exercise without transmitting and confirm that one notice does not close another authority's task.",
      "acceptance": "The program can identify and execute each applicable notice separately.",
      "recurrence": "On rule, contact or incident changes."
    },
    {
      "id": "NY-DW-MFA",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Protect external access to operational technology",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(i)",
      "scope": "Individuals accessing covered OT from an external network.",
      "duty": "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.",
      "owner": "Technical access owner and authorized approver",
      "evidence": "Remote route inventory, authentication configuration and written compensating control approvals.",
      "test": "Inspect configuration and an authorized demonstration; do not attempt unauthorized access or change plant operation.",
      "acceptance": "Every reviewed external route enforces MFA or has the specified written approval and implemented compensating controls.",
      "recurrence": "On access or control changes; include in CVA review."
    },
    {
      "id": "NY-DW-LEAST-PRIVILEGE",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Limit access to assigned work",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(ii)",
      "scope": "User access to OT and nonpublic information.",
      "duty": "Restrict privileges to those needed for the user's assigned tasks.",
      "timing": "By January 1, 2027 and when access is granted or changed.",
      "owner": "Access owner and user's manager",
      "evidence": "Role definitions, access approvals and effective permission records.",
      "test": "Compare sampled user permissions with documented duties and approvals.",
      "acceptance": "Sampled privileges match assigned work; unexplained access becomes a finding.",
      "recurrence": "On role changes and access reviews."
    },
    {
      "id": "NY-DW-ACCOUNT-SEPARATION",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Separate OT and IT user accounts",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(iii)",
      "scope": "User accounts authorized for OT and IT.",
      "duty": "Separate accounts authorized to access OT from accounts authorized to access IT.",
      "timing": "By January 1, 2027 and during account administration.",
      "owner": "Identity and access administrator",
      "evidence": "Account directories, role mappings and access architecture.",
      "test": "Compare approved account identities and authorizations across the OT and IT boundary.",
      "acceptance": "Separate accounts are used for the respective environments.",
      "recurrence": "On identity design and account changes."
    },
    {
      "id": "NY-DW-UNIQUE-CREDENTIALS",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Give OT users unique credentials",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(iv)",
      "scope": "OT capable of supporting unique user credentials; compensating controls for incapable OT.",
      "duty": "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.",
      "owner": "OT access owner and designated lead where applicable",
      "evidence": "Capability evidence, account inventory, compensating control records and required written documentation.",
      "test": "Inspect account settings and vendor capability documentation without exposing passwords.",
      "acceptance": "Unique accounts exist where supported and required compensating controls are implemented and documented.",
      "recurrence": "On equipment and user changes."
    },
    {
      "id": "NY-DW-ACCESS-REVIEW",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Review access at least annually",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(v)",
      "scope": "All user access privileges within the covered program.",
      "duty": "Review privileges and remove or disable accounts and access no longer needed for the user's job.",
      "timing": "At least annually.",
      "owner": "Access owner and managers",
      "evidence": "Complete account population, dated review, decisions and completed removals.",
      "test": "Compare the review population with active accounts and trace removal decisions to completion.",
      "acceptance": "The annual review covers the relevant population and unnecessary access is removed or disabled.",
      "recurrence": "At least annually."
    },
    {
      "id": "NY-DW-LEAVER-ACCESS",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Remove access immediately when it is no longer needed",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(v)",
      "scope": "Departing users and users whose changed role no longer requires access.",
      "duty": "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.",
      "owner": "Personnel notifier and access administrator",
      "evidence": "Event time, access removal records and shared credential control record.",
      "test": "Trace sampled departure and role changes to the effective removal of each access path.",
      "acceptance": "No unaddressed route remains solely because it uses shared credentials.",
      "recurrence": "Each departure or qualifying role change."
    },
    {
      "id": "NY-DW-REMOTE-NEED",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Disable unnecessary remote access",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(vi)",
      "scope": "Remote access to covered OT.",
      "duty": "Disable remote access that is unnecessary for monitoring or operating the system.",
      "timing": "By January 1, 2027 and when need ends.",
      "owner": "OT owner",
      "evidence": "Remote path inventory, operational justification and disabled access records.",
      "test": "Compare enabled paths with approved operational needs using configuration review.",
      "acceptance": "Each enabled path has a monitoring or operating need.",
      "recurrence": "On vendor, network and operational changes."
    },
    {
      "id": "NY-DW-REMOTE-FUNCTION",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Limit remote functions",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(vii)",
      "scope": "Allowed remote access to covered OT.",
      "duty": "Limit remote functionality to what is necessary to monitor or operate the system.",
      "timing": "By January 1, 2027 and on configuration changes.",
      "owner": "OT access owner",
      "evidence": "Remote role settings, approved functions and restrictions.",
      "test": "Inspect whether sampled remote accounts can perform functions beyond their documented need.",
      "acceptance": "Enabled remote functions match the necessary monitoring or operating work.",
      "recurrence": "On remote role and configuration changes."
    },
    {
      "id": "NY-DW-REMOTE-CONFIG",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Secure remote access protocols",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(viii)",
      "scope": "Protocols permitting remote access to OT or nonpublic information.",
      "duty": "Securely configure the protocols that permit remote access.",
      "timing": "By January 1, 2027 and throughout operation.",
      "owner": "Technical access owner",
      "evidence": "Protocol inventory, approved configuration basis and configuration records.",
      "test": "Compare approved settings with read only configuration evidence and record unexplained deviations.",
      "acceptance": "A supported security configuration is implemented for each reviewed protocol.",
      "recurrence": "On protocol, vendor or configuration changes."
    },
    {
      "id": "NY-DW-DEFAULT-PASSWORDS",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Remove default OT passwords",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(2)(ix)",
      "scope": "All covered OT, including equipment with technically unchangeable passwords.",
      "duty": "Disallow default passwords. Where technology cannot change them, implement compensating controls.",
      "timing": "By January 1, 2027 and when equipment enters service.",
      "owner": "OT equipment owner",
      "evidence": "Configuration attestation, vendor capability record and compensating control evidence.",
      "test": "Review records and authorized demonstrations without recording actual passwords.",
      "acceptance": "Defaults are removed or technically unavoidable defaults have implemented compensating controls.",
      "recurrence": "On installation, reset and equipment changes."
    },
    {
      "id": "NY-DW-INVENTORY",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Maintain the cyber asset inventory",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.3(c); 5-E.6(c)(3)",
      "scope": "OT reachable by management, control or communications protocols and IT physically or logically connected to OT.",
      "duty": "Maintain an inventory covering the defined cyber assets.",
      "timing": "By January 1, 2027 and maintained thereafter.",
      "owner": "OT asset owner with IT support",
      "evidence": "Asset inventory, system boundaries, owners and connection records.",
      "test": "Reconcile approved drawings, procurement and maintenance records with representative assets; no unsolicited scanning.",
      "acceptance": "The inventory covers the defined asset population, including relevant legacy and third party equipment.",
      "recurrence": "When assets or connections change."
    },
    {
      "id": "NY-DW-DEFENSIVE-ARCHITECTURE",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Protect OT and nonpublic information",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(4)",
      "scope": "Covered OT and nonpublic information.",
      "duty": "Use defensive architecture, controls, compensating controls, policies and procedures against unauthorized disclosure, alteration or destruction.",
      "timing": "By January 1, 2027 and maintained thereafter.",
      "owner": "Technical security owner and operations owner",
      "evidence": "Architecture, control design, approved rules and supporting effectiveness records.",
      "test": "Trace selected critical dependencies through documented boundaries and authorized control evidence.",
      "acceptance": "Protection measures address confidentiality, integrity and availability for the relevant assets and information.",
      "recurrence": "With architecture changes and CVA reviews."
    },
    {
      "id": "NY-DW-ONGOING-RISK",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Assess internal and external threats",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(5)",
      "scope": "OT and nonpublic information relevant to Subpart compliance.",
      "duty": "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.",
      "owner": "Program lead and operations owner",
      "evidence": "Risk register, threat inputs, dependencies and decisions.",
      "test": "Check whether vendor, insider, remote access and external exposure are considered where relevant.",
      "acceptance": "The program considers relevant internal and external risks, with unsupported areas left open.",
      "recurrence": "With new risks and CVA reviews."
    },
    {
      "id": "NY-DW-LOGGING",
      "track": "drinking-water",
      "scopeKey": "dw-large",
      "kind": "requirement",
      "title": "Monitor and retain useful network logs",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(6)",
      "scope": "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.",
      "duty": "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.",
      "owner": "Network monitoring owner",
      "evidence": "Logging scope, retained sample, access controls and any supported exception decision.",
      "test": "Inspect logs and retrieval capability through a safe demonstration; verify device capability before relying on an outward only exception.",
      "acceptance": "Required activity is monitored and logs are retrievable, or a supported specific exception is recorded.",
      "recurrence": "On network changes and program review."
    },
    {
      "id": "NY-DW-RESPONSE",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Respond with operations and safety in view",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(7)",
      "scope": "Cybersecurity incidents affecting the covered system.",
      "duty": "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.",
      "owner": "Incident lead and operating authority",
      "evidence": "Response procedures, operating decisions and incident or exercise records.",
      "test": "Use a discussion exercise to trace response authority and operational dependencies without changing live controls.",
      "acceptance": "Response decisions account for service, regulatory and physical consequences.",
      "recurrence": "After incidents and material plan changes."
    },
    {
      "id": "NY-DW-RECOVERY",
      "track": "drinking-water",
      "scopeKey": "dw-covered",
      "kind": "requirement",
      "title": "Restore safe operations and services",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.6(c)(8)",
      "scope": "Covered system recovery following cyber incidents.",
      "duty": "Recover from cybersecurity incidents and restore normal operations and services.",
      "timing": "Prepare capability by January 1, 2027 and use it when needed.",
      "owner": "Recovery lead and operating authority",
      "evidence": "Recovery dependencies, approved restoration steps and verification records.",
      "test": "Review an isolated restore demonstration or existing approved evidence; confirm the operator authorizes return to service.",
      "acceptance": "The recovery approach can restore needed services with verification of the operating state.",
      "recurrence": "With recovery changes and after incidents."
    },
    {
      "id": "NY-DW-TRAINING",
      "track": "drinking-water",
      "scopeKey": "dw-all-operators",
      "kind": "requirement",
      "title": "Complete approved operator cyber training",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(a) and (b); 5-E.7",
      "scope": "All drinking water operators certified under Subpart 5-4, independent of system population or isolation.",
      "duty": "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.",
      "owner": "Certified operator and training coordinator",
      "evidence": "Operator certification, approved course record, attendance and next training date.",
      "test": "Compare the course approval and completed hours with the operator's training period.",
      "acceptance": "The operator has the required approved cybersecurity training within the applicable three year period.",
      "recurrence": "Every three years."
    },
    {
      "id": "NY-DW-IRP",
      "track": "drinking-water",
      "scopeKey": "dw-all-covered",
      "kind": "requirement",
      "title": "Write the cyber incident response plan",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.8; 5-E.2(a)",
      "scope": "All covered water systems, including systems using the no connection exclusion.",
      "duty": "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.",
      "owner": "Emergency plan owner and operating authority",
      "evidence": "Controlled plan, notification roster, operating tasks and corrective follow up.",
      "test": "Walk a fictional incident through roles, communications and restoration tasks without sending messages.",
      "acceptance": "The written plan gives responsible personnel an executable sequence for maintaining or restoring compliance.",
      "recurrence": "With plan and operational changes."
    },
    {
      "id": "NY-DW-INCIDENT-NOTICE",
      "track": "drinking-water",
      "scopeKey": "dw-all-covered",
      "kind": "requirement",
      "title": "Notify DOH of a qualifying cyber incident",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.3(e); 5-E.9",
      "scope": "A defined cybersecurity incident that has created or may create a public health hazard, including at otherwise excluded covered systems.",
      "duty": "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.",
      "owner": "Authorized reporting lead with operating authority",
      "evidence": "Event chronology, determination basis and time, report and delivery receipt.",
      "test": "Compare the recorded determination with the reporting time; do not substitute detection alone for the defined trigger.",
      "acceptance": "The qualifying incident is reported on time through the prescribed process and parallel duties remain tracked.",
      "recurrence": "Each qualifying incident."
    },
    {
      "id": "NY-DW-DEFICIENCY-CONSULT",
      "track": "drinking-water",
      "scopeKey": "dw-all-covered",
      "kind": "requirement",
      "title": "Consult after a State deficiency notice",
      "sourceId": "NYDOH-SUBPART51",
      "section": "5-1.71(c); Appendix 5-E.1(d)",
      "scope": "State notification that a significant deficiency exists; section 5-1.71 also has broader public water system application.",
      "duty": "Consult with the State regarding corrective action after receiving its significant deficiency notice.",
      "timing": "Within 30 days of the State notification.",
      "owner": "Supplier of water and authorized compliance representative",
      "evidence": "State notice, receipt date, consultation record and agreed actions.",
      "test": "Trace the dated State notice to documented consultation.",
      "acceptance": "Consultation occurred within the required period and any earlier State direction is recorded.",
      "recurrence": "Each State significant deficiency notification."
    },
    {
      "id": "NY-DW-DEFICIENCY-CORRECT",
      "track": "drinking-water",
      "scopeKey": "dw-all-covered",
      "kind": "requirement",
      "title": "Correct the deficiency or comply with its action plan",
      "sourceId": "NYDOH-SUBPART51",
      "section": "5-1.71(c) and (d); Appendix 5-E.1(d)",
      "scope": "State notified significant deficiency and any applicable public health hazard.",
      "duty": "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.",
      "owner": "Supplier of water and corrective action owner",
      "evidence": "State notice, action plan, milestones, completion evidence and State correspondence.",
      "test": "Compare the notice and required schedule with demonstrated progress and completed corrections.",
      "acceptance": "The deficiency is corrected or the system is in compliance with the applicable action plan; opening a work ticket alone is insufficient.",
      "recurrence": "Through required correction and verification."
    },
    {
      "id": "NY-DW-ERP-RECURRENCE",
      "track": "drinking-water",
      "scopeKey": "dw-all-covered",
      "kind": "requirement",
      "title": "Keep State emergency plan submissions current",
      "sourceId": "NYDOH-SUBPART51",
      "section": "5-1.33(e)",
      "scope": "Community water systems supplying more than 3,300 people; other systems may be directed to prepare a plan under 5-1.33(f).",
      "duty": "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.",
      "owner": "Emergency plan owner",
      "evidence": "Plan versions, State receipts, major change dates and annual contact submission.",
      "test": "Reconcile plan submissions with the five year cycle, changes and annual contact update.",
      "acceptance": "Each separate submission and update trigger is tracked and met.",
      "recurrence": "Five year, change driven and annual duties remain separate."
    },
    {
      "id": "NY-DW-ERP-PUBLIC-REVIEW",
      "track": "drinking-water",
      "scopeKey": "dw-all-covered",
      "kind": "requirement",
      "title": "Handle plan comment and protected information correctly",
      "sourceId": "NYDOH-SUBPART51",
      "section": "5-1.33(d) and (h); Appendix 5-E.10",
      "scope": "Required emergency plan public review and submitted information.",
      "duty": "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.",
      "owner": "System owner with counsel or records officer",
      "evidence": "Publication record, comment period, comments and protected information determination.",
      "test": "Check the publication dates and comment record; verify sensitive technical details were handled under the correct authority.",
      "acceptance": "Public review requirements and documented security protections are both addressed; confidentiality is not assumed for every record.",
      "recurrence": "Before relevant final submissions."
    },
    {
      "id": "NY-WW-SCOPE",
      "track": "wastewater",
      "scopeKey": "ww-all-spdes",
      "kind": "requirement",
      "title": "Separate permit reporting from POTW controls",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.2(a)(27), (78), (94); 750-2.7(h); 750-2.9(d) through (f)",
      "scope": "All SPDES permittees for reporting; POTWs for the additional plans and controls.",
      "duty": "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.",
      "owner": "Legally responsible party and permit coordinator",
      "evidence": "SPDES permit, ownership record, design flow basis and data system inventory.",
      "test": "Compare the facility profile with the permit and adopted definitions.",
      "acceptance": "Private permittees retain reporting duties and small POTWs retain plans and controls; no drinking water threshold is substituted.",
      "recurrence": "On permit, ownership or design changes."
    },
    {
      "id": "NY-WW-NOTIFY-ORAL",
      "track": "wastewater",
      "scopeKey": "ww-all-spdes",
      "kind": "requirement",
      "title": "Report a wastewater cyber incident promptly",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.2(a)(27); 750-2.7(h)(1)",
      "scope": "All SPDES permittees when a defined cybersecurity incident occurs.",
      "duty": "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.",
      "owner": "Permittee's reporting lead",
      "evidence": "Awareness time and timezone, initial facts, online receipt, call record and recipient.",
      "test": "Trace the defined incident and awareness time to both the initial filing and oral notification record.",
      "acceptance": "The notice uses known facts without waiting for a complete examination and meets the oral reporting deadline.",
      "recurrence": "Each qualifying incident.",
      "guidanceSourceId": "NYDEC-IMPLEMENTATION"
    },
    {
      "id": "NY-WW-NOTIFY-WRITTEN",
      "track": "wastewater",
      "scopeKey": "ww-all-spdes",
      "kind": "requirement",
      "title": "Complete the written wastewater incident report",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.7(h)(2)",
      "scope": "All SPDES permittees after a defined cybersecurity incident.",
      "duty": "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.",
      "owner": "Permittee's reporting lead",
      "evidence": "Eight required subject areas, supporting facts, approved report version and submission receipt.",
      "test": "Check the report against each statutory information category and the awareness based deadline.",
      "acceptance": "The written report covers every required category and is submitted on time.",
      "recurrence": "Each qualifying incident.",
      "guidanceSourceId": "NYDEC-IMPLEMENTATION"
    },
    {
      "id": "NY-WW-PARALLEL-NOTICES",
      "track": "wastewater",
      "scopeKey": "ww-all-spdes",
      "kind": "requirement",
      "title": "Keep other incident notices open",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.7(h)(3)",
      "scope": "Other reporting and notification duties applicable under 750-2.7 and the permit.",
      "duty": "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.",
      "owner": "Permit coordinator and reporting lead",
      "evidence": "Parallel notice register, scope decisions and receipts.",
      "test": "Check whether a cyber incident with operational or discharge effects has been screened for other notices.",
      "acceptance": "The cyber report is not treated as satisfying every other reporting duty.",
      "recurrence": "Each incident and permit or rule change."
    },
    {
      "id": "NY-WW-ERP",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Establish the wastewater emergency plan",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(d)(1)",
      "scope": "All POTWs.",
      "duty": "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.",
      "owner": "POTW operating authority and emergency plan owner",
      "evidence": "Dated plan, eligibility decision for existing plan or template basis, roles and resources.",
      "test": "Trace the required plan elements to actual site procedures, contacts and resource availability.",
      "acceptance": "A qualifying written plan is established, maintained and implemented.",
      "recurrence": "Maintain continuously and update when required.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-WWERP-2021",
          "locator": "Introduction and facility planning sections"
        }
      ]
    },
    {
      "id": "NY-WW-ERP-CONTACT",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Update changed emergency contacts",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(d)(2)",
      "scope": "Titles and contact information in the POTW emergency plan.",
      "duty": "Update the emergency plan after its responsible titles or contact details change.",
      "timing": "Within 30 days of the change.",
      "owner": "Emergency plan owner",
      "evidence": "Change date, revised plan, distribution record and current roster.",
      "test": "Compare recent personnel and contact changes with the controlled plan and its distributed copies.",
      "acceptance": "Changed titles and contacts are corrected within 30 days.",
      "recurrence": "Each title or contact change."
    },
    {
      "id": "NY-WW-ERP-COPIES",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Keep secure printed plans on and off site",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(d)(3)",
      "scope": "POTW emergency plan including its incorporated cyber plan.",
      "duty": "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.",
      "owner": "Emergency plan custodian",
      "evidence": "Copy register, version dates, location and authorized access record.",
      "test": "Have the custodian demonstrate retrieval of current copies without publishing their sensitive contents.",
      "acceptance": "Current printed copies exist in both required locations with controlled access.",
      "recurrence": "On plan revision or custody changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 114; response plan availability"
        },
        {
          "sourceId": "IBR-EPA-WWERP-2021",
          "locator": "Introduction; plan copies"
        }
      ]
    },
    {
      "id": "NY-WW-ERP-CERT",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Certify the ERP requirements annually",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(d)(4); 750-2.9(f)",
      "scope": "All POTWs.",
      "duty": "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.",
      "owner": "Principal executive officer, ranking elected official or qualifying authorized municipal representative",
      "evidence": "Supporting work, signed certification, signer authority and DEC receipt.",
      "test": "Trace the certification to evidence for 750-2.9(d)(1) through (3) and verify the signer.",
      "acceptance": "A supported ERP certification reaches DEC by the deadline.",
      "recurrence": "Annually by March 28."
    },
    {
      "id": "NY-WW-ACCESS",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Write and apply least privilege access rules",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(i)(a)",
      "scope": "OT, SPDES program data, IT permitting direct or indirect access to either, and the ERP.",
      "duty": "Establish, maintain and implement written access rules or procedures consistent with least privilege.",
      "timing": "By March 11, 2027 and maintained thereafter.",
      "owner": "Access owner with operations and data owners",
      "evidence": "Written rules, role approvals, account population and actual permissions.",
      "test": "Compare sampled users with assigned duties across all four required asset and information categories.",
      "acceptance": "Written rules govern actual access and reviewed permissions are limited to assigned work.",
      "recurrence": "Annual policy review and event updates are separate duties.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Page 36, AC-6"
        },
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Pages 98 and 99"
        }
      ]
    },
    {
      "id": "NY-WW-PASSWORDS",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Set and implement password rules",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(i)(b)",
      "scope": "Authentication within the required access rules.",
      "duty": "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.",
      "owner": "Identity and OT access owners",
      "evidence": "Password rules, supported configuration, feasibility decisions and exception handling.",
      "test": "Compare policy to configuration without collecting passwords; check the chosen method against the incorporated guidance.",
      "acceptance": "The written approach addresses all three password subjects and is implemented for its scope.",
      "recurrence": "With access policy review and changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Question 2.B and related factsheet; minimum length as feasible"
        },
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Page 139; password based authentication"
        }
      ]
    },
    {
      "id": "NY-WW-MFA",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Require MFA for allowed remote OT access",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(i)(c)",
      "scope": "Remote access to OT allowed under the POTW's access rules.",
      "duty": "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.",
      "owner": "Remote access owner",
      "evidence": "Route inventory, authentication configuration and authorized demonstration record.",
      "test": "Inspect each selected permitted route's authentication controls without conducting an unauthorized connection.",
      "acceptance": "Allowed remote OT access requires MFA; unsupported routes remain unresolved.",
      "recurrence": "On remote route or authentication changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Question 2.H"
        },
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 106"
        },
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Pages 132 and 133"
        }
      ]
    },
    {
      "id": "NY-WW-DEFAULTS",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Disallow preset and default credentials",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(i)(d)",
      "scope": "Assets covered by the POTW's access and authentication rules.",
      "duty": "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.",
      "owner": "Asset and access owners",
      "evidence": "Credential configuration attestations, vendor capabilities and remediation decisions.",
      "test": "Review records or an authorized demonstration without disclosing the credentials.",
      "acceptance": "Default or preset credentials are not allowed by the implemented rules.",
      "recurrence": "On equipment installation, reset and review.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Question 2.A"
        },
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 123"
        },
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Page 140"
        }
      ]
    },
    {
      "id": "NY-WW-ACCESS-REVIEW",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Review access rules annually",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(i)(e)",
      "scope": "Written access control and authentication rules or procedures.",
      "duty": "Review the access rules and procedures at least annually.",
      "timing": "At least annually by March 28, beginning in 2027.",
      "owner": "Access policy owner",
      "evidence": "Dated review, participants, conclusions and resulting changes.",
      "test": "Compare the last review with the current policy edition and open changes.",
      "acceptance": "A documented review occurs by the annual deadline.",
      "recurrence": "At least annually by March 28."
    },
    {
      "id": "NY-WW-ACCESS-UPDATE",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Update access rules after an incident or assessment",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(i)(f)",
      "scope": "Written access control and authentication rules or procedures.",
      "duty": "Update the rules after a cyber incident or a cybersecurity assessment or audit.",
      "timing": "Within 90 days after the triggering incident, assessment or audit.",
      "owner": "Access policy owner",
      "evidence": "Trigger date, findings, revised procedures and implementation record.",
      "test": "Trace recent incidents and assessments to the dated policy updates.",
      "acceptance": "Required updates occur within 90 days of each relevant trigger.",
      "recurrence": "Each incident, assessment or audit."
    },
    {
      "id": "NY-WW-INVENTORY",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Include the full cyber asset inventory",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.2(a)(25); 750-2.9(e)(1)(ii)(a)",
      "scope": "Reachable OT and IT connected to OT or serving as the system of record for SPDES program data.",
      "duty": "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.",
      "owner": "Asset owner and vulnerability process owner",
      "evidence": "Inventory with asset identity, role, owner, connectivity and data function.",
      "test": "Reconcile drawings and maintenance or procurement records with representative OT and SPDES data assets; avoid unapproved scanning.",
      "acceptance": "The inventory covers the regulatory definition and supported asset boundaries.",
      "recurrence": "When assets are added or decommissioned.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Question 1.A; apply DEC's broader asset definition"
        },
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Pages 107 through 110"
        }
      ]
    },
    {
      "id": "NY-WW-REMOTE-INVENTORY",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Identify remotely accessible assets",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(b)",
      "scope": "Assets in the cyber asset inventory.",
      "duty": "Identify which inventoried assets can be accessed remotely.",
      "timing": "By March 11, 2027 and as access changes.",
      "owner": "Asset owner and remote access owner",
      "evidence": "Remote accessibility field, path references and vendor access records.",
      "test": "Compare network and vendor records with the inventory's remote access classification.",
      "acceptance": "Remote capability is identified for the relevant population, with unknown paths marked unresolved.",
      "recurrence": "On asset or connection changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CIRP-2025",
          "locator": "Page 4; remote OT systems and personnel"
        }
      ]
    },
    {
      "id": "NY-WW-VULNERABILITIES",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Identify known asset vulnerabilities",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(c)",
      "scope": "Assets within the cyber asset inventory.",
      "duty": "Identify known cybersecurity vulnerabilities in inventoried assets.",
      "timing": "By March 11, 2027 and as vulnerability information changes.",
      "owner": "Vulnerability process owner with vendor support",
      "evidence": "Asset versions, dated advisories, applicability decisions and findings.",
      "test": "Match a sample of inventory entries to relevant vendor and authoritative advisories using read only research.",
      "acceptance": "Known relevant vulnerabilities are identified and unsupported version information stays unresolved.",
      "recurrence": "When new vulnerabilities are identified.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 94; vulnerability information"
        },
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Questions 1.G/H"
        }
      ]
    },
    {
      "id": "NY-WW-RISK",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Assess likelihood and operating consequences",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(d)",
      "scope": "Known vulnerabilities identified for inventoried assets.",
      "duty": "Assess the likelihood of exploitation and consequences for the POTW's normal operations.",
      "timing": "During vulnerability assessment and review.",
      "owner": "Vulnerability owner and operating authority",
      "evidence": "Risk rationale, affected process, data dependencies and supporting facts.",
      "test": "Trace selected findings through their likelihood and operational consequence rationale.",
      "acceptance": "Both likelihood and consequence inform the assessment; a vendor severity score alone is not the entire analysis.",
      "recurrence": "When exposure or consequences change.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 95; OT risk strategy"
        }
      ]
    },
    {
      "id": "NY-WW-PRIORITY",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Prioritize vulnerabilities by assessed risk",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(e)",
      "scope": "Known vulnerabilities with assessed risks.",
      "duty": "Prioritize vulnerabilities using the assessed risks.",
      "timing": "During vulnerability management.",
      "owner": "Vulnerability process owner and operating authority",
      "evidence": "Prioritized register, rationale and dependency decisions.",
      "test": "Compare work priorities with assessed likelihood and operational consequences.",
      "acceptance": "The sequence follows supported risk decisions and material exceptions have a recorded rationale.",
      "recurrence": "When the risk picture changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 95"
        }
      ]
    },
    {
      "id": "NY-WW-REMEDIATE",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Mitigate or remediate in risk order",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(f)",
      "scope": "Prioritized vulnerabilities.",
      "duty": "Mitigate or remediate vulnerabilities according to the established priority.",
      "timing": "As part of the implemented vulnerability process; use actual risk and authorized operational schedules.",
      "owner": "Corrective action owner and operating authority",
      "evidence": "Approved changes, mitigations, completion evidence and verification results.",
      "test": "Trace selected priorities into implemented action and safely obtained verification records.",
      "acceptance": "Actions address the prioritized risks; planned work is not recorded as verified completion.",
      "recurrence": "Until risk treatment and verification are complete.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Question 1.E"
        },
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Page 52"
        }
      ]
    },
    {
      "id": "NY-WW-VULN-REVIEW",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Review the vulnerability process annually",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(g)",
      "scope": "Written cybersecurity vulnerability management process.",
      "duty": "Review the written process at least annually.",
      "timing": "At least annually by March 28, beginning in 2027.",
      "owner": "Vulnerability process owner",
      "evidence": "Dated review, participating owners, conclusions and revisions.",
      "test": "Check review dates and whether actual asset and vulnerability changes informed the review.",
      "acceptance": "The process has a documented review by the annual deadline.",
      "recurrence": "At least annually by March 28."
    },
    {
      "id": "NY-WW-VULN-UPDATE",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Update the process when assets or vulnerabilities change",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(ii)(h)",
      "scope": "Written vulnerability management process and cyber asset inventory.",
      "duty": "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.",
      "owner": "Asset and vulnerability process owners",
      "evidence": "Asset change events, advisory dates and process or register updates.",
      "test": "Trace recent additions, removals and vulnerability discoveries to the corresponding updates.",
      "acceptance": "The process is updated for each applicable trigger rather than waiting for the annual review.",
      "recurrence": "Each specified asset or vulnerability event."
    },
    {
      "id": "NY-WW-NETWORK",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Document and protect the network structure",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(1)(iii)",
      "scope": "POTW operational technology and its IT or external connections.",
      "duty": "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.",
      "owner": "Network owner and operations owner",
      "evidence": "Current network description, permitted paths, boundary controls and supporting configuration records.",
      "test": "Compare drawings and approved rule sets with the described architecture through a safe review.",
      "acceptance": "The documented protection method matches actual necessary connections and control evidence.",
      "recurrence": "On network changes and relevant assessments.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-CYBER-2024",
          "locator": "Questions 2.F, 2.W and 2.X"
        },
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Pages 67 through 89 and 105"
        }
      ]
    },
    {
      "id": "NY-WW-LOGGING",
      "track": "wastewater",
      "scopeKey": "ww-large",
      "kind": "requirement",
      "title": "Monitor and log the required network activity",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(2)",
      "scope": "POTWs with design flow at least 10 MGD unless the specific no connection or outward only device exception is supported.",
      "duty": "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.",
      "owner": "Network monitoring owner",
      "evidence": "Design flow record, network diagram, logging sample, retrieval demonstration or documented exception basis.",
      "test": "Check actual connections, one way device capabilities where relevant, and safe retrieval of sample logs.",
      "acceptance": "Required monitoring and logging are implemented, or the specific exception has adequate technical support.",
      "recurrence": "On network, design flow or device changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-NIST-80082R3",
          "locator": "Pages 73, 92 and 207"
        },
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Page 30; one way information flow"
        }
      ]
    },
    {
      "id": "NY-WW-IRP",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Incorporate the cyber response plan into the ERP",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(3)",
      "scope": "All POTWs.",
      "duty": "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.",
      "owner": "Incident response owner and emergency plan owner",
      "evidence": "Controlled ERP with incorporated IRP, plan basis, roles, resources and procedures.",
      "test": "Trace a fictional incident through the plan; verify the IRP is incorporated rather than only mentioned as an external document.",
      "acceptance": "The incorporated IRP describes the POTW's preparation and response and satisfies the permitted plan basis.",
      "recurrence": "On plan and operational changes.",
      "incorporatedReferences": [
        {
          "sourceId": "IBR-EPA-INCIDENT-2021",
          "locator": "Preparation, response and recovery checklist"
        },
        {
          "sourceId": "IBR-EPA-CIRP-2025",
          "locator": "Introduction and template instructions"
        },
        {
          "sourceId": "IBR-NIST-80053R5",
          "locator": "Pages 158 and 159"
        }
      ]
    },
    {
      "id": "NY-WW-IBR",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Use the incorporated document editions",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.25(j) through (o); 750-2.9(e)(1) and (4)",
      "scope": "Establishing, maintaining and implementing the specified wastewater controls and plan options.",
      "duty": "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.",
      "owner": "Compliance and technical document owners",
      "evidence": "Edition register, clause mapping, selected methods and supporting control records.",
      "test": "Compare each control's criterion with the adopted rule and the specified incorporated edition.",
      "acceptance": "The selected methods can be traced to the correct editions and legal clause without silently substituting a later version.",
      "recurrence": "On rule, source or control changes."
    },
    {
      "id": "NY-WW-CYBER-CERT",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Certify the cybersecurity controls annually",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(e)(5); 750-2.9(f)",
      "scope": "Municipalities responsible for POTWs.",
      "duty": "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.",
      "owner": "Authorized municipal certification signer",
      "evidence": "Control evidence, unresolved findings, signed certification and DEC receipt.",
      "test": "Trace the certification to actual evidence and confirm that incomplete work is not represented as compliance.",
      "acceptance": "A supported certification is signed by the correct authority and submitted on time.",
      "recurrence": "Annually by March 28."
    },
    {
      "id": "NY-WW-CERT-AUTHORITY",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "requirement",
      "title": "Use the authorized municipal signer and filing process",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.9(f)(1) through (3)",
      "scope": "Required POTW ERP and cybersecurity certifications.",
      "duty": "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.",
      "owner": "Municipal executive or ranking elected official",
      "evidence": "Delegation, role and oversight basis, DEC authorization receipt and certification record.",
      "test": "Confirm the signer is eligible and reviewed information prepared under the required supervision. A contractor is not eligible solely because it performs the work.",
      "acceptance": "The signer and filing method satisfy the rule; current DEC guidance uses nForm.",
      "recurrence": "Each filing and signer change.",
      "guidanceSourceId": "NYDEC-IMPLEMENTATION"
    },
    {
      "id": "NY-WW-TRAINING",
      "track": "wastewater",
      "scopeKey": "ww-operators",
      "kind": "requirement",
      "title": "Complete cybersecurity hours for operator renewal",
      "sourceId": "NYDEC-650-2026",
      "section": "650.8; 650.12(c)(2)",
      "scope": "New York certified wastewater operators with certifications expiring on or after January 1, 2027.",
      "duty": "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.",
      "owner": "Certified operator and training coordinator",
      "evidence": "Grade, certification expiration, approved course and completed hours.",
      "test": "Compare the operator's grade and renewal dates with eligible cybersecurity training records.",
      "acceptance": "The required approved hours fall within the applicable renewal period.",
      "recurrence": "Each five year renewal.",
      "guidanceSourceId": "NYDEC-IMPLEMENTATION"
    },
    {
      "id": "NY-WW-EXERCISE",
      "track": "wastewater",
      "scopeKey": "ww-potw",
      "kind": "guidance",
      "title": "Rehearse the response without affecting operations",
      "sourceId": "NYDEC-IMPLEMENTATION",
      "section": "Cybersecurity Incident Response Plans, exercise question",
      "scope": "POTW staff and response partners selected by the operating authority.",
      "duty": "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.",
      "owner": "Incident response owner and operating authority",
      "evidence": "Fictional scenario, participant roles, observations, actions and retest record.",
      "test": "Rehearse with no external transmission and no live control changes; record what was not demonstrated.",
      "acceptance": "The exercise reveals actionable gaps and responsible owners without being treated as proof that every control works.",
      "recurrence": "Recommended regularly, preferably annually; after material changes as appropriate."
    },
    {
      "id": "US-DW-RRA",
      "track": "federal",
      "scopeKey": "federal-cws",
      "kind": "requirement",
      "title": "Complete the federal risk and resilience assessment",
      "sourceId": "USEPA-AWIA",
      "section": "SDWA 1433(a); RRA requirements",
      "scope": "Community drinking water systems serving more than 3,300 people.",
      "duty": "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.",
      "owner": "Community water system owner and authorized assessment lead",
      "evidence": "Complete RRA scope, review record, certification by PWSID and receipt.",
      "test": "Check that the assessment covers the statutory categories beyond cybersecurity and that the correct system was certified.",
      "acceptance": "The broader RRA and its certification meet the applicable cycle, with omissions identified explicitly.",
      "recurrence": "Review, revise as needed and certify at least every five years."
    },
    {
      "id": "US-DW-ERP",
      "track": "federal",
      "scopeKey": "federal-cws",
      "kind": "requirement",
      "title": "Prepare the federal emergency plan from the assessment",
      "sourceId": "USEPA-AWIA",
      "section": "SDWA 1433(b); ERP requirements",
      "scope": "Community drinking water systems serving more than 3,300 people.",
      "duty": "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.",
      "owner": "Community water system emergency plan owner",
      "evidence": "Actual RRA certification date, ERP edition, coordination record and ERP certification receipt.",
      "test": "Derive the ERP deadline from the actual RRA certification and trace RRA findings into the plan.",
      "acceptance": "The plan and certification meet the actual six month deadline rather than an assumed common year end date.",
      "recurrence": "After the applicable RRA certification and review cycle."
    },
    {
      "id": "US-DW-CERTIFICATION",
      "track": "federal",
      "scopeKey": "federal-cws",
      "kind": "requirement",
      "title": "Submit the federal certifications by PWSID",
      "sourceId": "USEPA-AWIA-FILING",
      "section": "Electronic submission and certification statements",
      "scope": "Each covered community water system's PWSID.",
      "duty": "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.",
      "owner": "Authorized certifying official",
      "evidence": "PWSID, signed statements, actual submission dates and available acknowledgments.",
      "test": "Compare the system identifier, signer, statement type and deadline with the saved submission record.",
      "acceptance": "Each system has the correct timely certification and a retained filing record.",
      "recurrence": "Each required certification cycle."
    },
    {
      "id": "US-DW-RETENTION",
      "track": "federal",
      "scopeKey": "federal-cws",
      "kind": "requirement",
      "title": "Retain the federal assessment and plan securely",
      "sourceId": "USEPA-AWIA",
      "section": "ERP requirements; five year review requirements",
      "scope": "RRA and ERP for each covered community water system.",
      "duty": "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.",
      "owner": "System records custodian",
      "evidence": "Controlled document versions, access permissions, retention dates and retrieval record.",
      "test": "Verify secure retrieval of the certified editions and the next scheduled review without disclosing sensitive contents publicly.",
      "acceptance": "Required editions remain retrievable for the retention period and the next review is assigned.",
      "recurrence": "Each certification and retention review."
    }
  ],
  "reporting": [
    {
      "id": "NY-DW-VULN-NOTICE",
      "track": "drinking-water",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.1(c)(2); 5-E.5(e)",
      "event": "A CVA vulnerability that may affect Subpart compliance, or a situation that may pose a public health risk.",
      "trigger": "Identification of the qualifying vulnerability or situation, with time and timezone.",
      "deadline": "Within 48 hours of identification.",
      "recipient": "NYSDOH through the applicable section 5-1.77 process; confirm the system's current department contact and channel.",
      "record": "Scope decision, trigger, reporter and alternate, facts known, submitted version, recipient, submission time and receipt."
    },
    {
      "id": "NY-DW-INCIDENT-NOTICE",
      "track": "drinking-water",
      "sourceId": "NYDOH-APP5E",
      "section": "5-E.3(e); 5-E.9",
      "event": "A defined cybersecurity incident that has created or may create a public health hazard.",
      "trigger": "Determination that the qualifying incident occurred, with time, timezone and basis. Keep earlier detection times as separate chronology entries.",
      "deadline": "As soon as possible and no later than 24 hours after determination.",
      "recipient": "NYSDOH in the prescribed section 5-1.77(a) manner; keep other applicable notices separate.",
      "record": "Detection and determination times, impact facts, decision owner, submission version, method, time, recipient and receipt."
    },
    {
      "id": "NY-WW-NOTIFY-ORAL",
      "track": "wastewater",
      "sourceId": "NYDEC-750-2026",
      "section": "750-1.2(a)(27); 750-2.7(h)(1)",
      "event": "A cyber event causing or reasonably likely to harm normal operations, compromise SPDES program data or physical assets, or delay or prevent permit compliance.",
      "trigger": "Time the permittee becomes aware of the defined incident.",
      "deadline": "As soon as possible and no later than 24 hours after awareness.",
      "recipient": "Regional water engineer. Current DEC instructions: submit the initial online report, then immediately notify the regional water engineer or manager orally. If unreachable, use DEC Dispatch at (844) 332-3267.",
      "record": "Awareness and discovery times, discoverer, known incident facts, affected IT or OT, disruption and duration, data or physical impacts, actions, online receipt and oral call record.",
      "guidanceSourceId": "NYDEC-IMPLEMENTATION"
    },
    {
      "id": "NY-WW-NOTIFY-WRITTEN",
      "track": "wastewater",
      "sourceId": "NYDEC-750-2026",
      "section": "750-2.7(h)(2)",
      "event": "Follow up written report for the same defined wastewater cyber incident.",
      "trigger": "The same permittee awareness time used for the initial notice, not the initial submission time.",
      "deadline": "Within 30 days after awareness.",
      "recipient": "Regional water engineer through DEC's current online report process.",
      "record": "Discovery date and time, discoverer, incident description, affected IT or OT, actual or anticipated disruption and duration, data and physical loss or absence of loss, mitigation or remediation, approved version and receipt.",
      "guidanceSourceId": "NYDEC-IMPLEMENTATION"
    }
  ],
  "notes": [
    "The main January 1, 2027 drinking water date does not defer incident reporting or operator training already effective upon adoption. Wastewater controls and plans have a March 11, 2027 implementation date and separate March 28 certifications.",
    "Record populations, combined wholesale and retail population, service connections and design flow as separate facts. More than 3,300 and more than 50,000 are strict greater than thresholds. The wastewater logging threshold is at least 10 MGD.",
    "The drinking water no connection exclusion preserves emergency response planning and incident reporting. Training has its own scope and is not removed by this exclusion. A one way logging exception is not a general exemption from all controls.",
    "The operator and operating authority approve how evidence is gathered. The toolkit does not authorize active scans, exploitation, credential attempts, PLC changes, production shutdowns or live recovery tests. Use records, interviews and approved demonstrations; record untested conditions.",
    "The department approved forms, current filing channels, permit conditions and State directions control an actual submission. The toolkit is a work record and cannot submit or certify on the utility's behalf.",
    "No control or criterion is satisfied merely because a document was written. Keep evidence, examination results, corrective work and verified closure separate.",
    "Confidentiality is governed by applicable law and the appropriate disclosure procedure. DOH Appendix 5-E.10 and 5-1.33(h), and DEC 616.7, do not establish a blanket promise that every worksheet is exempt from disclosure.",
    "Additional municipal cyber reporting, privacy, PSC, financial services, insurance and contractual duties require their own applicability decisions. They are not silently treated as satisfied by these DOH, DEC or federal records.",
    "This edition gives a complete working breakdown of the selected cybersecurity clauses, not every environmental, drinking water or municipal legal obligation. A site specific reviewer must resolve uncertain scope, conflicting directions and evidence limits."
  ]
}
