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

How Does NY DFS Enforce 23 NYCRR Part 500 Under Section 500.20?

Short Answer

23 NYCRR 500.20 says the superintendent enforces Part 500 under existing authority, that a single prohibited act or failure to meet an obligation is a violation, including a failure to protect nonpublic information due to noncompliance or a material failure to comply with any section for any 24-hour period, and lists 16 factors DFS considers when setting penalties, such as cooperation, good faith, prior violations, consumer harm and alignment with recognized frameworks such as NIST.

23 NYCRR 500.20 Enforcement at a Glance

  • Regulation: NY DFS Cybersecurity Requirements for Financial Services Companies, 23 NYCRR Part 500.
  • Section: 23 NYCRR 500.20 Enforcement.
  • Status: Amended by the Second Amendment, effective November 1, 2023.
  • Who it applies to: Every covered entity.
  • Class A companies: Not applicable.
  • Limited exemption (500.19(a)): Not applicable.
  • Compliance dates: The amended enforcement provisions took effect November 1, 2023 (500.22(e)).

The Second Amendment rewrote 500.20 to say what counts as a violation and how penalties are weighed. A single act or failure is a violation, and two examples are written into the rule: failing to secure or prevent unauthorized access to nonpublic information because of noncompliance, and a material failure to comply with any section for any 24-hour period.

The 16 penalty factors in 500.20(c) reward cooperation, good faith and documented programs, and they explicitly include whether policies and procedures are consistent with nationally recognized cybersecurity frameworks such as NIST.

What Does 23 NYCRR 500.20 Require?

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

  • (a) This regulation will be enforced by the superintendent pursuant to, and is not intended to limit, the superintendent’s authority under any applicable laws.
  • (b) The commission of a single act prohibited by this Part or the failure to act to satisfy an obligation required by this Part shall constitute a violation hereof. Such acts or failures include, without limitation:
  • (1) the failure to secure or prevent unauthorized access to an individual’s or an entity’s nonpublic information due to noncompliance with any section of this Part; or
  • (2) the material failure to comply for any 24-hour period with any section of this Part.
  • (c) In assessing any penalty for a violation of this Part pursuant to the Banking Law, Insurance Law or Financial Services Law, the superintendent shall take into account, without limitation, factors including:
  • (1) the extent to which the covered entity has cooperated with the superintendent in the investigation of such acts;
  • (2) the good faith of the entity;
  • (3) whether the violations resulted from conduct that was unintentional or inadvertent, reckless or intentional and deliberate;
  • (4) whether the violation was a result of failure to remedy previous examination matters requiring attention, or failing to adhere to any disciplinary letter, letter of instructions or similar;
  • (5) any history of prior violations;
  • (6) whether the violation involved an isolated incident, repeat violations, systemic violations or a pattern of violations;
  • (7) whether the covered entity provided false or misleading information;
  • (8) the extent of harm to consumers;
  • (9) whether required, accurate and timely disclosures were made to affected consumers;
  • (10) the gravity of the violations;
  • (11) the number of violations and the length of time over which they occurred;
  • (12) the extent, if any, to which the senior governing body participated therein;
  • (13) any penalty or sanction imposed by any other regulatory agency;
  • (14) the financial resources, net worth and annual business volume of the covered entity and its affiliates;
  • (15) the extent to which the relevant policies and procedures of the company are consistent with nationally recognized cybersecurity frameworks, such as NIST; and
  • (16) such other matters as justice and the public interest require.

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

How Does 23 NYCRR 500.20 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. The STRM records "no relationship" between every paragraph of 23 NYCRR 500.20 and the SCF controls. That fits a section that describes enforcement and violations rather than a control to implement.

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

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

  • Assuming violations need a breach. Under 500.20(b), a single prohibited act or failure to meet an obligation is a violation, and a material failure to comply with any section for any 24-hour period is listed as an example.
  • Unsupported annual filings. Whether the covered entity provided false or misleading information is one of the penalty factors, which makes the support behind the 500.17(b) filing important.
  • Repeat findings. Failure to remedy previous examination matters requiring attention, and history of prior violations, are both penalty factors.
  • No framework alignment. Consistency with nationally recognized frameworks such as NIST is a listed factor. Documented mappings help show it.

What Is Reasonable Evidence for 23 NYCRR 500.20?

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 following are examples of records that typically show 23 NYCRR 500.20 is designed and operating:

  • Examination and remediation history. Prior findings, matters requiring attention and how each was closed.
  • Framework mapping. Documentation showing how policies and procedures align with a recognized framework.
  • Filing support. The records behind each 500.17(b) certification or acknowledgment.
  • Board participation records. Minutes showing senior governing body oversight, a factor under 500.20(c)(12).

Which ComplianceForge Documents Support 23 NYCRR 500.20?

The following ComplianceForge documents can help you document and implement 23 NYCRR 500.20 Enforcement:

  • 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 counts as a violation under 23 NYCRR 500.20? The commission of a single act prohibited by Part 500 or the failure to act to satisfy an obligation it requires. Examples include failing to secure or prevent unauthorized access to nonpublic information due to noncompliance with any section, and the material failure to comply for any 24-hour period with any section.

What factors does NY DFS consider when assessing penalties under 500.20? Sixteen factors, including cooperation, good faith, whether conduct was inadvertent, reckless or intentional, failure to remedy prior examination matters, prior violations, whether violations were isolated or systemic, false or misleading information, consumer harm, consumer disclosures, gravity, number and duration of violations, senior governing body participation, penalties by other regulators, financial resources, consistency with nationally recognized frameworks such as NIST, and other matters justice and the public interest require.

Does using a recognized framework help under 500.20? It is one of the factors. 500.20(c)(15) lists the extent to which the company's policies and procedures are consistent with nationally recognized cybersecurity frameworks, such as NIST.

When did the amended 500.20 take effect? November 1, 2023, under 500.22(e).

Bottom Line on 23 NYCRR 500.20 Enforcement

500.20 makes clear that a single failure, or a material lapse for any 24-hour period, is a violation. Cooperation, documentation, remediation of past findings and alignment with recognized frameworks all weigh in your favor when DFS sets a penalty.

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.19 Exemptions. Next section: 500.22 Transitional Periods. Sections 500.0, 500.18, 500.21, 500.23 and 500.24 are covered in the NY DFS 23 NYCRR Part 500 Compliance Guide.