Summary

  • Every April since the rule took effect, a New York-regulated financial firm must file one of exactly two things: a certification that it materially complied with the cybersecurity regulation for the prior calendar year, or an acknowledgment that names every section it did not materially comply with and gives a remediation date.
  • Two officers sign it — the highest-ranking executive plus the CISO, or the senior officer who runs cybersecurity where there is no CISO — and the supporting file must be kept five years. Across three 2025 consent orders the regulator recited the calendar year and the filing date of each certification, priced the improper certification as its own violation, and never published the certification.

Start with the fork in the road, because there is no third branch. Section 500.17(b)(1) of Title 23 of the New York Codes, Rules and Regulations requires each covered entity to submit to the Superintendent, electronically, by 15 April, either a written certification or a written acknowledgment of noncompliance. The certification says the firm materially complied with the requirements of Part 500 during the prior calendar year, and it must rest on data and documentation sufficient to determine and demonstrate that material compliance. The acknowledgment is not a blank page with an apology: it must state that the firm did not materially comply with all the requirements, identify every section it did not materially comply with, describe the nature and extent of the noncompliance, and give a remediation timeline or confirm the remediation is already done. The text is in the Department's own posted consolidated Part 500 (23 NYCRR Part 500).

The signature line is where this instrument separates itself from every notification clock a security team already knows. Paragraph (b)(2) requires the filing to be in the form on the Department's website and to be signed by the covered entity's highest-ranking executive and its CISO. Where the firm has no CISO, the second signature belongs to the senior officer responsible for the cybersecurity programme. Two names, one document, once a year.

What the Department says around the rule sharpens the choice. Its submissions page states the binary plainly and adds that the certification is accepted between 1 January and 15 April of the following calendar year (Cybersecurity Submissions). The FAQs go further: a covered entity may not submit a certification of material compliance unless it was in material compliance with all applicable requirements for the calendar year before the year of submission, and a firm that was not must file the acknowledgment (Cybersecurity FAQs). The same page lists the factors that make a shortfall material — industry, size, type and amount of data, and the nature, duration, scope and potential impact of the noncompliance — and warns that several immaterial violations, taken together, may be material. Then comes the sentence that tells you who actually decides: covered entities must keep all records and documentation supporting the decision to file a particular type of notification, including the reasons for that decision.

That is the whole architecture. A judgement about materiality is authored inside the firm, signed by two of its officers, filed electronically, and supported by a file the firm must retain for five years and produce to the Department on request. Paragraph (b)(3) is explicit about the five years and about examination and inspection. Nothing in it creates a publication duty.

Two things this article will not claim, because the materials do not support them. First, the regulation does not contain a clause announcing that the notice is not a certification of technical security or of security effectiveness; that disclaimer is not in the text I read. What the text does instead is narrower and more useful — the certification is a statement about compliance with this Part, a legal checklist, not a statement about the state of the controls behind it. Second, the phrase "materially false statement" does not appear in the rule, and no reviewed provision creates an offence aimed at the signer.

The only false-information language in the inspected text is a penalty factor: section 500.20(c)(7) lists, among the matters the Superintendent shall take into account when assessing penalties under the Banking Law, Insurance Law or Financial Services Law, whether the covered entity provided false or misleading information. A factor in a penalty assessment is a real consequence, and it is not the same thing as a charge against an individual, and the difference matters to anyone who has to decide what to sign.

The enforcement record is where the instrument gets interesting. In August 2025 the Department published a consent order against Healthplex, Inc. that recites four dated certifications — the 2018 year certified on 8 February 2019, 2019 on 27 August 2020, 2020 on 12 April 2021, 2021 on 15 April 2022 — finds that the company was not in compliance at the time of the certifications, calls them improper, and imposes a $2,000,000 civil monetary penalty under Financial Services Law § 408 (Healthplex consent order). On 14 October 2025 two more orders followed the same template: Metromile Insurance Company, four certifications recited and a $2,050,000 penalty (Metromile consent order), and Liberty Mutual Insurance Company, five certifications for the 2018 through 2022 years and a $2,700,000 penalty (Liberty Mutual consent order). Together, $6.75 million, and in each case the improper certification is charged as its own violation of 500.17(b) rather than as a footnote to the control failures.

Now read what those three orders print and what they do not. Each recites the calendar year covered and the date the filing arrived. None of them reproduces the certification. In the material I reviewed on 20 November 2026 — these three orders and the Department's cybersecurity pages — no signed certification or acknowledgment appears in any form. That is a bounded statement about the reviewed set, not a claim that no such filing is public anywhere; but it is the shape of the record, and the shape is the finding.

The regulator holds a two-signature statement about a firm's entire year, prices it when it is wrong, and describes it to the public in a paragraph rather than a document.

One detail inside the Healthplex order deserves to be quoted rather than smoothed over, because it shows how these documents are assembled. The order recites dated certifications for the 2018, 2019, 2020 and 2021 calendar years — four filings — and then its charging paragraph states that the company improperly certified compliance "for the calendar years 2017-2021". Five years named, four filings recited. It may be a drafting slip; the order does not explain it. It is a reminder that the enforcement narrative is a summarising document written after the fact, which is precisely why the underlying signed filings would be worth seeing.

A timing caution belongs here rather than buried. All three orders apply Part 500 as it read before November 2023, and the reviewed material does not print the filing deadline that applied in those years. So the recited dates — including one certification that arrived in late August — cannot be scored here against today's 15 April date, and this article does not score them. What changed in 2023 is documented by secondary commentary: the standard moved from compliance to material compliance and the CISO signature was added alongside the senior executive (NYU Stern commentary). That source is commentary on the drafting history, not the regulation, and is labelled as such.

One further claim circulates widely and should carry its label. A law-firm refresher note states that making false statements to the Department is itself actionable and that the certifying individual could be held personally liable (Cooley refresher note). The note cites no statute and no prosecution, and none of the material I reviewed identifies a case against a signatory. Treat it as commentary: a proposition worth watching, not a demonstrated consequence.

What this publication has previously carried on the New York State Department of Financial Services is a directory profile card and nothing else; no part of Part 500 has been read here before. That makes the addition simple to state. A notification clock tells the regulator what happened, and this correspondent has spent a year and more than forty briefings on such clocks — four business days from a determination, 36 hours from a bank's own judgement, 72 hours from reasonable belief. The annual notice asks something the clocks never ask: was the whole year compliant, and will two named officers say so in writing. New York built that instrument, gave it a five-year evidence file, and put a price on getting it wrong. What it did not build is a way for anyone outside the building to read the answer.

So the control recommendation is deliberately modest, and it is a return rather than an accusation. In any enforcement record that turns on a certification, publish the three fields the Department already holds: the calendar year certified, the date the filing arrived, and the qualification that certification did or did not carry. Add the same three fields to an annual public count of certifications and acknowledgments filed.

That is enough for a stranger to see whether the two-box structure is being used as designed — whether firms that fell short chose the acknowledgment, whether the ones that certified were ever contradicted — without publishing anything about a firm's controls that the regulator has not already put in an order. The signature is only worth the paper if somebody outside can tell that the paper exists.