23 NYCRR 500.3 Cybersecurity Policy at a Glance
- Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
- Section: 23 NYCRR 500.3 Cybersecurity Policy.
- 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).
- Class A companies: None beyond the general requirement.
- 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.3.
- Compliance dates: Written policies have been required since 2017. The new policy areas added by the Second Amendment, such as vulnerability management and end of life management, applied from April 29, 2024 (500.22(c)).
Section 500.3 is where most Part 500 documentation starts. It requires written policies approved at least annually, and since the Second Amendment it also says procedures must be developed, documented and implemented in accordance with those policies.
The 15 areas in 500.3(a) to (o) are a minimum list, applied to the extent relevant to your operations. The Second Amendment added retention to data governance, device and end of life management to asset inventory, security awareness and training, notification to incident response, and vulnerability management as a new area.
What Does 23 NYCRR 500.3 Require?
The following is the text of 23 NYCRR 500.3 Cybersecurity Policy as amended by the Second Amendment to Part 500, effective November 1, 2023. Only the formatting has been adjusted for readability.
- Each covered entity shall implement and maintain a written policy or policies, approved at least annually by a senior officer or the covered entity’s senior governing body for the protection of its information systems and nonpublic information stored on those information systems. Procedures shall be developed, documented and implemented in accordance with the written policy or policies. The cybersecurity policy or policies and procedures shall be based on the covered entity’s risk assessment and address, at a minimum, the following areas to the extent applicable to the covered entity’s operations:
- (a) information security;
- (b) data governance, classification and retention;
- (c) asset inventory, device management and end of life management;
- (d) access controls, including remote access and identity management;
- (e) business continuity and disaster recovery planning and resources;
- (f) systems operations and availability concerns;
- (g) systems and network security and monitoring;
- (h) security awareness and training;
- (i) systems and application security and development and quality assurance;
- (j) physical security and environmental controls;
- (k) customer data privacy;
- (l) vendor and third-party service provider management;
- (m) risk assessment;
- (n) incident response and notification; and
- (o) vulnerability management.
Source: NY DFS, Second Amendment to 23 NYCRR 500 (text).
How Does 23 NYCRR 500.3 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.3 to 18 SCF controls through 33 relationships (15 "subset of", 18 "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-04 Publishing Security, Compliance & Resilience Documentation. Subset of (strength 10): 500.3(a), 500.3(b), 500.3(c), 500.3(d), 500.3(e), 500.3(f), 500.3(g), 500.3(h), 500.3(i), 500.3(j), 500.3(k), 500.3(l), 500.3(m), 500.3(n), 500.3(o). Intersects with (strength 8): 500.3. 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 8): 500.3. 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.
- GOV-02 Security, Compliance & Resilience Program (SCRP). Intersects with (strength 5): 500.3(a). SCF control: Mechanisms exist to facilitate the design, implementation, and monitoring of security, compliance and resilience governance controls.
- DCH-02 Data Protection. Intersects with (strength 5): 500.3(b). SCF control: Mechanisms exist to facilitate the implementation of data protection controls.
- AST-02 Asset Governance. Intersects with (strength 5): 500.3(c). SCF control: Mechanisms exist to facilitate an IT Asset Management (ITAM) program to implement and manage asset management controls.
- IAC-02 Identity & Access Management (IAM). Intersects with (strength 5): 500.3(d). SCF control: Mechanisms exist to facilitate the implementation of Identification and Access Management (IAM) controls.
- BCD-02 Business Continuity Management System (BCMS). Intersects with (strength 5): 500.3(e). 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.
- CAP-02 Capacity & Performance Management. Intersects with (strength 5): 500.3(f). SCF control: Mechanisms exist to facilitate the implementation of capacity management controls to ensure optimal system performance to meet expected and anticipated future capacity requirements.
- NET-02 Network Security Controls (NSC). Intersects with (strength 5): 500.3(g). SCF control: Mechanisms exist to develop, govern & update procedures to facilitate the implementation of Network Security Controls (NSC).
- SAT-02 Security, Compliance & Resilience-Minded Workforce. Intersects with (strength 5): 500.3(h). SCF control: Mechanisms exist to facilitate the implementation of security workforce development and awareness controls.
- TDA-02 Technology Development & Acquisition. Intersects with (strength 5): 500.3(i). SCF control: Mechanisms exist to facilitate the implementation of tailored development and acquisition strategies, contract tools and procurement methods to meet unique business needs.
- PES-02 Physical & Environmental Protections. Intersects with (strength 5): 500.3(j). SCF control: Mechanisms exist to facilitate the operation of physical and environmental protection controls.
- PRI-02 Data Privacy Program. Intersects with (strength 5): 500.3(k). SCF control: Mechanisms exist to facilitate the implementation and operation of data protection controls throughout the data lifecycle to ensure all forms of Personal Data (PD) are processed lawfully, fairly and transparently.
- TPM-01 Third-Party Management Policy. Intersects with (strength 5): 500.3(l). SCF control: Mechanisms exist to establish a formal, documented third-party management policy that: (1) Conveys executive management's intent; (2) Provides organizational direction and expected behaviors; (3) Is reviewed at least annually; and (4) Is updated, as necessary, to adapt to evolving risks, threats and other changes that affect the organization.
- TPM-02 Third-Party Management. Intersects with (strength 5): 500.3(l). SCF control: Mechanisms exist to facilitate the implementation of third-party management controls.
- RSK-02 Risk Management Program. Intersects with (strength 5): 500.3(m). 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.
- IRO-02 Incident Response Operations. Intersects with (strength 5): 500.3(n). 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.
- VPM-02 Vulnerability & Patch Management Program (VPMP). Intersects with (strength 5): 500.3(o). SCF control: Mechanisms exist to facilitate the implementation and monitoring of risk-based vulnerability management capabilities.
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.3
The following are issues teams commonly run into, not certainties. Each one is tied to the text of the regulation:
- Policies without procedures. 500.3 now says procedures shall be developed, documented and implemented in accordance with the written policies. A policy set with no supporting procedures leaves that sentence unmet.
- Missing the annual approval. Approval must happen at least annually by a senior officer or the senior governing body. An approval record with a date is the simplest proof.
- Using the pre-2023 list of areas. Older policy sets often lack vulnerability management, end of life management, data retention, security awareness and training, and notification.
- Generic policies with no risk link. The policies must be based on the risk assessment, so the policy set should reflect the risks your 500.9 assessment identified.
What Is Reasonable Evidence for 23 NYCRR 500.3?
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.3 include:
- E-GOV-01 Security, Compliance & Resilience Policies. Documented evidence of an appropriately-scoped security, compliance and resilience-focued policies. Policies are high-level statements of management intent from an organization's executive leadership that are designed to influence decisions and guide the organization to achieve the desired outcomes. Policies are enforced by standards and further implemented by procedures to establish actionable and accountable requirements.
- E-GOV-04 Cybersecurity & Data Protection Procedures. Documented evidence of an appropriate appropriately-scoped cybersecurity & data protection procedures. Procedures are a documented set of steps necessary to perform a specific task or process in conformance with an applicable standard. Procedures help address the question of how the organization actually operationalizes a policy, standard or control. The result of a procedure is intended to satisfy a specific control. Procedures are also commonly referred to as “control activities.”
- E-GOV-02 Cybersecurity & Data Protection Standards. Documented evidence of an appropriately-scoped cybersecurity & data protection standards. Standards are mandatory requirements regarding processes, actions and configurations. Standards are intended to be granular and prescriptive to ensure Technology Assets, Applications and/or Services (TAAS) are designed and operated to include appropriate cybersecurity & data protection protections
- E-AST-01 IT Asset Management (ITAM). Documented evidence of an IT Asset Management (ITAM) program that addresses the due diligence and due care activities associated with maintaining both secure, compliance and resilient Technology Assets, Applications and/or Services (TAAS).
- 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-CAP-01 Capacity Planning. Documented evidence of proactive capacity planning to meet expected and anticipated future technology-related capacity and/or performance requirements.
- E-DCH-02 Data Handling Practices. Documented evidence of an organization-specific data handling practices (e.g., guidance specific the data classification scheme).
- E-GOV-07 Charter - Cybersecurity Program. Documented evidence of a charter to establish and resource the organization's cybersecurity program.
Records specific to 23 NYCRR 500.3 that typically show the requirement is designed and operating:
- Approved policy set. Policies covering each applicable area in 500.3(a) to (o), with version history.
- Annual approval record. Minutes or a signed approval by a senior officer or the senior governing body, dated within the last year.
- Procedures mapped to policies. Documented procedures showing how each policy is carried out.
- Coverage matrix. A table mapping each of the 15 areas to the policy and procedure that addresses it, or a note on why an area does not apply.
Which ComplianceForge Documents Support 23 NYCRR 500.3?
The following ComplianceForge documents can help you document and implement 23 NYCRR 500.3 Cybersecurity Policy:
- SCF Policies & Standards (SCRP): editable SCF-based cybersecurity policies, standards and control objectives covering all 34 SCF domains.
- SCF Procedures (CSOP): editable SCF-aligned cybersecurity procedures covering all 34 SCF domains, mapped 1-to-1 to the SCRP standards.
Frequently Asked Questions (FAQ)
What areas must a 23 NYCRR 500.3 cybersecurity policy cover? To the extent applicable: information security; data governance, classification and retention; asset inventory, device management and end of life management; access controls, including remote access and identity management; business continuity and disaster recovery; systems operations and availability; systems and network security and monitoring; security awareness and training; systems and application security and development and quality assurance; physical security and environmental controls; customer data privacy; vendor and third-party service provider management; risk assessment; incident response and notification; and vulnerability management.
Who must approve the cybersecurity policy under 500.3? A senior officer or the covered entity's senior governing body, at least annually.
Does 500.3 require written procedures as well as policies? Yes. The amended text says procedures shall be developed, documented and implemented in accordance with the written policy or policies.
Do entities with a limited exemption still need a written cybersecurity policy? Yes. 500.3 is not on the list of sections waived by the 500.19(a) limited exemption. Only entities exempt under 500.19(c) or (d) are exempt from 500.3.
Bottom Line on 23 NYCRR 500.3 Cybersecurity Policy
500.3 asks for a risk-based policy set approved every year and backed by procedures that are actually in use. Check your policies against all 15 areas, add the ones the Second Amendment introduced, and keep a dated approval record for the annual filing.
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.2 Cybersecurity Program. Next section: 500.4 Cybersecurity Governance. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.