Regulation · Financial services · New York
NYDFS 500 compliance: the amended Part 500 requirements explained
NYDFS 500 compliance means meeting 23 NYCRR Part 500, the New York Department of Financial Services cybersecurity regulation for banks, insurers and other licensed entities. The 2023 amendment phased in through 1 November 2025, adding universal MFA and asset inventories, and every covered entity certifies compliance by 15 April each year.
What you need to know about NYDFS 500
Who must comply with NYDFS 500?
Entities licensed or chartered under New York banking, insurance or financial services law.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does NYDFS Part 500 require?
NYDFS Part 500 requires a risk-based cybersecurity program with a CISO and board oversight, technical controls including universal MFA and an asset inventory, tested incident and continuity plans, fast incident reporting and an annual signed certification.
Program and governance
Program, policies, CISO, board oversight.
In QULDEX: Governance evidenceTechnical controls
Testing, access, MFA, assets, encryption.
In QULDEX: Controls mapped to NIST CSFThird-party providers
Assess and manage vendors.
In QULDEX: Vendor registerIR and continuity
Plans tested yearly.
In QULDEX: Test results storedNotices and certification
72 h, 24 h, 15 April.
In QULDEX: Timers and certification packWhich Part 500 sections matter most?
These 17 sections carry the obligations most covered entities work on. Select any section to see what it requires, typical evidence and the matching NIST CSF or ISO 27001 reference.
Showing up to 6 per group. Search, filter, or open a group to see all 17.
Governance 4
500.2Cybersecurity programMaintain a risk-based cybersecurity program; Class A companies also need independent audits of it.
In QULDEXQULDEX gives this section an owner, evidence requests and a review date, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Program documentation
- Maps to
- NIST CSF GV
500.3Cybersecurity policyBoard-approved policies covering listed areas, reviewed at least yearly.
In QULDEXQULDEX gives this section an owner, evidence requests and a review date, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Approved policies
- Maps to
- ISO 27001 A.5.1
500.4Cybersecurity governanceA CISO who reports to the board at least yearly; senior governing body oversight with sufficient expertise.
In QULDEXCISO reports and board minutes are evidence.
- Typical evidence
- CISO report, minutes
- Maps to
- NIST CSF GV.RR
500.9Risk assessmentReview and update the risk assessment at least yearly and on material change.
In QULDEXThe risk register is versioned yearly.
- Typical evidence
- Risk assessment
- Maps to
- ISO 27001 6.1
Technical controls 7
500.5Vulnerability managementAnnual penetration tests and automated vulnerability scans, with timely remediation.
In QULDEXFindings become CAPA items with due dates.
- Typical evidence
- Pen test, scan reports
- Maps to
- ISO 27001 A.8.8
500.7Access privileges and managementLimit privileged accounts, review access at least yearly, and control remote access.
In QULDEXAccess reviews run as recurring tasks.
- Typical evidence
- Access reviews
- Maps to
- ISO 27001 A.5.15–A.5.18
500.12Multi-factor authenticationPhased in 2025MFA for any individual accessing any information system, from 1 November 2025, with limited CISO-approved exceptions.
In QULDEXMFA coverage is tracked per system.
- Typical evidence
- MFA settings
- Maps to
- ISO 27001 A.8.5
500.13Asset management and data retentionPhased in 2025A complete, documented asset inventory with owner, location, classification, support end date and RTO, from 1 November 2025.
In QULDEXThe asset inventory holds the required fields.
- Typical evidence
- Asset inventory
- Maps to
- ISO 27001 A.5.9
500.14Monitoring and trainingMonitor user activity, protect against malicious code, and train staff annually including on social engineering.
In QULDEXQULDEX gives this section an owner, evidence requests and a review date, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Training records
- Maps to
- ISO 27001 A.6.3
500.15EncryptionEncrypt nonpublic information in transit and at rest, or use CISO-approved compensating controls.
In QULDEXQULDEX gives this section an owner, evidence requests and a review date, and maps it to NIST CSF and ISO 27001.
- Typical evidence
- Encryption evidence
- Maps to
- ISO 27001 A.8.24
500.11Third-party service provider securityPolicies to assess and manage third-party providers that hold or access nonpublic information.
In QULDEXEach provider is assessed and linked to its services.
- Typical evidence
- Vendor assessments
- Maps to
- ISO 27001 A.5.19–A.5.22
Response and reporting 4
500.16Incident response and business continuityWritten incident response, business continuity and disaster recovery plans, tested at least yearly, with backups protected.
In QULDEXPlan tests and results are stored per year.
- Typical evidence
- IR and BCDR plans, test results
- Maps to
- ISO 22301
500.17(a)Notice of cybersecurity incidentNotify NYDFS within 72 hours of determining that a reportable cybersecurity incident occurred.
In QULDEXIncidents start a 72-hour timer.
- Typical evidence
- Incident notices
- Maps to
- NIS2 Art. 23
500.17(c)Notice of extortion paymentNotify NYDFS within 24 hours of an extortion payment, and give a written justification within 30 days.
In QULDEXExtortion payments start 24-hour and 30-day timers.
- Typical evidence
- Payment notice, justification
500.17(b)Annual certificationPhased in 2025Submit a certification of compliance, or an acknowledgment of noncompliance, by 15 April each year, signed by the CEO and CISO.
In QULDEXThe certification is prepared from live evidence.
- Typical evidence
- Annual certification
Scope and enforcement 2
500.20EnforcementA single act or failure, or failing to comply for 24 hours, can be a violation; NYDFS considers listed factors when setting penalties.
In QULDEXQULDEX gives this section an owner, evidence requests and a review date, and maps it to NIST CSF and ISO 27001.
500.1Class A companiesCompanies with at least $20 million in New York revenue and over 2,000 employees or $1 billion in revenue, with extra duties such as independent audits.
In QULDEXQULDEX gives this section an owner, evidence requests and a review date, and maps it to NIST CSF and ISO 27001.
Nothing matches that search.
Section numbers follow 23 NYCRR Part 500 as amended on 1 November 2023. Summaries are QULDEX paraphrases, not legal advice.
How do you comply with NYDFS 500 each year?
Keep the program and risk assessment current, prove the technical controls, test the plans, report incidents on time and certify by 15 April.
Update the risk assessment
At least yearly and on material change.
Confirm MFA and asset inventory
Universal MFA and a complete inventory with the required fields.
Test and scan
Annual penetration test and regular vulnerability scans.
Test IR and BCDR plans
At least yearly, with results recorded.
CISO report to the board
At least yearly.
Certify by 15 April
Every incidentNotify within 72 hoursAny extortion paymentNotify within 24 hours15 AprilCertification or acknowledgment
Dates follow the amended regulation. Durations are QULDEX planning ranges.
Which documents does NYDFS 500 need?
NYDFS examiners ask for these records, and the certification rests on them.
| Document | Section | Where it lives in QULDEX |
|---|---|---|
| Cybersecurity program and policies | 500.2–500.3 | Policy library |
| CISO annual report to the board | 500.4 | Policy library |
| Risk assessment | 500.9 | Risk register |
| Pen test and scan reports | 500.5 | CAPA automation |
| Access reviews | 500.7 | Evidence vault |
| MFA coverage evidence | 500.12 | Evidence vault |
| Asset inventory | 500.13 | Risk register |
| IR and BCDR plans and tests | 500.16 | Evidence vault |
| Incident and extortion notices | 500.17 | CAPA automation |
| Annual certification and supporting evidence | 500.17(b) | Audit workspace |
Section numbers follow 23 NYCRR Part 500 as amended.
How much effort does NYDFS 500 take?
Keeping compliant is an annual cycle. Universal MFA, the asset inventory and third-party management usually take the most work.
Where the time goes
Bars compare relative effort across an annual cycle.
What changes the effort
- Class A status: adds independent audits
- Legacy systems: MFA exceptions need CISO approval
- Vendors: third-party assessments
- Existing NIST CSF or ISO 27001: covers much of the program
- Prior findings: examiners revisit them
How ready are you for NYDFS 500?
Check these eight things first. Nothing you enter leaves this page.
How NYDFS 500 maps to NIST CSF, ISO 27001 and SOX ITGC
Part 500 lines up closely with NIST CSF and ISO 27001; access and change controls overlap with SOX ITGC testing at listed companies.
NYDFS crosswalk
| NYDFS Part 500 | NIST CSF 2.0 | ISO 27001:2022 | SOX ITGC | Shared evidence |
|---|---|---|---|---|
| 500.4 Governance | GV.RR | 5.3 | — | CISO report |
| 500.7 Access | PR.AA | A.5.15–A.5.18 | Access reviews | Review sign-offs |
| 500.12 MFA | PR.AA-03 | A.8.5 | Authentication | MFA settings |
| 500.13 Assets | ID.AM | A.5.9 | Scoping | Inventory |
| 500.5 Testing | ID.RA | A.8.8 | — | Scan reports |
| 500.16 IR and BCDR | RS, RC | A.5.24–A.5.30 | Backup and recovery | Plan tests |
| 500.11 Vendors | GV.SC | A.5.19–A.5.22 | SOC 1 | Vendor register |
Indicative mapping for planning.
How QULDEX runs NYDFS 500 from risk assessment to certification
QULDEX is NYDFS 500 compliance and audit management software built from EGV Group's audit delivery, used by covered entities, their advisors and auditors. Pick your role to see who does what.
For NYDFS-licensed banks, insurers and financial firms.
- RiskUpdate the risk assessmentVersioned risk register
- ControlsProve MFA and inventoryCoverage tracked per system
- TestRun testsPen test and scan findings into CAPA
- ReportNotify NYDFS72 h and 24 h timers
- BoardReport to the boardCISO report from live data
- CertifyCertify by 15 AprilCertification pack from evidence
For NYDFS consultants and internal audit.
- RiskRun the gap assessmentA reusable Part 500 template
- ControlsReview evidenceReview states
- TestTrack remediationDue dates
- ReportAdviseDecision records
- BoardBrief the boardBoard pack
- CertifyPrepareReadiness check
For independent auditors, including Class A audits.
- RiskPlanScope in a standard format
- ControlsSampleView-only evidence with download control and an access log
- TestRetestRetest evidence
- ReportReviewIncident history
- BoardReviewMinutes on record
- CertifyAuditFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →NYDFS 500 questions people ask
Who must comply with NYDFS Part 500?
Entities operating under a licence, registration or charter under New York banking, insurance or financial services law, with limited exemptions for small entities.
What changed in the 2023 amendment?
The amendment added Class A companies, stronger governance and board oversight, extortion payment notices, universal MFA and asset inventory requirements, phased in through 1 November 2025.
When is the NYDFS annual certification due?
By 15 April each year, covering the previous calendar year. It is either a certification of compliance or an acknowledgment of noncompliance, signed by the CEO and CISO.
What must be reported to NYDFS and how fast?
Reportable cybersecurity incidents within 72 hours of determining they occurred, and any extortion payment within 24 hours, with a written justification within 30 days.
What is a Class A company under Part 500?
A covered entity with at least $20 million in gross annual New York revenue and either over 2,000 employees or over $1 billion in gross annual revenue, including affiliates.
Go deeper on NYDFS 500
Audit evidence naming convention
A file-naming scheme examiners can follow.
blog.quldex.comAudit sampling size for compliance
How many samples auditors look at.
blog.quldex.comNIST CSF 2.0: the Govern function explained
The governance outcomes Part 500 now expects.
blog.quldex.comNIST & CIS topic hub
NIST CSF, 800-53 and CIS Controls articles.
References
- 23 NYCRR Part 500, as amended 1 Nov 2023. dfs.ny.gov
- NYDFS guidance on requirements effective 1 Nov 2025. dfs.ny.gov
- Hogan Lovells, final Part 500 requirements effective 1 Nov 2025. hoganlovells.com
- NIST CSF 2.0. nist.gov
Reviewed by
Page history
- : Page first built on the amended regulation: section explorer, annual cycle and readiness check
Certify on 15 April with evidence behind it
Answer a short readiness check and get a gap summary by section. No sales call needed to see the result.