Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

How Do You Comply With NY DFS 23 NYCRR 500.17 Notices to the Superintendent?

Short Answer

23 NYCRR 500.17 requires three notices to DFS: notice of a cybersecurity incident at the covered entity, an affiliate or a third-party service provider within 72 hours after determining it occurred; an annual filing by April 15 of either a certification of material compliance or an acknowledgment of noncompliance, signed by the highest-ranking executive and the CISO, with supporting records kept for five years; and notice of any extortion payment within 24 hours, followed by a written explanation within 30 days.

23 NYCRR 500.17 Notices to Superintendent at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.17 Notices to Superintendent.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity. Entities exempt under 500.19 still file a Notice of Exemption under 500.19(f).
  • Class A companies: None beyond the general requirement.
  • Limited exemption (500.19(a)): Not exempt under 500.19(a), (c) or (d).
  • Compliance dates: The new notice requirements applied from December 1, 2023, 30 days after the Second Amendment took effect (500.22(d)(1)). The annual notice of compliance is due each April 15.

Section 500.17 is where Part 500 meets the regulator directly. It sets the 72-hour incident notice, the annual April 15 filing, and the ransom payment notice and explanation.

The Second Amendment changed the incident trigger to the new cybersecurity incident definition in 500.1(g), extended it to incidents at affiliates and third-party service providers, and replaced the old compliance certificate with a choice between a certification of material compliance and an acknowledgment of noncompliance that lists the gaps and a remediation timeline.

What Does 23 NYCRR 500.17 Require?

The following is the text of 23 NYCRR 500.17 Notices to Superintendent as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.

  • (a) Notice of cybersecurity incident.
  • (1) Each covered entity shall notify the superintendent electronically in the form set forth on the department’s website as promptly as possible but in no event later than 72 hours after determining that a cybersecurity incident has occurred at the covered entity, its affiliates, or a third-party service provider.
  • (2) Each covered entity shall promptly provide to the superintendent any information requested regarding such incident. Covered entities shall have a continuing obligation to update the superintendent with material changes or new information previously unavailable.
  • (b) Notice of compliance.
  • (1) Annually each covered entity shall submit to the superintendent electronically by April 15 either:
  • (i) a written certification that:
  • (a) certifies that the covered entity materially complied with the requirements set forth in this Part during the prior calendar year; and
  • (b) shall be based upon data and documentation sufficient to accurately determine and demonstrate such material compliance, including, to the extent necessary, documentation of officers, employees, representatives, outside vendors and other individuals or entities, as well as other documentation, whether in the form of reports, certifications, schedules or otherwise; or
  • (ii) a written acknowledgment that:
  • (a) acknowledges that, for the prior calendar year, the covered entity did not materially comply with all the requirements of this Part;
  • (b) identifies all sections of this Part that the entity has not materially complied with and describes the nature and extent of such noncompliance; and
  • (c) provides a remediation timeline or confirmation that remediation has been completed.
  • (2) Such certification or acknowledgment shall be submitted electronically in the form set forth on the department’s website and shall be signed by the covered entity’s highest-ranking executive and its CISO. If the covered entity does not have a CISO, the certification or acknowledgment shall be signed by the highest-ranking executive and by the senior officer responsible for the cybersecurity program of the covered entity.
  • (3) Each covered entity shall maintain for examination and inspection by the department upon request all records, schedules and other documentation and data supporting the certification or acknowledgment for a period of five years, including the identification of all areas, systems and processes that require or required material improvement, updating or redesign, all remedial efforts undertaken to address such areas, systems and processes, and remediation plans and timelines for their implementation.
  • (c) Notice and explanation of extortion payment. Each covered entity, in the event of an extortion payment made in connection with a cybersecurity event involving the covered entity, shall provide the superintendent electronically, in the form set forth on the department’s website, with the following:
  • (1) within 24 hours of the extortion payment, notice of the payment; and
  • (2) within 30 days of the extortion payment, a written description of the reasons payment was necessary, a description of alternatives to payment considered, all diligence performed to find alternatives to payment and all diligence performed to ensure compliance with applicable rules and regulations including those of the Office of Foreign Assets Control.

Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).

How Does 23 NYCRR 500.17 Map to the Secure Controls Framework (SCF)?

The SCF publishes a NIST IR 8477 Set Theory Relationship Mapping (STRM) between 23 NYCRR Part 500 (2023 Amendment 2) and SCF version 2026.3. It maps 23 NYCRR 500.17 to 7 SCF controls through 22 relationships (22 "intersects with").

How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "Intersects with" means the Part 500 requirement and the SCF control share partial overlap. The strength of relationship runs from 1 (nominal) to 10 (strongest), where 5 is moderately strong and 10 is typically reserved for "equal" and "subset of" relationships.

  • CPL-27 Security, Compliance & Resilience Status Reporting. Intersects with (strength 5): 500.17(a)(1), 500.17(a)(2). SCF control: Mechanisms exist to submit status reporting of the organization's security, compliance and/or resilience program to applicable statutory and/or regulatory authorities, as required.
  • IRO-15 Regulatory & Law Enforcement Contacts. Intersects with (strength 5): 500.17(a)(1). SCF control: Mechanisms exist to maintain incident response contacts with applicable regulatory and law enforcement agencies.
  • IRO-16 Incident Stakeholder Reporting. Intersects with (strength 5): 500.17(a)(1), 500.17(c), 500.17(c)(1), 500.17(c)(2). SCF control: Mechanisms exist to timely-report incidents to applicable: (1) Internal stakeholders; (2) Affected clients & third-parties; and (3) Regulatory authorities.
  • IRO-16.2 Cyber Incident Reporting for Sensitive / Regulated Data. Intersects with (strength 5): 500.17(a)(1). SCF control: Mechanisms exist to report sensitive and/or regulated data incidents in a timely manner.
  • CPL-02 Statutory, Regulatory & Contractual Compliance. Intersects with (strength 5): 500.17(a)(2), 500.17(b)(1), 500.17(b)(1)(i), 500.17(b)(1)(i)(a), 500.17(b)(1)(i)(b), 500.17(b)(1)(ii), 500.17(b)(1)(ii)(a), 500.17(b)(1)(ii)(b), 500.17(b)(1)(ii)(c), 500.17(b)(2), 500.17(b)(3), 500.17(c). SCF control: Mechanisms exist to facilitate the identification and implementation of relevant statutory, regulatory and contractual controls.
  • CPL-19 Legal Assessment of Investigative Inquires. Intersects with (strength 5): 500.17(a)(2). SCF control: Mechanisms exist to determine whether a government agency has an applicable and valid legal basis to request data from the organization and what further steps need to be taken, if necessary.
  • CPL-19.2 Investigation Access Restrictions. Intersects with (strength 5): 500.17(a)(2). SCF control: Mechanisms exist to support official investigations by provisioning government investigators with "least privileges" and "least functionality" to ensure that government investigators only have access to the Technology Assets, Applications, Services and/or Data (TAASD) needed to perform the investigation.

The STRM records "no relationship" for the lead-in text of 500.17(a) and 500.17(b); the numbered paragraphs under them are mapped individually.

Mapping taken from the STRM published with SCF version 2026.3. Download it at no cost: SCF STRM for NY DFS 23 NYCRR 500 (2023 Amendment 2). The SCF explains the method in its Set Theory Relationship Mapping (STRM) guidance.

Common Pitfalls With 23 NYCRR 500.17

The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:

  • Starting the 72-hour clock too late. Notice is due as promptly as possible, and no later than 72 hours after determining that a cybersecurity incident has occurred, including at an affiliate or third-party service provider.
  • Certifying without supporting records. A certification must be based on data and documentation sufficient to accurately determine and demonstrate material compliance. Records must be kept for five years.
  • Avoiding the acknowledgment path. If the entity did not materially comply with all requirements in the prior calendar year, the acknowledgment must identify every section not met, describe the noncompliance and give a remediation timeline or confirm remediation.
  • Missing the extortion payment clock. Notice of an extortion payment is due within 24 hours of payment, and a written description of the reasons, alternatives considered and diligence performed, including OFAC compliance, within 30 days.
  • Not updating DFS. 500.17(a)(2) creates a continuing obligation to update DFS with material changes or new information about the incident.

What Is Reasonable Evidence for 23 NYCRR 500.17?

NY DFS does not publish a fixed evidence list. Under 500.17(b)(3), records supporting the annual certification or acknowledgment must be kept for five years.

The SCF Evidence Request List (ERL) ties evidence artifacts to SCF controls. ERL items linked to the SCF controls mapped to 23 NYCRR 500.17 include:

  • E-IRO-11 Incident Reporting Capability. Documented evidence of a capability to provide situational awareness of incidents to internal stakeholders and generated necessary reporting to affected clients, applicable third-parties and regulatory authorities.
  • E-GOV-22 Contacts With Authorities. Documented evidence of established points of contact with regulatory authorities and law enforcement (e.g., contact roster, notification procedures).
  • E-CPL-01 Statutory, Regulatory & Contractual Obligations. Documented evidence of applicable statutory, regulatory and/or contractual obligations for cybersecurity & data privacy controls.
  • E-GOV-18 Cybersecurity & Data Privacy Status Reports. Documented evidence of status reports of the organization's security, compliance and/or resilience program that were submitted to applicable statutory and/or regulatory authorities.

Records specific to 23 NYCRR 500.17 that typically show the requirement is designed and operating:

  • Incident notification procedure. Criteria for determining a cybersecurity incident and the process for filing within 72 hours.
  • Filing records. Copies of submitted incident notices, updates and annual filings.
  • Certification support file. The data and documentation behind the April 15 certification or acknowledgment.
  • Remediation records. Areas needing material improvement, remedial efforts, and remediation plans and timelines, kept for five years.
  • Extortion payment procedure. Who decides, who notifies DFS within 24 hours, and how the 30-day explanation, including OFAC diligence, is prepared.

Which ComplianceForge Documents Support 23 NYCRR 500.17?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.17 Notices to Superintendent:

Frequently Asked Questions (FAQ)

How quickly must a cybersecurity incident be reported to NY DFS under 23 NYCRR 500.17? As promptly as possible, but in no event later than 72 hours after determining that a cybersecurity incident has occurred at the covered entity, its affiliates or a third-party service provider. The covered entity must also provide requested information promptly and keep DFS updated with material changes or new information.

What is due by April 15 under 500.17(b)? Either a written certification that the covered entity materially complied with Part 500 during the prior calendar year, based on sufficient data and documentation, or a written acknowledgment that it did not materially comply, identifying the sections not met, describing the noncompliance and providing a remediation timeline or confirmation of remediation.

Who signs the annual 500.17(b) filing? The covered entity's highest-ranking executive and its CISO. If there is no CISO, the highest-ranking executive and the senior officer responsible for the cybersecurity program sign.

What must be reported after an extortion payment? Notice of the payment within 24 hours, and within 30 days a written description of why payment was necessary, alternatives considered, diligence performed to find alternatives, and diligence performed to ensure compliance with applicable rules and regulations, including those of the Office of Foreign Assets Control.

Bottom Line on 23 NYCRR 500.17 Notices to Superintendent

500.17 sets the deadlines DFS watches most closely: 72 hours for incidents, April 15 for the annual filing, and 24 hours and 30 days for extortion payments. Build each into procedures, decide early whether you can certify or must acknowledge, and keep five years of supporting records.

Authoritative sources:

This page reproduces New York State regulatory text from 23 NYCRR Part 500. It is educational, not legal advice. Last reviewed: 2026-11-15.

Other 23 NYCRR Part 500 Requirements

Previous section: 500.16 Incident Response and Business Continuity Management. Next section: 500.19 Exemptions. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.