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.2 Cybersecurity Program?

Short Answer

23 NYCRR 500.2 requires every covered entity to maintain a risk-based cybersecurity program that protects the confidentiality, integrity and availability of its information systems and nonpublic information and performs six core functions: identify, protect, detect, respond, recover and meet regulatory reporting obligations. Class A companies must also conduct independent audits of the program, and all program documentation must be available to DFS on request.

23 NYCRR 500.2 Cybersecurity Program at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.2 Cybersecurity Program.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity unless exempt under 500.19(c) or (d). Entities with a 500.19(a) limited exemption still need a cybersecurity program.
  • Class A companies: 500.2(c): Class A companies must design and conduct independent audits of the cybersecurity program based on the risk assessment.
  • Limited exemption (500.19(a)): Not exempt under 500.19(a). Entities exempt under 500.19(c) or (d) do not need to meet 500.2.
  • Compliance dates: The core program requirement has applied since 2017. The new Class A independent audit requirement in 500.2(c) applied from April 29, 2024, 180 days after the Second Amendment took effect on November 1, 2023 (500.22(c)).

Section 500.2 is the umbrella requirement. Every other section describes part of the cybersecurity program that 500.2 says you must have, and the program has to be based on the risk assessment required by 500.9.

The six core functions in 500.2(b) read like the NIST Cybersecurity Framework functions, plus a sixth function for regulatory reporting. Class A companies picked up an independent audit requirement in the Second Amendment, and 500.2(d) still lets a covered entity adopt an affiliate's program as long as it meets Part 500 for that entity.

What Does 23 NYCRR 500.2 Require?

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

  • (a) Each covered entity shall maintain a cybersecurity program designed to protect the confidentiality, integrity and availability of the covered entity’s information systems and nonpublic information stored on those information systems.
  • (b) The cybersecurity program shall be based on the covered entity’s risk assessment and designed to perform the following core cybersecurity functions:
  • (1) identify and assess internal and external cybersecurity risks that may threaten the security or integrity of nonpublic information stored on the covered entity’s information systems;
  • (2) use defensive infrastructure and the implementation of policies and procedures to protect the covered entity’s information systems, and the nonpublic information stored on those information systems, from unauthorized access, use or other malicious acts;
  • (3) detect cybersecurity events;
  • (4) respond to identified or detected cybersecurity events to mitigate any negative effects;
  • (5) recover from cybersecurity events and restore normal operations and services; and
  • (6) fulfill applicable regulatory reporting obligations.
  • (c) Each class A company shall design and conduct independent audits of its cybersecurity program based on its risk assessment.
  • (d) A covered entity may meet the requirement(s) of this Part by adopting the relevant and applicable provisions of a cybersecurity program maintained by an affiliate, provided that such provisions satisfy the requirements of this Part, as applicable to the covered entity.
  • (e) All documentation and information relevant to the covered entity’s cybersecurity program, including the relevant and applicable provisions of a cybersecurity program maintained by an affiliate and adopted by the covered entity, shall be made available to the superintendent upon request.

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

How Does 23 NYCRR 500.2 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.2 to 20 SCF controls through 31 relationships (20 "subset of", 11 "intersects with").

How to read the mapping: each relationship runs from the Part 500 text to the SCF control. "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.

  • GOV-02 Security, Compliance & Resilience Program (SCRP). Subset of (strength 10): 500.2(a), 500.2(b), 500.2(b)(1), 500.2(b)(2), 500.2(b)(3), 500.2(b)(4), 500.2(b)(5), 500.2(b)(6), 500.2(d), 500.2(e). SCF control: Mechanisms exist to facilitate the design, implementation, and monitoring of security, compliance and resilience governance controls.
  • RSK-02 Risk Management Program. Subset of (strength 10): 500.2(b)(1). SCF control: Mechanisms exist to facilitate the implementation of strategic, operational and tactical risk management controls that are aligned with: (1) The organization's Enterprise Risk Management (ERM); and (2) Industry-recognized cybersecurity risk management practices.
  • SEA-04 Alignment With Enterprise Architecture. Subset of (strength 10): 500.2(b)(2). SCF control: Mechanisms exist to develop an enterprise architecture, aligned with industry-recognized leading practices, with consideration for security, compliance and resilience principles that addresses risk to organizational operations, assets, individuals and other organizations.
  • SEA-05 Secure Engineering Principles. Subset of (strength 10): 500.2(b)(2). SCF control: Mechanisms exist to facilitate the implementation of industry-recognized security, compliance and resilience practices in the specification, design, development, implementation and modification of Technology Assets, Applications and/or Services (TAAS).
  • MON-02 Continuous Monitoring. Subset of (strength 10): 500.2(b)(3). SCF control: Mechanisms exist to facilitate the implementation of enterprise-wide monitoring controls.
  • IRO-02 Incident Response Operations. Subset of (strength 10): 500.2(b)(4). 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.
  • BCD-02 Business Continuity Management System (BCMS). Subset of (strength 10): 500.2(b)(5). 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.
  • CPL-02 Statutory, Regulatory & Contractual Compliance. Subset of (strength 10): 500.2(b)(6), 500.2(e). Intersects with (strength 5): 500.2(d). SCF control: Mechanisms exist to facilitate the identification and implementation of relevant statutory, regulatory and contractual controls.
  • CPL-05 Conformity Monitoring. Subset of (strength 10): 500.2(c). Applies to Class A companies. SCF control: Mechanisms exist to validate that Technology Assets, Applications, Services and/or Data (TAASD) conform to the organization's security, compliance and/or resilience policies, standards and other applicable requirements.
  • CPL-08 Independent Assessors. Subset of (strength 10): 500.2(c). Applies to Class A companies. SCF control: Mechanisms exist to utilize independent assessors to evaluate security, compliance and resilience at planned intervals or when the Technology Asset, Application and/or Service (TAAS) undergoes significant changes.
  • RSK-09 Risk Identification. Intersects with (strength 5): 500.2(b)(1). SCF control: Mechanisms exist to identify and document risks, both internal and external.
  • RSK-13 Risk Assessment. Intersects with (strength 5): 500.2(b)(1). SCF control: Mechanisms exist to conduct recurring assessments of risk that includes the likelihood and magnitude of harm, from unauthorized access, use, disclosure, disruption, modification or destruction of the organization's Technology Assets, Applications, Services and/or Data (TAASD).
  • GOV-04 Publishing Security, Compliance & Resilience Documentation. Intersects with (strength 5): 500.2(b)(2). SCF control: Mechanisms exist to establish, maintain and disseminate policies, standards and procedures necessary for secure, compliant and resilient capabilities.
  • OPS-04 Standardized Operating Procedures (SOP). Intersects with (strength 5): 500.2(b)(2). SCF control: Mechanisms exist to identify and document Standardized Operating Procedures (SOP), or similar documentation, to enable the proper execution of day-to-day / assigned tasks.
  • SEA-06 Defense-In-Depth (DiD) Architecture. Intersects with (strength 5): 500.2(b)(2). SCF control: Mechanisms exist to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.
  • TPM-05.1 Outsourcing Non-Essential Functions or Services. Intersects with (strength 5): 500.2(d). SCF control: Mechanisms exist to identify non-essential functions or services that are capable of being outsourced to external service providers and align with the organization's enterprise architecture and security standards.
  • TPM-11 Responsible, Accountable, Supportive, Consulted & Informed (RASCI) Matrix. Intersects with (strength 5): 500.2(d). SCF control: Mechanisms exist to document and maintain a Responsible, Accountable, Supportive, Consulted & Informed (RASCI) matrix, or similar documentation, to delineate assignment for security, compliance and resilience controls between internal stakeholders and External Service Providers (ESPs).
  • TPM-14 Third-Party Contract Requirements. Intersects with (strength 5): 500.2(d). SCF control: Mechanisms exist to require contractual requirements for applicable security, compliance and resilience requirements with third-parties, reflecting the organization's needs to protect its Technology Assets, Applications, Services and/or Data (TAASD).
  • CPL-19 Legal Assessment of Investigative Inquires. Intersects with (strength 5): 500.2(e). 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.2(e). 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.

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.2

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

  • A program that is not tied to the risk assessment. 500.2(b) requires the program to be based on the risk assessment. A program built from a generic framework without a documented link to 500.9 results is hard to defend in an examination.
  • Forgetting the reporting function. The sixth core function in 500.2(b)(6) is fulfilling regulatory reporting obligations, which connects the program to the 500.17 notices and the April 15 filing.
  • Treating the Class A audit as a one-time project. 500.2(c) requires independent audits designed around the risk assessment. The auditors must be free of influence from the covered entity, its owners, managers or employees, as defined in 500.1(h).
  • Adopting an affiliate program without checking the fit. 500.2(d) allows it only where the adopted provisions satisfy Part 500 as applicable to the covered entity, and 500.2(e) requires that documentation to be available to DFS.

What Is Reasonable Evidence for 23 NYCRR 500.2?

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

  • E-GOV-01.1 Security, Compliance & Resilience Governance Policy. Documented evidence of a security, compliance and resilience governance policy.
  • E-SEA-02 Security Architecture. Documented evidence of security architecture-related documentation.
  • E-CPL-07 Control Assessments. Documented evidence of internal or third-party control assessments to provide governance oversight of cybersecurity & data privacy controls.
  • 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-CPL-01 Statutory, Regulatory & Contractual Obligations. Documented evidence of applicable statutory, regulatory and/or contractual obligations for cybersecurity & data privacy controls.
  • E-CPL-05 Internal Audit (IA) Findings. Documented evidence of a centrally-managed and prioritized repository Internal Audit (IA) findings.
  • E-GOV-07 Charter - Cybersecurity Program. Documented evidence of a charter to establish and resource the organization's cybersecurity program.
  • 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.

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

  • Program charter or description. A document showing how the program covers each of the six core functions in 500.2(b).
  • Link to the risk assessment. Records showing how 500.9 risk assessment results shaped program priorities.
  • Independent audit reports (Class A). Audit scope, auditor independence, findings and management responses.
  • Affiliate program adoption records. Where an affiliate program is used, the provisions adopted and how they apply to the covered entity.
  • Document index. An index of program documentation that can be produced to DFS on request under 500.2(e).

Which ComplianceForge Documents Support 23 NYCRR 500.2?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.2 Cybersecurity Program:

Frequently Asked Questions (FAQ)

What are the six core cybersecurity functions in 23 NYCRR 500.2? Identify and assess internal and external cybersecurity risks; protect information systems and nonpublic information with defensive infrastructure, policies and procedures; detect cybersecurity events; respond to detected events to mitigate negative effects; recover and restore normal operations and services; and fulfill applicable regulatory reporting obligations.

Who must conduct independent audits under 500.2(c)? Class A companies, as defined in 500.1(d). They must design and conduct independent audits of the cybersecurity program based on the risk assessment. Independent audit is defined in 500.1(h) as an audit by internal or external auditors free to make decisions not influenced by the covered entity or its owners, managers or employees.

Can a covered entity use an affiliate's cybersecurity program? Yes. Under 500.2(d), a covered entity may meet Part 500 by adopting the relevant and applicable provisions of an affiliate's cybersecurity program, provided those provisions satisfy Part 500 as applicable to the covered entity.

Does a limited exemption under 500.19(a) remove the 500.2 requirement? No. The 500.19(a) limited exemption does not list 500.2, so those entities still need a cybersecurity program. Only entities exempt under 500.19(c) or (d) are exempt from 500.2.

Bottom Line on 23 NYCRR 500.2 Cybersecurity Program

500.2 is the requirement every other section rolls up to. Document a risk-based program that covers all six core functions, keep the documentation ready for DFS, and, if you are a Class A company, plan independent audits that follow your risk assessment.

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.1 Definitions. Next section: 500.3 Cybersecurity Policy. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.