If DFS asked tomorrow for the documents behind the cybersecurity certification your CEO and CISO are about to sign, could you hand them over in a single afternoon? For most New York-regulated lenders, insurers, agencies, and money transmitters, that is the real test of the NYDFS Part 500 certification due April 15, 2027, and the time to answer it is now, not in March.
The short answer: the NYDFS Part 500 certification filed by April 15, 2027 covers calendar year 2026, the first full year in which every Second Amendment requirement applied, including universal MFA and a written asset inventory. Before signing, leadership needs dated evidence for each requirement, or an honest Acknowledgment of Noncompliance with a remediation timeline.
It covers compliance during calendar year 2026. Under section 500.17(b) of the amended 23 NYCRR Part 500, each covered entity must submit by April 15 either a certification that it materially complied with Part 500 during the prior calendar year, or a written acknowledgment that it did not, identifying every section involved, describing the nature and extent of noncompliance, and giving a remediation timeline.
Two details raise the stakes. The filing must be signed by both the highest-ranking executive and the CISO, or the senior officer responsible for cybersecurity if there is no CISO. And the entity must keep all records supporting the filing for five years and produce them on request. A signature is not a formality; it is a statement DFS can test against documents.
The last Second Amendment provisions took effect on November 1, 2025, as Greenberg Traurig summarized when they came into force. Those were the expanded MFA requirement in section 500.12 and the asset inventory requirement in section 500.13(a). The certification filed in April 2026 covered a year in which those rules applied for only two months. The April 2027 filing covers twelve months of them, with no transition period left to point to.
Many executives treat the Acknowledgment of Noncompliance as the dangerous option, something to avoid at almost any cost. The record suggests the opposite. The filing that has drawn penalties is the unsupported certification, because it turns a control gap into a separate violation with a named executive's signature attached.
DFS has charged this directly. In its August 2025 consent order with Healthplex, Inc., the Department found that the company improperly certified compliance for calendar years 2017 through 2021 in violation of section 500.17(b), alongside the underlying failures. DFS's announcement of the $2 million Healthplex penalty described those failures: a phishing email that exposed a customer service mailbox, no MFA on the Microsoft 365 email environment, no email retention limits, and notice to DFS more than four months after the company learned of the exposure.
Healthplex is not an outlier. When DFS fined Robinhood Crypto $30 million in 2022, its press release stated that the company improperly certified compliance with the cybersecurity regulation and that companies should only certify if their programs are compliant. An acknowledgment with a credible remediation plan is a disclosure. A certification that the evidence cannot support is a finding waiting to happen.
The certification is an attestation about a full year, so the evidence needs dates throughout 2026, not a snapshot taken in March 2027. The table below lists the requirements that most often lack documentation in the environments we review, with the evidence that supports each one.
| Requirement | Section | Evidence to have in hand |
|---|---|---|
| MFA for any individual accessing any information system | 500.12 | MFA coverage report across systems, plus any CISO-approved compensating controls in writing, reviewed at least annually |
| Complete, documented asset inventory | 500.13(a) | Written inventory procedure, the inventory itself with owner, location, sensitivity, support expiration, and recovery time objectives, and records of updates at the frequency your policy sets |
| Risk assessment | 500.9 | Current written assessment specific to your entity, and proof it shaped the program |
| Access privilege review | 500.7 | At least annual review of all user access, with removed accounts recorded |
| Incident response and BCDR plans | 500.16 | Plans that name regulatory reporting steps, records of annual testing with critical staff and management, and a backup restoration test |
| Notification readiness | 500.17(a), (c) | Procedure for 72-hour incident notice and for 24-hour extortion payment notice with a 30-day written justification |
| Governance | 500.3, 500.4 | Policies approved at least annually and the CISO's written report to the senior governing body |
| Training | 500.14 | Annual awareness training records that include social engineering |
The MFA row deserves a closer look. The full requirement applies to any individual accessing any information system, not just remote access and privileged accounts. Remote access, third-party cloud applications holding nonpublic information, and privileged accounts are the minimum scope for entities that qualify for the limited exemption in section 500.19(a). If your MFA report only covers VPN and admin accounts, you probably have evidence for the exempt standard, not the full one. Our guide to cleaning up IAM, MFA, and privileged access walks through building that coverage report.
Section 500.16 requires covered entities to test their incident response and business continuity plans at least annually with all staff and management critical to the response, and to test restoring critical data from backups. The regulation does not mandate a particular format, but a tabletop exercise with dated attendance, findings, and plan revisions is the most common way to evidence it. A plan that has never been exercised will be hard to certify.
On April 30, 2026, DFS announced a $2.25 million settlement with Delta Dental Insurance Company and Delta Dental of New York arising from the 2023 MOVEit Transfer attacks. DFS said inadequate incident response policies and procedures contributed to the exposure of consumer data, that retention settings and controls fell short, and that the companies failed to report their cybersecurity events on time. Debevoise's analysis of the order notes the incident response plan was charged as two standalone violations because it did not adequately address regulatory reporting, and that notice reached DFS roughly six months after the webshell was found.
Smaller entities are not out of reach either. In August 2026, DFS announced that licensed money transmitter Order Express would pay $250,000 for deficient risk assessments and inadequate policies for system updates, even though its limited revenue exempted it from many Part 500 requirements. Partial exemption narrows the list of obligations. It does not remove the risk assessment, and it does not remove the certification.
The cost of getting this wrong lands on the signers personally, on the entity through penalties and independent consultant requirements, and on the business through examination findings that can follow it for years. A structured review in the first quarter of 2027 avoids most of that. This is the sequence we recommend.
Third-party providers are part of this picture. Section 500.17(a) requires notice within 72 hours of determining that a cybersecurity incident occurred at the entity, its affiliates, or a third-party service provider, which means vendor incidents can start your clock. Our article on common incident response planning mistakes covers how plans tend to fail at exactly that handoff. The same attestation discipline applies to insurance applications, as we explain in The Attestation Trap: Why Cyber Insurance Claims Get Denied.
If your organization is also deploying AI tools that touch nonpublic information, those systems belong in the asset inventory and risk assessment too. Our AI Lab piece While State AI Laws Stalled, Your Actual Regulator Kept Moving explains why sector regulators like DFS are where AI scrutiny is actually arriving.
For covered entities, we build the evidence package across the year rather than at the deadline: MFA coverage reports against the full 500.12 standard, an asset inventory that tracks the fields 500.13 requires, quarterly access reviews, and incident response tests with dated records. We also help write the incident response plan's regulatory reporting section so the 72-hour and 24-hour clocks have named owners.
Where an entity does not have a full-time CISO, our vCISO support can fill the signing role's preparation work and the annual written report to the board. Our comparison of a vCISO versus a full-time CISO covers how that decision usually plays out for smaller financial firms.
The April 15, 2027 NYDFS Part 500 certification is the first to cover a full year of every Second Amendment requirement, and DFS has shown it will penalize certifications the evidence cannot support. Start assembling dated 2026 evidence now, and decide early whether certification or acknowledgment is the honest filing.
For year-round help building and maintaining that evidence, see how Securafy's compliance management service supports regulated financial firms.
If you would rather talk through your specific environment first, book a strategy call with Securafy and we will walk your current Part 500 evidence, gaps, and the fastest path to a certification your leadership can sign with confidence.