SMSMC Blog

The April 15 Part 500 filing: what a small agency signs, and what has to be true

What the NYDFS annual cybersecurity filing asks for, who is exempt, and what a small agency or lender can prepare now for April 15, 2027.

By Jim Venuto

The one example DFS gives

When the New York Department of Financial Services explains what “material noncompliance” means, it picks a plain example: a regulated business that never carried out a cybersecurity risk assessment. Everything else in its program is supposed to rest on that assessment, so without one the business cannot certify that it complied. It has to say so instead. [1]

That is the choice every DFS licensee faces each spring. By April 15, the owner (and whoever runs cybersecurity) signs one of two forms about the year just ended. This post explains what those forms say, who has to file, who does not, and what to put in place now so the April 2027 filing is a short, calm job.

What gets filed, and by whom

Under 23 NYCRR Part 500, every “covered entity” sends DFS an annual notice by April 15 about the previous calendar year. The filing due April 15, 2027 covers calendar year 2026. [2][3]

A covered entity is any business operating under a DFS license, registration, charter or similar authorization under the Banking, Insurance or Financial Services Laws. That includes insurance agencies and brokers, many individual agents, and state-licensed lenders and mortgage firms. [4]

There are two forms, and you choose one: [2][3]

  • Certification of Material Compliance. You certify that the business materially complied with every requirement that applies to it, for the whole of the prior year. The certification has to rest on data and documentation that show it.
  • Acknowledgment of Noncompliance. You name each section you did not materially comply with, describe the gap, and give a remediation timeline or confirm the fix is done.

The form is signed by the business’s highest-ranking executive and its CISO. If there is no CISO, the senior officer responsible for the cybersecurity program signs instead. An individual licensee signs alone. [2][1] Filing is done in the DFS Portal, which you sign in to with a DFS ID and multifactor authentication; DFS emails a receipt number, and that email is the only confirmation you get. [3]

DFS does not accept a certification from a business that was not in material compliance. Not every lapse is material: the business decides whether any noncompliance was significant in its overall circumstances, considering its industry, size, the data it holds, and the nature, duration, scope and potential impact of the noncompliance. DFS says a single, short, inadvertent lapse with little or no impact is not likely to be material, but several small violations together can be. If the business was not in material compliance, the acknowledgment is the correct form. [1] Whichever you file, keep the records behind it for five years. DFS can ask to see them. [2][3]

Who is exempt, and what “exempt” still means

Part 500 has two kinds of exemption, and they are often confused. [5][1]

A limited exemption (section 500.19(a)) applies if the business, counted together with its affiliates, has any one of these: [6][5]

  • fewer than 20 employees and independent contractors;
  • less than $7.5 million in gross annual revenue in each of the last three fiscal years (counted as DFS defines it); or
  • less than $15 million in year-end total assets.

A limited exemption removes some sections, such as the requirement to appoint a CISO and to keep a full incident response plan. It does not remove the annual filing. DFS’s own checklist for these businesses lists what still applies: [6]

  • the annual filing by April 15;
  • written cybersecurity policies, reviewed and approved every year;
  • a risk assessment, reviewed at least yearly and after significant changes;
  • awareness training for all staff at least yearly, including social engineering;
  • a yearly review of who has access to what, including outside providers;
  • a written password policy, secure disposal of data you no longer need, and remote-control protocols turned off or secured;
  • multifactor authentication for remote access, for outside applications that hold nonpublic information, and for all privileged accounts;
  • an up-to-date asset inventory;
  • assessments of third-party service providers; and
  • reporting of cybersecurity incidents and extortion payments.

Contractors count toward the 20, whatever their hours, and so do the staff of affiliates. DFS says the limited exemption is meant for small businesses, not small branches of large ones. [1]

A full exemption removes the filing altogether, but it covers narrow cases: an employee, agent or wholly owned subsidiary that is covered by another covered entity’s program, and some specific groups such as inactive individual licensees. [5][1] An independent agency with its own computers and client files will rarely fit.

Exemptions are generally claimed by filing a Notice of Exemption within 30 days of deciding you qualify, and the notice is amended if your situation changes. If you stop qualifying, you have 180 days to meet every requirement that now applies. [1][3]

Why the 2027 filing is a little different

The second amendment to Part 500 took effect on November 1, 2023 and phased in over two years. The last pieces, the expanded multifactor authentication requirement and the asset inventory, applied from November 1, 2025. [2] So calendar year 2026 is the first full year in which every part of the amended rule applied. The April 2027 filing is the first one that covers a full year of all of it.

What to prepare now

Most of this is organizing what you already have and writing down what you already do.

  1. Confirm your exemption status. Count employees and contractors, including affiliates, and check revenue and assets. If you filed a Notice of Exemption years ago, check that it still matches your situation, and amend it if not. [1]
  2. Decide who signs. Name the highest-ranking executive and the person responsible for cybersecurity. Make sure both can sign in to the DFS Portal before April. [2][3]
  3. Start a filing folder. For each requirement that applies to you, put in the proof: the approved policies, the risk assessment, training records, the access review, the multifactor authentication settings, the asset inventory and the provider assessments. [6]
  4. Check the whole year, not just today. The certification covers January to December. A control switched on in September was missing for the earlier months, and that has to be weighed when you decide whether the year was materially compliant. [2][1]
  5. Decide materiality, in writing, then choose the form. For each gap in 2026, record its nature, duration, scope and impact, and whether it was material on its own or together with others. If the business was not in material compliance, file the acknowledgment, name each section, and give a remediation timeline or confirm the fix is done. [2][1]
  6. Bring your IT provider in, but keep the decision. DFS has said in writing that a covered entity may not hand responsibility for compliance to an affiliate or a third-party service provider. Your provider runs the tools; the business answers for the program. [7]

The gaps that come up most often

These are the places the DFS requirements and guidance point to, and where small businesses most often come up short:

  • A risk assessment that is old or missing. DFS’s own example of material noncompliance, and the base of everything else. DFS issued guidance in September 2026 on how to carry out and use a risk assessment. [1][8]
  • No asset inventory. DFS calls an accurate, current asset inventory a foundational input to the risk assessment. [8]
  • Multifactor authentication on email but not elsewhere. Remote access, privileged accounts and outside applications that hold client information all need it, even under the limited exemption. [6]
  • Providers never assessed. Managed IT providers and others with system access must be assessed, and DFS has seen businesses rely on them without enough oversight. [7][6]
  • No folder behind the signature. A certification has to be based on data and documentation, kept for five years. [2]

Who does what

  • The owner and the signers: decide the exemption question, approve the policies, choose the form and sign it.
  • The IT provider: turns on and evidences the technical controls, such as multifactor authentication, access changes and the asset list.
  • An independent advisor (if you use one): runs the risk assessment, writes the policies, assembles the filing folder and walks the signers through what they are signing. The business still files and signs.

Start with where you stand

Security Medic Consulting helps New York businesses get ready for the Part 500 filing with proof in hand, working alongside your IT provider. To talk through your own gaps, book a free 30-minute call: https://bookings.cloud.microsoft/book/SecurityMedicConsulting@securitymedic.com/

Sources

  1. NYDFS, Cybersecurity FAQs: https://www.dfs.ny.gov/cybersecurity/faqs (accessed 2026-10-29)
  2. NYDFS, 23 NYCRR Part 500 (Cybersecurity Requirements for Financial Services Companies), §§500.17(b), 500.19, 500.22: https://www.dfs.ny.gov/cybersecurity/23-NYCRR-Part-500 (accessed 2026-10-29)
  3. NYDFS, Cybersecurity submissions (annual compliance notification, Notice of Exemption, DFS Portal and DFS ID): https://www.dfs.ny.gov/cybersecurity/submissions (accessed 2026-10-29)
  4. NYDFS, Compliance resources for individuals and small businesses: https://www.dfs.ny.gov/cybersecurity/small-business-resources (accessed 2026-10-29)
  5. NYDFS, Cybersecurity Regulation exemptions: https://www.dfs.ny.gov/cybersecurity/exemptions (accessed 2026-10-29)
  6. NYDFS, Part 500 Requirement Checklist for DFS-Regulated Entities with §500.19(a) Limited Exemptions (July 2026): https://www.dfs.ny.gov/system/files/documents/2026/07/Cybersecurity-Part500-Requirement-Checklist_0.pdf (accessed 2026-10-29)
  7. NYDFS, Industry letter, Guidance on managing risks related to third-party service providers (October 21, 2025): https://www.dfs.ny.gov/industry-guidance/industry-letters/il20251021-guidance-managing-risks-third-party (accessed 2026-10-29)
  8. NYDFS, Industry letter, Guidance on how to conduct and use risk assessments required by the DFS Cybersecurity Regulation (September 10, 2026): https://www.dfs.ny.gov/industry_guidance/industry_letters/il20260910-cyber-risk-assessment (accessed 2026-10-29)