NYDFS Part 500 after the 2023 second amendment: what changed and when each part applied

New York’s financial regulator amended its cybersecurity rule effective November 1, 2023, adding Class A companies, board oversight, near-universal MFA, asset inventories and extortion-payment notices, and phased the new duties in over 30 days to two years.

The New York State Department of Financial Services (DFS) adopted a second amendment to its cybersecurity regulation, 23 NYCRR Part 500. The Notice of Adoption, published in the State Register of November 1, 2023, gives a filing date of October 16, 2023 and an effective date of November 1, 2023, and summarizes each change section by section [2]. For the regulation text we used the PDF that DFS publishes at the address listed as source 1, retrieved on November 14, 2026. Its first page says it is not an official version of the amendment and is meant to help regulated persons identify the textual changes [1]. Section numbers below follow that text.

Who is covered, and the new Class A tier

A covered entity is any person operating under, or required to operate under, a license, registration, charter, certificate, permit, accreditation or similar authorization under the Banking Law, the Insurance Law or the Financial Services Law, even if another government agency also regulates it [1].

The amendment added a defined category, the Class A company, which the Notice describes as larger, more complex and better-resourced entities that must apply additional controls [2]. A covered entity is Class A if it had at least $20,000,000 in gross annual revenue in each of the last two fiscal years from its own business and the New York business of its affiliates, and either:

  • over 2,000 employees averaged over the last two fiscal years, counting the entity and all affiliates wherever located; or
  • over $1,000,000,000 in gross annual revenue in each of the last two fiscal years from all business of the entity and all its affiliates wherever located [1].

For these counts, only affiliates that share information systems, cybersecurity resources or any part of a cybersecurity program with the covered entity are included [1].

At the other end, the amendment widened the limited exemption. An entity qualifies if it has fewer than 20 employees and independent contractors (with its affiliates), less than $7,500,000 in gross annual revenue in each of the last three fiscal years, or less than $15,000,000 in year-end total assets [1]. A qualifying entity is exempt from sections 500.4, 500.5, 500.6, 500.8, 500.10, 500.14(a)(1), (a)(2) and (b), 500.15 and 500.16; the Notice states that multi-factor authentication (500.12) and annual awareness training (500.14(a)(3)) are not exempted [1] [2].

Governance: the CISO and the senior governing body

The amendment moved the definition of the Chief Information Security Officer into section 500.1 and added a definition of the senior governing body: the board of directors, an appropriate committee, an equivalent body or, where none exists, the senior officers responsible for the program [1] [2]. The changes to section 500.4 require that:

  • the CISO’s annual written report to the senior governing body include plans for remediating material inadequacies;
  • the CISO report in a timely way on material cybersecurity issues, such as significant cybersecurity events and significant changes to the program;
  • the senior governing body exercise oversight of cybersecurity risk management, including having sufficient understanding of cybersecurity matters (which may include advisors), regularly receiving management reports, and confirming that management has allocated sufficient resources [1] [2].

Cybersecurity policies must now be approved at least annually by a senior officer or the senior governing body, and the list of topics they must cover gained data retention, end-of-life management, remote access, systems monitoring, security awareness and training, application security, incident notification and vulnerability management [2]. Risk assessments must be reviewed and updated at least annually and whenever a business or technology change materially changes cyber risk, and Class A companies must design and conduct independent audits of their programs [2].

Technical controls added or tightened

  • Vulnerability management (500.5). Written policies and procedures; penetration testing from inside and outside system boundaries at least annually; automated scans, with manual review of systems the scans miss, at a risk-based frequency and promptly after material changes; a monitoring process for new vulnerabilities; and risk-prioritized remediation. The Notice states that the amendment removed the option to substitute continuous monitoring for testing [1] [2].
  • Access privileges (500.7). Least-privilege access, fewer and narrower privileged accounts, at least annual access reviews, disabling or securely configuring remote-control protocols, prompt removal of access after departures, and a written password policy. Class A companies must also monitor privileged access activity, run a privileged access management solution and automatically block commonly used passwords [1].
  • Multi-factor authentication (500.12). Required for any individual accessing any information system. An entity with the limited exemption must still use it for remote access to its information systems, for remote access to third-party applications from which nonpublic information is accessible, and for all privileged accounts other than service accounts that prohibit interactive login. A CISO may approve equivalent or more secure compensating controls in writing, reviewed at least annually [1].
  • Asset inventory (500.13(a)). Written policies and procedures for a complete, documented inventory that tracks, as applicable, each asset’s owner, location, classification, support expiration date and recovery time objective, and sets how often the inventory is updated and validated [1].
  • Monitoring and training (500.14). Controls against malicious code, including web and email filtering, and at least annual awareness training that includes social engineering. Class A companies must run endpoint detection and response and a solution that centralizes logging and security event alerting, unless the CISO approves compensating controls in writing [1].
  • Encryption (500.15). A written policy requiring encryption that meets industry standards, in transit over external networks and at rest. The Notice states that the option of compensating controls for data in transit was removed; for data at rest, compensating controls need the CISO’s written approval and an annual review [1] [2].
  • Incident response and business continuity (500.16). Written incident response, business continuity and disaster recovery plans; incident response plans that address recovery from backups and root cause analysis; at least annual testing of the plans and of the ability to restore from backups; and backups protected from unauthorized alteration or destruction [2].

Notices to DFS

A covered entity must notify DFS electronically no later than 72 hours after determining that a cybersecurity incident has occurred at the entity, its affiliates or a third-party service provider, and must keep DFS updated with material changes [1]. The new definition of cybersecurity incident adds events that resulted in the deployment of ransomware within a material part of the entity’s information systems [2].

The amendment also added an extortion-payment notice: notice of the payment within 24 hours of making it, and within 30 days a written explanation of why payment was necessary, the alternatives considered, and the diligence performed, including on compliance with Office of Foreign Assets Control rules [1].

The annual filing, due April 15, is either a certification that the entity materially complied during the prior calendar year or an acknowledgment that it did not, with the sections affected and a remediation timeline. It is signed by the highest-ranking executive and the CISO, and supporting records are kept for five years [1]. Under section 500.20, a single prohibited act or failure to act is a violation, including a material failure to comply with any section for any 24-hour period [1].

The phase-in dates as DFS states them

Section 500.22 states the transition periods as lengths of time from the effective date of the second amendment, November 1, 2023. It gives no calendar dates for them [1].

  • Effective November 1, 2023: the new requirements in sections 500.19(e) to (h), 500.20, 500.21, 500.22 and 500.24.
  • 30 days: the new requirements in section 500.17, the notices to DFS.
  • 180 days: all other new requirements unless listed below.
  • One year: sections 500.4, 500.15, 500.16 and 500.19(a).
  • 18 months: sections 500.5(a)(2), 500.7, 500.14(a)(2) and 500.14(b).
  • Two years: sections 500.12 and 500.13(a) [1].

On our reading, the Class A audit duty in section 500.2(c) is not named in the longer periods and so falls under the 180-day default. The longest transition period is two years from November 1, 2023, so every period had ended before the date of this explainer, and all of the amended requirements now apply.

This explainer describes the regulation; it is not legal advice, and institutions should confirm with counsel how it applies to them. The evidence a covered entity gathers for its annual filing is set out in the companion NYDFS Part 500 filing checklist.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • NYDFS
  • 23 NYCRR 500
  • second amendment
  • Class A companies
  • multi-factor authentication
  • extortion payments
  • CISO