Guide · NYDFS Part 500
NYDFS Part 500 for New York-licensed mortgage companies
If your company is licensed as a mortgage banker, or registered as a mortgage broker or mortgage loan servicer, under New York's Banking Law, DFS's cybersecurity regulation (23 NYCRR Part 500) applies to you. DFS amended it effective November 1, 2023 and phased in the new requirements over two years. The last phase, multi-factor authentication for everyone who accesses your information systems and a documented asset inventory, took effect November 1, 2025.
Every covered company files with DFS by April 15 each year: either a certification that it materially complied during the prior calendar year, or an acknowledgment that it didn't, with a remediation timeline. A cybersecurity incident goes to DFS within 72 hours of determining it occurred. Smaller firms can qualify for a limited exemption from some sections, but not from the whole rule.
Who's covered
Part 500 covers any person "operating under or required to operate under a license, registration, charter, certificate, permit, accreditation or similar authorization under the Banking Law, the Insurance Law or the Financial Services Law, regardless of whether the covered entity is also regulated by other government agencies" (500.1(e)). Mortgage bankers are licensed, and mortgage brokers and mortgage loan servicers registered, under Article 12-D of the Banking Law.
That last clause matters for non-bank lenders. Part 500 sits on top of the FTC Safeguards Rule, not in place of it.
Larger "Class A" companies have extra requirements, including independent audits, privileged access management and endpoint detection. A Class A company has at least $20 million in gross annual revenue in each of the last two fiscal years (its own operations plus its affiliates' New York operations), and either more than 2,000 employees averaged over those two years or more than $1 billion in gross annual revenue in each of them, counting affiliates (500.1(d)).
What the amended rule requires
For a covered company that isn't exempt, the core requirements are:
Program, policies and governance
- A cybersecurity program based on your risk assessment (500.2).
- Written policies approved at least once a year by a senior officer or your senior governing body, covering the areas listed in the rule, from data retention and access controls to vendor management and incident response (500.3).
- A designated CISO, who can work for you, an affiliate or a third-party provider. If outside, you keep responsibility, name a senior person to oversee them, and require the provider to keep a program that protects you (500.4(a)).
- A written CISO report to the senior governing body at least once a year, and board oversight of cyber risk (500.4(b), (d)).
- A risk assessment reviewed and updated at least once a year and whenever a business or technology change materially changes your cyber risk (500.9).
Controls
- Penetration testing at least once a year by a qualified internal or external party, plus automated scans and manual review at a frequency set by your risk assessment (500.5).
- Audit trails (500.6) and secure development and app-evaluation procedures (500.8).
- Access limited to what each job needs, fewer privileged accounts, a yearly access review, prompt removal when people leave, and a written password policy if you use passwords (500.7).
- Written policies for third-party service providers that touch your systems or data (500.11).
- MFA for any individual accessing any of your information systems (500.12).
- A complete, documented asset inventory, and secure disposal of nonpublic information you no longer need (500.13).
- Monitoring of user activity, controls against malicious code, and cybersecurity awareness training at least once a year that includes social engineering (500.14(a)).
- A written encryption policy for nonpublic information in transit and at rest (500.15).
- Written incident response and business continuity plans, tested at least once a year, with protected backups and a yearly test of restoring from them (500.16).
What you file with DFS
Within 72 hours: cybersecurity incidents
You notify DFS electronically as promptly as possible, and no later than 72 hours after determining that a cybersecurity incident has occurred at your company, an affiliate or a third-party service provider (500.17(a)). A cybersecurity incident is an event that requires notice to a government or supervisory body, has a reasonable likelihood of materially harming a material part of your normal operations, or deploys ransomware within a material part of your systems (500.1(g)).
If you make an extortion payment, notice is due within 24 hours of the payment, and a written explanation within 30 days (500.17(c)).
By April 15: certification or acknowledgment
Each year, by April 15, you submit either a certification that you materially complied with Part 500 during the prior calendar year, or an acknowledgment that you didn't. The acknowledgment names every section you didn't materially comply with, describes the gap and gives a remediation timeline or confirms it's done (500.17(b)(1)). Your highest-ranking executive and your CISO sign it, or the senior officer responsible for the program if you have no CISO. Keep the supporting records for 5 years (500.17(b)(2)-(3)).
The phase-in dates
From the regulation's transition rules (500.22) and DFS's implementation timeline for covered entities that aren't Class A companies and don't qualify for exemptions:
The limited exemption
A covered company qualifies for the limited exemption in 500.19(a) if it has any one of these:
- Fewer than 20 employees and independent contractors, counting affiliates.
- Less than $7.5 million in gross annual revenue in each of the last three fiscal years, from all of its business operations and the New York business operations of its affiliates.
- Less than $15 million in year-end total assets, including affiliates' assets.
A qualifying company is exempt from sections 500.4, 500.5, 500.6, 500.8, 500.10, 500.14(a)(1), (a)(2) and (b), 500.15 and 500.16. That takes out the CISO and governance section, the penetration testing and vulnerability management section, and the incident response and business continuity plan requirements in 500.16, among others.
The rest still applies: the program and written policies, access privileges, the risk assessment, third-party provider policies, the asset inventory and disposal, annual training, and the filings with DFS. MFA still applies to remote access to your systems, remote access to third-party apps with nonpublic information, and all privileged accounts (500.12(a)).
You file a Notice of Exemption with DFS within 30 days of determining you qualify (500.19(f)). If you stop qualifying, you have 180 days to comply with everything that applies (500.19(h)).
Two other exemptions can matter. An employee, agent or wholly owned subsidiary that is itself a covered entity is exempt to the extent another covered entity's program covers it (500.19(b)). A company that has no information systems and no nonpublic information is exempt from most sections (500.19(c)).
Where to start
Much of Part 500 overlaps with the FTC Safeguards Rule: a named security lead, a risk assessment, MFA, vendor oversight, training and an incident plan. Build the evidence once and use it for both. The 10-question Lender Security Snapshot is a quick way to see where you stand on the shared basics.
For lenders with a New York license, Part 500 support is part of the Lender vCISO service. I'll help you work out what applies, build what's missing and keep the records behind your April 15 filing.
Sources
- 23 NYCRR Part 500, Cybersecurity Requirements for Financial Services Companies (DFS)
- DFS, Cybersecurity Implementation Timeline for Covered Entities (PDF)
- New York Banking Law § 590 (Article 12-D, mortgage bankers, brokers and servicers)
Educational, not legal advice. This guide summarizes 23 NYCRR Part 500 as published by DFS and DFS's implementation timeline, checked on November 15, 2026. Rules change, and how they apply depends on your business. Talk to your counsel about your obligations.