23 NYCRR 500.4 Cybersecurity Governance at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.4 Cybersecurity Governance.
- 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.4.
- Compliance dates: The new governance requirements applied from November 1, 2024, one year after the Second Amendment took effect (500.22(d)(2)).
Section 500.4 was retitled from Chief Information Security Officer to Cybersecurity Governance in the Second Amendment. It still requires a CISO, but it now also puts specific oversight duties on the senior governing body.
The CISO must report in writing at least annually and must also report material issues to the senior governing body or senior officers in a timely way. If the CISO is outsourced to an affiliate or a third-party service provider, the covered entity keeps responsibility for compliance and must designate a senior person to direct and oversee that provider.
What Does 23 NYCRR 500.4 Require?
The following is the text of 23 NYCRR 500.4 Cybersecurity Governance as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.
- (a) Chief information security officer. Each covered entity shall designate a CISO. The CISO may be employed by the covered entity, one of its affiliates or a third-party service provider. If the CISO is employed by a third-party service provider or an affiliate, the covered entity shall:
- (1) retain responsibility for compliance with this Part;
- (2) designate a senior member of the covered entity’s personnel responsible for direction and oversight of the third-party service provider; and
- (3) require the third-party service provider or affiliate to maintain a cybersecurity program that protects the covered entity in accordance with the requirements of this Part.
- (b) Report. The CISO of each covered entity shall report in writing at least annually to the senior governing body on the covered entity’s cybersecurity program, including to the extent applicable:
- (1) the confidentiality of nonpublic information and the integrity and security of the covered entity’s information systems;
- (2) the covered entity’s cybersecurity policies and procedures;
- (3) material cybersecurity risks to the covered entity;
- (4) overall effectiveness of the covered entity’s cybersecurity program;
- (5) material cybersecurity events involving the covered entity during the time period addressed by the report; and
- (6) plans for remediating material inadequacies.
- (c) The CISO shall timely report to the senior governing body or senior officer(s) on material cybersecurity issues, such as significant cybersecurity events and significant changes to the covered entity’s cybersecurity program.
- (d) The senior governing body of the covered entity shall exercise oversight of the covered entity’s cybersecurity risk management, including by:
- (1) having sufficient understanding of cybersecurity-related matters to exercise such oversight, which may include the use of advisors;
- (2) requiring the covered entity’s executive management or its designees to develop, implement and maintain the covered entity’s cybersecurity program;
- (3) regularly receiving and reviewing management reports about cybersecurity matters; and
- (4) confirming that the covered entity’s management has allocated sufficient resources to implement and maintain an effective cybersecurity program.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.4 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.4 to 18 SCF controls through 47 relationships (10 "subset of", 37 "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.
- TPM-02 Third-Party Management. Subset of (strength 10): 500.4(a)(1), 500.4(a)(2), 500.4(a)(3). SCF control: Mechanisms exist to facilitate the implementation of third-party management controls.
- GOV-09 Steering Committee & Program Oversight. Subset of (strength 10): 500.4(d), 500.4(d)(1), 500.4(d)(2), 500.4(d)(3), 500.4(d)(4). Intersects with (strength 5): 500.4(b), 500.4(b)(1), 500.4(b)(2), 500.4(b)(3), 500.4(b)(4), 500.4(b)(5), 500.4(b)(6). SCF control: Mechanisms exist to align security, compliance and resilience capabilities with business requirements through a steering committee or advisory board, comprised of key cybersecurity, data protection and business executives, which meets formally and on a regular basis.
- GOV-09.1 Status Reporting To Governing Body. Subset of (strength 10): 500.4(c). Intersects with (strength 5): 500.4(b). SCF control: Mechanisms exist to provide governance oversight reporting and recommendations enabling executives to make decisions about matters considered material to the organization's Security, Compliance & Resilience Program (SCRP).
- PRM-05 Security, Compliance & Resilience Resource Management. Subset of (strength 10): 500.4(d)(4). SCF control: Mechanisms exist to address all capital planning and investment requests, including the resources needed to implement the Security, Compliance & Resilience Program (SCRP) and document all exceptions.
- GOV-05 Assigned Security, Compliance & Resilience Responsibilities. Intersects with (strength 5): 500.4(a). SCF control: Mechanisms exist to assign one or more qualified individuals with the mission and resources to centrally-manage, coordinate, develop, implement and maintain an enterprise-wide Security, Compliance & Resilience Program (SCRP).
- TPM-11 Responsible, Accountable, Supportive, Consulted & Informed (RASCI) Matrix. Intersects with (strength 5): 500.4(a)(1), 500.4(a)(2), 500.4(a)(3). 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-21.1 Security Compromise Notification Agreements. Intersects with (strength 5): 500.4(a)(1), 500.4(a)(2), 500.4(a)(3). SCF control: Mechanisms exist to compel External Service Providers (ESPs) to provide notification of actual or potential compromises in the supply chain that can potentially affect or have adversely affected Technology Assets, Applications and/or Services (TAAS) that the organization utilizes.
- GOV-05.1 Stakeholder Accountability Structure. Intersects with (strength 5): 500.4(b), 500.4(b)(6). SCF control: Mechanisms exist to enforce an accountability structure so that appropriate teams and individuals are empowered, responsible and trained for identifying, mapping, measuring and managing Technology Assets, Applications, Services and/or Data (TAASD)-related risks.
- GOV-05.2 Authoritative Chain of Command. Intersects with (strength 5): 500.4(b). SCF control: Mechanisms exist to establish an authoritative chain of command with clear lines of communication to remove ambiguity for individuals and teams managing Technology Assets, Applications, Services and/or Data (TAASD)-related risks.
- GOV-07 Materiality Determination. Intersects with (strength 5): 500.4(b), 500.4(b)(3), 500.4(b)(5). SCF control: Mechanisms exist to define materiality threshold criteria capable of designating an incident as material.
- RSK-06 Material Risks. Intersects with (strength 5): 500.4(b), 500.4(b)(3), 500.4(b)(5). SCF control: Mechanisms exist to define criteria necessary to designate a risk as a material risk.
- THR-07 Material Threats. Intersects with (strength 5): 500.4(b), 500.4(b)(3), 500.4(b)(5). SCF control: Mechanisms exist to define criteria necessary to designate a threat as a material threat.
- TPM-22 First-Party Declaration (1PD). Intersects with (strength 5): 500.4(b)(1), 500.4(b)(2), 500.4(b)(3), 500.4(b)(4), 500.4(b)(5). SCF control: Mechanisms exist to obtain a First-Party Declaration(1PD) from applicable External Service Providers (ESPs) that provides assurance of compliance with specified statutory, regulatory and contractual obligations for security, compliance and resilience controls, including any flow-down requirements to subcontractors.
- CPL-06 Non-Conformity Oversight. Intersects with (strength 5): 500.4(b)(6). SCF control: Mechanisms exist to identify and document instances of non-conformity with statutory, regulatory and/or contractual obligations, in order to develop appropriate risk mitigation actions.
- RSK-17 Risk Remediation. Intersects with (strength 5): 500.4(b)(6). SCF control: Mechanisms exist to remediate risks to an acceptable level.
- TPM-18 Third-Party Deficiency Remediation. Intersects with (strength 5): 500.4(b)(6). SCF control: Mechanisms exist to address weaknesses or deficiencies in supply chain elements identified during independent or organizational assessments of such elements.
- VPM-06 Vulnerability Remediation Process. Intersects with (strength 5): 500.4(b)(6). SCF control: Mechanisms exist to ensure that vulnerabilities are properly identified, tracked and remediated.
- PRM-06 Allocation of Resources. Intersects with (strength 5): 500.4(d)(4). SCF control: Mechanisms exist to identify and allocate resources for management, operational, technical and data protection requirements within business process planning for projects / initiatives.
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.4
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- An annual report that skips required topics. The report must cover, to the extent applicable, the six topics in 500.4(b), including plans for remediating material inadequacies.
- No timely reporting between annual reports. 500.4(c) requires the CISO to report material cybersecurity issues, such as significant events and significant program changes, as they arise.
- Board oversight on paper only. 500.4(d) expects the senior governing body to have sufficient understanding, receive and review management reports regularly, and confirm management has allocated sufficient resources. Minutes should show this happening.
- Virtual CISO without an internal owner. Where a third-party service provider or affiliate provides the CISO, 500.4(a)(2) requires a senior member of the covered entity's personnel to direct and oversee that provider.
What Is Reasonable Evidence for 23 NYCRR 500.4?
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.4 include:
- E-HRS-05 Role Assignment - CISO. Documented evidence of a formal role assignment to the Chief Information Security Officer (CISO) position.
- E-GOV-09 Charter - Cybersecurity Steering Committee. Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of cybersecurity management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.
- E-GOV-11 Charter - Audit Committee. Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of internal and external audit management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.
- E-GOV-12 Charter - Risk Committee. Documented evidence of an executive steering committee, or advisory board, that is formed to perform oversight of risk management decisions and is comprised of key cybersecurity, technology, risk, privacy and business executives.
- E-CPL-09 Non-Compliance Oversight Reporting. Documented evidence of governance oversight reporting of non-compliance to the organization's executive leadership.
- E-GOV-16 Material Risks. Documented evidence of specific risks that are categorized as material risks.
- E-PRM-02 Portfolio Roadmap. Documented evidence of the organization's roadmap for implementing cybersecurity-related initiatives and technologies.
- E-HRS-15 Organization Chart. Current and accurate organization chart that depicts logical staff hierarchies.
Records specific to 23 NYCRR 500.4 that typically show the requirement is designed and operating:
- CISO designation. A dated designation of the CISO and, if outsourced, the contract and the internal person responsible for oversight.
- Annual CISO report. The written report to the senior governing body covering each topic in 500.4(b).
- Board or committee minutes. Records showing the senior governing body received and discussed cybersecurity reports and resource adequacy.
- Interim escalations. Records of timely reports on significant events or program changes under 500.4(c).
- Board cybersecurity education or advisors. Records supporting the sufficient understanding expected by 500.4(d)(1).
Which ComplianceForge Documents Support 23 NYCRR 500.4?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.4 Cybersecurity Governance:
Frequently Asked Questions (FAQ)
Does 23 NYCRR 500.4 require a full-time, in-house CISO? No. The CISO may be employed by the covered entity, one of its affiliates or a third-party service provider. If the CISO is not employed by the covered entity, the covered entity retains responsibility for compliance, must designate a senior member of its personnel to direct and oversee the provider, and must require the provider or affiliate to maintain a cybersecurity program that protects the covered entity under Part 500.
What must the annual CISO report under 500.4(b) include? To the extent applicable: the confidentiality of nonpublic information and the integrity and security of information systems; cybersecurity policies and procedures; material cybersecurity risks; overall effectiveness of the program; material cybersecurity events during the period; and plans for remediating material inadequacies.
What oversight does 500.4(d) require from the board? The senior governing body must exercise oversight of cybersecurity risk management, including having sufficient understanding of cybersecurity matters (which may include advisors), requiring executive management to develop, implement and maintain the program, regularly receiving and reviewing management reports, and confirming management has allocated sufficient resources.
Is a small entity with a limited exemption required to have a CISO? No. 500.4 is one of the sections waived for entities that qualify for the 500.19(a) limited exemption.
Bottom Line on 23 NYCRR 500.4 Cybersecurity Governance
500.4 turns cybersecurity into a governance obligation, not just a CISO title. Designate the CISO, make the annual report cover every 500.4(b) topic, escalate material issues between reports, and make sure board minutes show real oversight and resource decisions.
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.3 Cybersecurity Policy. Next section: 500.5 Vulnerability Management. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.