# Checklist: assembling the evidence for the NYDFS Part 500 compliance filing due April 15

Thirteen steps a New York DFS-regulated covered entity works through before its highest-ranking executive and CISO sign the annual certification or acknowledgment under 23 NYCRR 500.17(b), with the CISO report, MFA and asset inventory in scope.

Checklist · Financial Services · Regulation & Compliance. Published November 14, 2026. Last reviewed November 14, 2026.

## What the filing asks for

Each covered entity must submit to the superintendent electronically by April 15 every year either a certification that it materially complied with Part 500 during the prior calendar year, or an acknowledgment that it did not, listing the sections and a remediation timeline. The filing is signed by the highest-ranking executive and the CISO (or, without a CISO, the senior officer responsible for the cybersecurity program), and the records supporting it are kept for five years, under section 500.17(b) [1]. The second amendment took effect on November 1, 2023. Its transitional periods in section 500.22(d) gave covered entities two years from that date for the new multi-factor authentication and asset inventory requirements in sections 500.12 and 500.13(a) [1]. On our reading, the filing for calendar year 2026, due April 15, 2027, is the first to cover a full year after that two-year period; the regulation does not say so.

## Using the steps

The steps run in the order the evidence is usually gathered, ending with the decision to certify or acknowledge. Each names the section of Part 500 behind it and who usually owns it, and steps that are our suggestions say so. We cite the text of Part 500 as amended that DFS publishes on its website, which DFS notes is not the official version [1]. This page explains the regulation; it is not legal advice.

## The checklist

1. **Confirm the entity’s status for the year: covered entity, class A company, or eligible for the limited exemption.** (Chief Compliance Officer with legal) Section 500.1(d) defines a class A company by revenue and employee or global revenue tests, and class A companies must also run independent audits of the program under section 500.2(c). Section 500.19(a) exempts entities below the employee, revenue or asset thresholds from sections 500.4, 500.5, 500.6, 500.8, 500.10, 500.15, 500.16 and parts of 500.14 [1].
2. **Update the risk assessment and keep the documentation that shows it was reviewed at least annually.** (CISO) Section 500.9(a) requires review and update at least annually and whenever a business or technology change materially changes cyber risk; section 500.9(b) requires written procedures and documentation [1].
3. **Have the cybersecurity policies approved for the year by a senior officer or the senior governing body.** (CISO prepares; senior officer or board approves) Section 500.3 requires annual approval and lists the 15 areas the policies address, from information security to vulnerability management [1].
4. **Deliver the CISO’s annual written report to the senior governing body and file the minutes showing it was received.** (CISO and corporate secretary) Section 500.4(b) lists what the report covers, including material cybersecurity risks, overall effectiveness of the program, material cybersecurity events and plans for remediating material inadequacies. Section 500.4(d) requires the board to exercise oversight, including regularly receiving and reviewing management reports [1]. Keeping the minutes with the filing evidence is our suggestion.
5. **Validate the asset inventory against its written procedures: every information system with owner, location, classification, support expiration date and recovery time objective.** (IT asset management) Section 500.13(a) requires written policies and procedures to produce and maintain a complete, accurate and documented inventory, tracking those fields as applicable, and to set how often it is updated and validated [1].
6. **Show that multi-factor authentication is used for any individual accessing any information system, and list any CISO-approved compensating controls with their annual review.** (Identity and access management) Section 500.12(a) and (b). Entities with the limited exemption must still use it for remote access, remote access to third-party applications holding nonpublic information, and all privileged accounts other than service accounts that prohibit interactive login [1].
7. **Complete the annual review of user access privileges and record the accounts removed or disabled.** (Identity and access management) Section 500.7(a)(4). Class A companies must also run a privileged access management solution and block commonly used passwords, under section 500.7(c) [1].
8. **File the year’s penetration test, inside and outside the system boundaries, and the vulnerability scanning results.** (Security testing lead) Section 500.5(a) requires penetration testing by a qualified internal or external party at least annually and automated scans, with manual review of systems the scans do not cover, at a frequency set by the risk assessment and promptly after material system changes [1].
9. **Gather evidence that all personnel completed cybersecurity awareness training that includes social engineering.** (Security awareness lead with HR) Section 500.14(a)(3) requires the training at least annually. Class A companies also need endpoint detection and response and centralized logging under section 500.14(b), unless the CISO approved equivalent controls in writing [1].
10. **Record the annual test of the incident response and business continuity plans and the test of restoring critical data from backups.** (Business continuity lead with the CISO) Required by section 500.16(d)(1) and (2) [1].
11. **Review the third-party service provider policies and the periodic assessments made of providers during the year.** (Third-party risk management) Section 500.11(a) requires risk-based policies covering identification, minimum practices, due diligence and periodic assessment of providers [1].
12. **Reconcile the year’s incident log with the notices sent to DFS: 72-hour cybersecurity incident notices and any extortion payment notices.** (CISO with compliance) Section 500.17(a) requires notice within 72 hours of determining that a cybersecurity incident occurred, and section 500.17(c) requires notice within 24 hours of an extortion payment and a written explanation within 30 days [1]. The reconciliation is our suggestion, so the filing does not overlook a missed notice.
13. **Decide between certification and acknowledgment on the evidence, have the highest-ranking executive and the CISO sign, submit by April 15, and file the support for five years.** (Chief executive, CISO and Chief Compliance Officer) Section 500.17(b)(1) requires the certification to rest on data and documentation sufficient to show material compliance; an acknowledgment must identify each section not materially complied with and give a remediation timeline. Section 500.17(b)(2) sets the signatories (where there is no CISO, the senior officer responsible for the cybersecurity program signs) and section 500.17(b)(3) the five-year record [1].

## Sources

1. New York State Department of Financial Services. 23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies, as amended by the Second Amendment (DFS text, which DFS notes is not the official version). <https://www.dfs.ny.gov/system/files/documents/2026/10/NYCRR-part-500-Cybersecurity-Regulation_1.pdf> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-nydfs-part-500-annual-compliance-filing>
Publisher: Moraph Insights
