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.16 Incident Response and Business Continuity Management?

Short Answer

23 NYCRR 500.16 requires written incident response plans and business continuity and disaster recovery (BCDR) plans. Incident response plans must cover nine areas, including recovery from backups and root cause analysis, for different event types such as ransomware. BCDR plans must cover six areas. Plans must be accessible to the people who implement them, those people must be trained, plans and backup restoration must be tested at least annually, and backups must be protected from unauthorized alteration or destruction.

23 NYCRR 500.16 Incident Response and Business Continuity Management at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.16 Incident Response and Business Continuity Management.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity that does not qualify for an exemption under 500.19(a), (c) or (d).
  • Class A companies: None beyond the general requirement.
  • Limited exemption (500.19(a)): Exempt. 500.19(a) limited-exemption entities do not need to meet 500.16.
  • Compliance dates: The amended incident response and new business continuity and disaster recovery requirements applied from November 1, 2024, one year after the Second Amendment took effect (500.22(d)(2)).

The Second Amendment expanded 500.16 from an incident response plan into incident response and business continuity management. Plans must contain proactive measures to investigate and mitigate cybersecurity events and to ensure operational resilience.

The incident response plan list grew to nine areas, adding recovery from backups and root cause analysis, and plans must address different types of events, including disruptive events such as ransomware. A new BCDR plan requirement, distribution and training requirements, annual testing and protected backups complete the section.

What Does 23 NYCRR 500.16 Require?

The following is the text of 23 NYCRR 500.16 Incident Response and Business Continuity Management as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.

  • (a) As part of its cybersecurity program, each covered entity shall establish written plans that contain proactive measures to investigate and mitigate cybersecurity events and to ensure operational resilience, including but not limited to incident response, business continuity and disaster recovery plans.
  • (1) Incident response plan. Incident response plans shall be reasonably designed to enable prompt response to, and recovery from, any cybersecurity event materially affecting the confidentiality, integrity or availability of the covered entity’s information systems or the continuing functionality of any aspect of the covered entity’s business or operations. Such plans shall address the following areas with respect to different types of cybersecurity events, including disruptive events such as ransomware incidents:
  • (i) the goals of the incident response plan;
  • (ii) the internal processes for responding to a cybersecurity event;
  • (iii) the definition of clear roles, responsibilities and levels of decision-making authority;
  • (iv) external and internal communications and information sharing;
  • (v) identification of requirements for the remediation of any identified weaknesses in information systems and associated controls;
  • (vi) documentation and reporting regarding cybersecurity events and related incident response activities;
  • (vii) recovery from backups;
  • (viii) preparation of root cause analysis that describes how and why the event occurred, what business impact it had, and what will be done to prevent reoccurrence; and
  • (ix) updating of incident response plans as necessary.
  • (2) Business continuity and disaster recovery (BCDR) plan. BCDR plans shall be reasonably designed to ensure the availability and functionality of the covered entity’s information systems and material services and protect the covered entity’s personnel, assets and nonpublic information in the event of a cybersecurity-related disruption to its normal business activities. Such plans shall, at minimum:
  • (i) identify documents, data, facilities, infrastructure, services, personnel and competencies essential to the continued operations of the covered entity’s business;
  • (ii) identify the supervisory personnel responsible for implementing each aspect of the BCDR plan;
  • (iii) include a plan to communicate with essential persons in the event of a cybersecurity-related disruption to the operations of the covered entity, including employees, counterparties, regulatory authorities, third-party service providers, disaster recovery specialists, the senior governing body and any other persons essential to the recovery of documentation and data and the resumption of operations;
  • (iv) include procedures for the timely recovery of critical data and information systems and to resume operations as soon as reasonably possible following a cybersecurity-related disruption to normal business activities;
  • (v) include procedures for backing up or copying, with sufficient frequency, information essential to the operations of the covered entity and storing such information offsite; and
  • (vi) identify third parties that are necessary to the continued operations of the covered entity’s information systems.
  • (b) Each covered entity shall ensure that current copies of the plans or relevant portions therein are distributed or are otherwise accessible, including during a cybersecurity event, to all employees necessary to implement such plans.
  • (c) Each covered entity shall provide relevant training to all employees responsible for implementing the plans regarding their roles and responsibilities.
  • (d) Each covered entity shall periodically, but at a minimum annually, test its:
  • (1) incident response and BCDR plans with all staff and management critical to the response, and shall revise the plan as necessary; and
  • (2) ability to restore its critical data and information systems from backups.
  • (e) Each covered entity shall maintain backups necessary to restore material operations. The backups shall be adequately protected from unauthorized alterations or destruction.

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

How Does 23 NYCRR 500.16 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.16 to 19 SCF controls through 39 relationships (1 "equal", 10 "subset of", 28 "intersects with").

How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "Equal" means the Part 500 requirement and the SCF control are semantically equivalent. "Subset of" means the Part 500 requirement is fully contained within 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.

  • BCD-09 Contingency Training. Equal (strength 10): 500.16(c). SCF control: Mechanisms exist to adequately train contingency personnel and applicable stakeholders in their contingency roles and responsibilities.
  • IRO-08 Incident Response Plan (IRP). Subset of (strength 10): 500.16(b). Intersects with (strength 5): 500.16(a), 500.16(a)(1), 500.16(a)(1)(i), 500.16(a)(1)(ii), 500.16(a)(1)(iii), 500.16(a)(1)(iv), 500.16(a)(1)(v), 500.16(a)(1)(vi), 500.16(a)(1)(vii), 500.16(a)(1)(viii). SCF control: Mechanisms exist to maintain and make available a current and viable Incident Response Plan (IRP) to all stakeholders.
  • BCD-02 Business Continuity Management System (BCMS). Subset of (strength 10): 500.16(a)(2), 500.16(a)(2)(i), 500.16(a)(2)(ii), 500.16(a)(2)(iii), 500.16(a)(2)(iv), 500.16(a)(2)(v), 500.16(a)(2)(vi), 500.16(b). SCF control: Mechanisms exist to operate a Business Continuity Management System (BCMS) to achieve resilient Technology Assets, Applications, Services and/or Data (TAASD) during: (1) Routine operations; and (2) Adverse conditions.
  • BCD-10 Contingency Plan Testing & Exercises. Subset of (strength 10): 500.16(d)(2). Intersects with (strength 8): 500.16(d)(1). SCF control: Mechanisms exist to conduct tests and/or exercises to evaluate the contingency plan's effectiveness and the organization's readiness to execute the plan.
  • IRO-09 Incident Response Capabilities Testing. Intersects with (strength 8): 500.16(d)(1). SCF control: Mechanisms exist to formally test incident response capabilities through realistic exercises to determine the operational effectiveness of those capabilities.
  • IRO-02 Incident Response Operations. Intersects with (strength 5): 500.16(a). SCF control: Mechanisms exist to implement and govern processes and documentation to facilitate an organization-wide response capability for cybersecurity and data protection-related incidents.
  • IRO-06 Incident Handling. Intersects with (strength 5): 500.16(a). SCF control: Mechanisms exist to cover: (1) Preparation; (2) Automated event detection or manual incident report intake; (3) Analysis; (4) Containment; (5) Eradication; and (6) Recovery.
  • IRO-08.1 Incident Response Plan (IRP) Update. Intersects with (strength 5): 500.16(a)(1)(ix). SCF control: Mechanisms exist to regularly review and modify incident response practices to incorporate lessons learned, business process changes and industry developments, as necessary.
  • AST-05 Identify Critical Assets. Intersects with (strength 5): 500.16(a)(2)(i), 500.16(a)(2)(vi). SCF control: Mechanisms exist to identify and document the critical Technology Assets, Applications, Services and/or Data (TAASD) that support essential missions and business functions.
  • BCD-05 Recovery Operations Criteria. Intersects with (strength 5): 500.16(a)(2)(ii). SCF control: Mechanisms exist to define specific criteria that must be met to initiate Business Continuity / Disaster Recovery (BC/DR) plans that facilitate business continuity operations capable of meeting applicable Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).
  • HRS-03 Position Categorization. Intersects with (strength 5): 500.16(a)(2)(ii). SCF control: Mechanisms exist to manage personnel security risk by assigning a risk designation to all positions and establishing screening criteria for individuals filling those positions.
  • HRS-04 Defined Roles & Responsibilities. Intersects with (strength 5): 500.16(a)(2)(ii). SCF control: Mechanisms exist to define cybersecurity roles & responsibilities for all personnel.
  • BCD-06 Recovery Operations Communications. Intersects with (strength 5): 500.16(a)(2)(iii). SCF control: Mechanisms exist to communicate the status of recovery activities and progress in restoring operational capabilities to designated internal and external stakeholders.
  • BCD-08.1 Continue Essential Mission & Business Functions. Intersects with (strength 5): 500.16(a)(2)(iv). SCF control: Mechanisms exist to continue essential missions and business functions with little or no loss of operational continuity and sustain that continuity until full system restoration of primary processing and/or storage sites is performed.
  • BCD-04.1 Recovery Time / Point Objectives (RTO / RPO). Intersects with (strength 5): 500.16(a)(2)(v). SCF control: Mechanisms exist to facilitate recovery operations in accordance with Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).
  • BCD-24 Data Backups. Intersects with (strength 5): 500.16(a)(2)(v), 500.16(e). SCF control: Mechanisms exist to create recurring backups of data, software and/or system images, as well as verify the integrity of these backups, to ensure the availability of the data to satisfy Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs).
  • IRO-09.1 Incident Response Capabilities Testing Coordination with Related Plans. Intersects with (strength 5): 500.16(d)(1). SCF control: Mechanisms exist to coordinate incident response testing with organizational elements responsible for related plans.
  • BCD-24.3 Cryptographic Protection. Intersects with (strength 5): 500.16(e). SCF control: Cryptographic mechanisms exist to prevent the unauthorized disclosure and/or modification of backup information.
  • BCD-32 Testing for Reliability & Integrity. Intersects with (strength 5): 500.16(e). SCF control: Mechanisms exist to routinely test data backups to verify the reliability of the backup process, as well as the integrity and availability of the data.

The STRM records "no relationship" for the lead-in text of 500.16(d); the numbered paragraphs under it 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.16

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

  • One generic incident playbook. Plans must address the listed areas with respect to different types of cybersecurity events, including disruptive events such as ransomware incidents.
  • BCDR plans that ignore cybersecurity disruptions. The BCDR plan must protect personnel, assets and nonpublic information in the event of a cybersecurity-related disruption, with the six elements in 500.16(a)(2).
  • Testing the plan but not the restore. 500.16(d)(2) separately requires an annual test of the ability to restore critical data and information systems from backups.
  • Backups that ransomware can reach. 500.16(e) requires backups to be adequately protected from unauthorized alterations or destruction.
  • Plans nobody can reach during an outage. 500.16(b) requires current copies to be distributed or otherwise accessible, including during a cybersecurity event.

What Is Reasonable Evidence for 23 NYCRR 500.16?

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.16 include:

  • E-IRO-01 Incident Response Plan (IRP). Documented evidence of a Incident Response Plan (IRP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards.
  • E-BCD-01 Continuity of Operations Plan (COOP). Documented evidence of a Continuity of Operations Plan (COOP). This is program-level documentation in the form of a runbook, playbook or a similar format provides guidance on organizational practices that support existing policies and standards. This involves internal and external stakeholders for incident response, disaster recovery and business continuity support requirements.
  • E-BCD-06 COOP Testing. Documented evidence of a Continuity of Operations Plan (COOP)-related testing activity.
  • E-BCD-07 COOP Training. Documented evidence of a Continuity of Operations Plan (COOP)-related training activity.
  • E-IRO-04 IRP Testing. Documented evidence of an Incident Response Plan (IRP)-related testing activity.
  • E-IRO-05 Table Top Exercises. Documented evidence of "table top" exercises that test incident response practices.
  • E-BCD-10 Data Backups. Documented evidence of a Continuity of Operations Plan (COOP)-related data backup scheme that demonstrates the methods of data backup (including protection measures) for all data types to ensure business continuity requirements.
  • E-BCD-02 Recovery Time Objectives (RTOs). Documented evidence of Recovery Time Objectives (RTOs) that guide Continuity of Operations Plan (COOP)-related operations.

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

  • Incident response plans. Plans covering all nine areas in 500.16(a)(1), with scenario-specific content such as ransomware.
  • BCDR plans. Plans covering all six areas in 500.16(a)(2), including offsite backup procedures and essential third parties.
  • Distribution and training records. Proof that current plans are accessible to and trained for the employees who implement them.
  • Annual test records. Tabletop or exercise reports with all critical staff and management, plan revisions, and backup restoration test results.
  • Backup protection. Immutability, segregation or access controls protecting backups.
  • Root cause analyses. Post-incident reports describing how and why events occurred, business impact and prevention steps.

Which ComplianceForge Documents Support 23 NYCRR 500.16?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.16 Incident Response and Business Continuity Management:

Frequently Asked Questions (FAQ)

What must a 23 NYCRR 500.16 incident response plan include? For different types of cybersecurity events, including ransomware: the goals of the plan; internal response processes; clear roles, responsibilities and decision-making authority; external and internal communications and information sharing; remediation requirements for identified weaknesses; documentation and reporting of events and response activities; recovery from backups; root cause analysis; and updating the plans as necessary.

What must the BCDR plan under 500.16 include? At minimum: identification of documents, data, facilities, infrastructure, services, personnel and competencies essential to continued operations; the supervisory personnel responsible for each part of the plan; a plan to communicate with essential persons; procedures to recover critical data and systems and resume operations; procedures for backing up essential information with sufficient frequency and storing it offsite; and identification of third parties necessary to continued operations.

How often must incident response and BCDR plans be tested under 500.16? Periodically, but at a minimum annually. Testing must include all staff and management critical to the response, and covered entities must also test their ability to restore critical data and information systems from backups.

Do small entities with a limited exemption need to meet 500.16? No. 500.16 is one of the sections waived for entities that qualify for the 500.19(a) limited exemption.

Bottom Line on 23 NYCRR 500.16 Incident Response and Business Continuity Management

500.16 now covers both incident response and business continuity. Build scenario-based incident plans with all nine areas, a BCDR plan with all six, make them reachable during an outage, train the people who use them, test plans and restores every year, and protect backups from tampering.

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.15 Encryption of Nonpublic Information. Next section: 500.17 Notices to Superintendent. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.