NYDFS Part 500 fully in force: outlook to 2027

Every phase of New York's amended cybersecurity rule now applies, the April 2027 filing is the first against the complete text, and DFS keeps settling cases at about $2 million a firm.

The question for 2027

New York's cybersecurity regulation for financial services, 23 NYCRR Part 500, took effect March 1, 2017, and its second amendment took effect November 1, 2023 [1]. The amendment's new duties were phased in over two years, and the last of them, multi-factor authentication for everyone who accesses a covered entity's information systems and a documented asset inventory, applied from November 1, 2025 [2] [3]. Governor Hochul announced the amended regulation on November 1, 2023 [6]. Calendar 2026 is therefore the first full year in which every new requirement is in force, and the annual filing due April 15, 2027 is the first in which a covered entity certifies or admits gaps against the complete rule [1] [4]. Statuses here are as checked on November 16, 2026.

Who is covered, and the three tiers

Part 500 reaches anyone operating, or required to operate, under a license, registration, charter, certificate, permit, accreditation or similar authorization under New York's Banking Law, Insurance Law or Financial Services Law, whether or not another government agency also regulates them [14].

The rule now sorts covered entities into three tiers. A limited exemption applies to an entity with fewer than 20 employees and independent contractors, less than $7,500,000 in gross annual revenue in each of the last three fiscal years from New York business, or less than $15,000,000 in year-end total assets, including affiliates [1]. A Class A company is a covered entity with at least $20,000,000 in gross annual revenue in each of the last two fiscal years from its own operations and its affiliates' New York operations, plus either more than 2,000 employees averaged over two years or more than $1,000,000,000 in gross annual revenue in each of those years, both counted across all affiliates wherever located [1]. Everyone else is what DFS calls a Standard Company [5].

The phased deadlines, now all passed

The dates below are copied from DFS's implementation timelines [2] [3].

The phased deadlines, now all passed
DateWhat took effect
December 1, 2023New notice rules in section 500.17, including reporting of ransomware deployments and ransom payments [2] [3]
April 15, 2024First certification or acknowledgment of noncompliance under the amended rule, for calendar 2023, signed by the highest-ranking executive and the CISO [2] [3]
April 29, 2024Annual risk assessment review, annual policy approval, annual penetration testing, social engineering training; for Class A companies, independent audits (500.2(c)) [2] [3]
November 1, 2024Governance duties for the CISO and senior governing body (500.4), encryption policy (500.15), incident response and business continuity plans with backup testing (500.16) [2] [3]
May 1, 2025Automated vulnerability scans (500.5(a)(2)), tighter access privileges and a password policy (500.7), malicious code controls (500.14(a)(2)); for Class A companies, privileged access management, automated blocking of common passwords, endpoint detection and response, and centralized logging and alerting [2] [3]
November 1, 2025Multi-factor authentication for all individuals accessing information systems (500.12) and a documented asset inventory (500.13(a)) [2] [3]

Multi-factor authentication is the widest of these. It applies to any individual accessing any information system of a covered entity; an entity with a limited exemption must still use it for remote access to its own systems, remote access to third-party applications holding nonpublic information, and all privileged accounts other than non-interactive service accounts [1]. A CISO may approve equivalent compensating controls in writing, reviewed at least annually [1].

What Class A companies carry on top

Three duties apply only to Class A companies [5]. They must design and conduct independent audits of their cybersecurity program based on their risk assessment [1]. They must monitor privileged access activity, run a privileged access management solution and block commonly used passwords automatically on systems they own or control; where blocking is infeasible, the CISO may approve the infeasibility and compensating controls in writing at least annually [1]. And they must run endpoint detection and response that watches for anomalous activity including lateral movement, together with a solution that centralizes logging and security event alerting, unless the CISO approves equivalent controls in writing [1].

Moraph's view

Moraph's view: we think most large banks and insurers already had the Class A tools in place before May 2025. The harder Class A duty is the independent audit, because it produces a dated, written view of the program that DFS examiners can ask for and that must line up with what the CISO and chief executive sign each April.

The April 15 filing and the incident clocks

By April 15 each year, every covered entity outside the full exemptions files either a certification that it materially complied during the prior calendar year or an acknowledgment that it did not [4]. The acknowledgment must identify every section not materially complied with, describe the nature and extent of the gap, and give a remediation timeline or confirm that remediation is done [1]. Both are signed by the highest-ranking executive and the CISO, and the supporting records must be kept for five years [1].

The notice clocks match those set out in our incident reporting trend report. A covered entity must notify DFS as promptly as possible and no later than 72 hours after determining that a cybersecurity incident has occurred at the entity, its affiliates or a third-party service provider [1]. If it makes an extortion payment connected to a cybersecurity event, it must give notice within 24 hours of the payment and, within 30 days, a written account of why the payment was necessary, the alternatives considered and the sanctions diligence performed [1].

Under section 500.20, a single prohibited act or failure is a violation, including the failure to secure nonpublic information because of noncompliance with any section, and the material failure to comply with any section for any 24-hour period [1]. Penalty factors include cooperation, good faith, prior violations, harm to consumers and consistency with frameworks such as NIST [1].

How DFS has enforced Part 500

The first Part 500 settlement was announced on March 3, 2021: Residential Mortgage Services paid $1.5 million, in part for not reporting a 2019 breach [19]. Larger cyber-only penalties before the amendment included Carnival's $5 million on June 24, 2022 [20], EyeMed's $4.5 million on October 18, 2022 [21] and OneMain's $4.25 million on May 25, 2023 [22]. On October 14, 2025 DFS said that under Superintendent Harris it had entered into consent orders with 27 entities for violations of its cybersecurity regulation, with over $144 million in fines [11].

Since the second amendment took effect, the enforcement press releases DFS lists on its Cybersecurity Resource Center announce these penalties for violations of Part 500 alone [14]:

How DFS has enforced Part 500
AnnouncedEntityPenalty as DFS states itFailings DFS names
November 28, 2023First American Title Insurance Company$1 million [7]Governance, data classification, access controls and risk assessment, tied to a May 2019 breach [7]
January 23, 2025PayPal, Inc.$2 million [9]Unqualified personnel and training; no MFA, CAPTCHA or rate limiting for customers [9]
August 14, 2025Healthplex, Inc.$2 million [10]No MFA on email, no email retention policy, notice to DFS more than four months after learning of the incident [10]
October 14, 2025Eight auto insurersMore than $19 million in total, from $1.85 million to $3 million each [11]Weak controls on online quoting tools; two of them reported late [11]
April 30, 2026Delta Dental Insurance Company and Delta Dental of New York$2.25 million [12]Inadequate incident response policies and procedures, exploited through MOVEit Transfer servers in 2023; late reporting [12]
August 5, 2026Order Express, Inc.$250,000 [13]Patching policies and risk assessments, at a money transmitter exempt from many requirements [13]

Genesis Global Trading's $8 million penalty, announced January 12, 2024, was for violations of both DFS's virtual currency regulation and its cybersecurity regulation, covering anti-money laundering, transaction monitoring, suspicious activity reporting, sanctions screening and cybersecurity failings; the release states one penalty without splitting it, so it is left out of a table limited to Part 500 alone [8]. Across the 13 consent orders in the table, penalties total $26.625 million and the median is $2.05 million; these figures cover only settlements DFS lists on its cybersecurity resource pages and may miss others [14] [7] [9] [10] [11] [12] [13]; the method is below.

Moraph's view

Moraph's view: three patterns stand out. Penalties since the amendment cluster at $2 million to $3 million per entity, below the 2022 peaks, and DFS builds totals by acting against several firms at once. Late notice to DFS appears in three of the six announcements, so the 72-hour clock is the cheapest violation to avoid. And most of the conduct punished so far predates the amendment's new controls, so the first orders built on the November 2025 MFA and inventory duties are still ahead.

Guidance since 2025: no new rule, more expectations

DFS has added guidance rather than rules. Its October 21, 2025 letter on third-party service providers says it imposes no new requirements and walks through diligence, contracting, oversight and termination, including clauses on whether a provider may use the entity's data to train AI models [16]. Its September 10, 2026 letter on risk assessments also says it creates no new obligations [17]. A May 21, 2026 letter to CISOs on frontier AI models urges faster vulnerability remediation, dependency maps with critical providers and a review of whether logging and alerting are sufficient [18]. As checked on November 16, 2026, DFS's regulatory activity page lists no pre-proposed or proposed amendment to Part 500 [15].

Moraph's view

Moraph's view: the guidance letters show where examiners will look in 2027: risk assessments that actually drive the program, third-party offboarding and logging that would catch AI-accelerated attacks. We expect DFS to enforce the 2023 text through examinations and consent orders rather than open a third amendment before 2028.

What to watch in 2027

  • The April 15, 2027 filing, the first covering a full year with MFA and asset inventory in force [2] [4].
  • The first consent order that cites the universal MFA duty in section 500.12 for conduct after November 1, 2025 [1] [3].
  • Whether the 24-hour extortion payment notice appears in an enforcement action; none of the releases in the table cites it [7] [9] [10] [11] [12] [13].

Data and method

Scope: DFS press releases announcing penalties for violations of 23 NYCRR Part 500, dated from November 1, 2023, when the second amendment took effect [1], to November 16, 2026, found through the cybersecurity-related list of enforcement actions and press releases on the DFS Cybersecurity Resource Center [14]; a Part 500 settlement DFS did not add to that list would be missed. Releases that combine cybersecurity with anti-money laundering findings, such as Genesis Global Trading [8], are excluded because the penalty is not split between the regulations. Each consent order counts once: the eight auto insurers count as eight [11], and the two Delta Dental companies, covered by one consent order, count as one [12]. Amounts are as stated in each release: $1,000,000 [7]; $2,000,000 [9]; $2,000,000 [10]; $2,775,000, $1,850,000, $3,000,000, $2,250,000, $2,700,000, $2,050,000, $2,000,000 and $2,500,000 [11]; $2,250,000 [12]; and $250,000 [13]. The total of $26.625 million is the sum of these 13 amounts, and the median of $2.05 million is the seventh value when they are sorted [7] [9] [10] [11] [12] [13]. Late notice is counted only where the release says the entity failed to report on time or reported beyond the 72-hour requirement [10] [11] [12].

What this means for you

  • Class A banks and insurers: Line up the independent audit, the CISO's written approvals of any compensating controls and the April 15 certification, since the rule makes each a dated record [1]. Check that endpoint detection and centralized logging would show lateral movement, which section 500.14(b) names [1].
  • Standard covered entities: Treat the 2026 calendar year as the first test of universal MFA and the asset inventory, both in force from November 1, 2025 [3]; where either falls short, the acknowledgment of noncompliance with a remediation timeline is the route the rule provides [1].
  • Small and partly exempt licensees: File or update the notice of exemption within 30 days of determining that the entity is exempt [1], and keep the duties that still apply: DFS fined Order Express $250,000 although it is exempt from many requirements [13].
  • Incident response and legal teams: Record the moment a cybersecurity incident is determined, including one at an affiliate or third-party provider, to meet the 72-hour clock [1]; late notice was named in the Healthplex, auto insurer and Delta Dental orders [10] [11] [12].
  • Technology providers to New York licensees: Expect clients to ask for contract terms on notice, data return, offboarding and AI training use, all covered in DFS's October 2025 third-party guidance [16].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 75% Open

    DFS announces at least two new penalties for violations of 23 NYCRR Part 500 in press releases dated in calendar 2027.

    How we will check: Two or more DFS press releases dated January 1 to December 31, 2027 that announce a penalty for violations of the cybersecurity regulation (23 NYCRR Part 500), counting releases that also cover other violations.

    Basis: DFS announced Part 500 penalties in January, August and October 2025 [9] [10] [11] and in April and August 2026 [12] [13].

  2. P2 By Confidence 80% Open

    DFS does not post a proposed or pre-proposed amendment to 23 NYCRR Part 500.

    How we will check: No proposed or pre-proposed amendment to Part 500 appears on DFS's regulatory activity page or in the New York State Register on or before December 31, 2027.

    Basis: As checked on November 16, 2026 the regulatory activity page lists none [15]; DFS's 2025 and 2026 cybersecurity guidance letters say they impose no new requirements [16] [17].

  3. P3 By Confidence 75% Open

    A DFS press release or consent order announcing a Part 500 penalty names a failure to use multi-factor authentication.

    How we will check: A DFS press release or consent order dated between November 17, 2026 and June 30, 2028 that announces a Part 500 penalty and states that the entity failed to implement, require or maintain multi-factor authentication.

    Basis: Universal MFA applies from November 1, 2025 [3]; missing MFA was named in the Carnival, EyeMed, PayPal and Healthplex settlements [20] [21] [9] [10].

  4. P4 By Confidence 85% Open

    No single DFS penalty for violations of Part 500 alone reaches $10 million.

    How we will check: No DFS press release dated on or before December 31, 2027 announces a penalty of $10 million or more against one entity, or one consent order, for violations of Part 500 without other regulatory violations.

    Basis: Before the amendment, cyber-only penalties included $5 million for Carnival [20]; since it, the largest single amount is $3 million for Hartford Fire Insurance Company [11].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

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

  • 23 NYCRR Part 500
  • NYDFS
  • cybersecurity regulation
  • Class A companies
  • multi-factor authentication
  • asset inventory
  • annual certification
  • enforcement