• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team

2023 Amendments In Effect - New Compliance Deadlines Through 2025

NYDFS Cybersecurity Compliance

23 NYCRR 500 - New York Department of Financial Services

Navigate the nation's most rigorous financial cybersecurity regulation. Our experts guide your organization through every requirement, from gap analysis to annual certification.

An auditor and a security analyst comparing an evidence binder with a control matrix

Key 23 NYCRR 500 Requirements

Core obligations for DFS-regulated financial institutions under the cybersecurity regulation

Cybersecurity Program & Policy

Establish and maintain a cybersecurity program and written policy approved by the Board or senior officer, based on risk assessment.
  • Written Cybersecurity Policy
  • Board/Senior Officer Approval
  • Risk-Based Program Design
  • Annual Policy Review

Access Controls & MFA

Implement multi-factor authentication for all remote access, privileged accounts, and access to nonpublic information systems.
  • Multi-Factor Authentication (MFA)
  • Privileged Access Management
  • Access Privilege Reviews
  • Remote Access Controls

Monitoring & Incident Response

Continuous monitoring of information systems, 72-hour breach notification to DFS superintendent, and documented incident response plans.
  • Continuous Monitoring Systems
  • 72-Hour Breach Notification
  • Incident Response Plan
  • Annual Penetration Testing

Governance & Reporting

Designate a qualified CISO, provide annual Board reporting, file annual certification of compliance, and maintain qualified cybersecurity personnel.
  • CISO Designation Required
  • Annual Board Reporting
  • Certification of Compliance
  • Third-Party Risk Management

Who Part 500 covers

23 NYCRR Part 500 applies to any person operating, or required to operate, under a license, registration, charter or similar authorization under New York’s Banking, Insurance or Financial Services Law.

Covered entities

Banks, trust companies, insurers, insurance agents and brokers, mortgage companies, money transmitters, virtual currency businesses and other licensees. A Canadian bank branch or agency in New York, or a Canadian insurer licensed in the state, is a covered entity for that licensed business.

Limited exemptions

Fewer requirements, not none

Since the 2023 amendments, a limited exemption applies to entities with fewer than 20 employees and contractors (including affiliates), less than $7.5 million in New York revenue in each of the last three years, or less than $15 million in year-end total assets. Exempt entities still need a risk assessment, policies, access controls, MFA, an asset inventory, third-party oversight, notices and the annual filing.

Service providers

Covered by contract

Technology and other vendors to covered entities are not regulated directly, but Part 500 requires covered entities to assess vendors and set contract terms on access controls, encryption, incident notice and security. Canadian SaaS and managed service providers selling to New York insurers and banks will see these terms in contracts and questionnaires.

Individual licensees, such as insurance agents, who are covered by an affiliated entity’s program can rely on it. Exemptions must be filed with DFS. Confirm your status with counsel.

The November 2023 amendments, by date

The second amendment to Part 500 took effect on November 1, 2023, with requirements phased in over two years. By November 2025 everything was in force.
NYDFS Part 500 amendments and their effective dates
RequirementWhat changedIn force
Incident noticesNotify DFS within 72 hours of determining a reportable cybersecurity incident, including those at affiliates or third-party providers that affect you. New 24-hour notice of extortion payments.December 1, 2023
Annual certificationCertify material compliance, or file an acknowledgment of noncompliance with a remediation timeline. Signed by the CEO and the CISO.April 15, 2024 (for 2023) and every April 15
Governance and CISO reportingThe CISO reports in writing to the board at least annually. The board must have enough understanding of cyber risk to oversee it. Policies approved annually.November 1, 2024
Encryption, incident response and continuityEncryption of nonpublic information in transit and at rest (or CISO-approved compensating controls). Incident response and business continuity and disaster recovery plans tested annually.November 1, 2024
Vulnerability management and accessAutomated scans and manual review, annual review of access privileges, limits on privileged accounts, malware protection.May 1, 2025
MFA for everyoneMFA for any individual accessing any information system of the covered entity, unless the CISO approves an equivalent control in writing.November 1, 2025
Asset inventoryWritten inventory of information systems with owner, location, classification, support expiration and recovery time objective.November 1, 2025

Class A companies carry extra obligations

The amendments created a new category for the largest covered entities, with requirements that mirror what examiners already expected of big institutions.

Are you Class A?

A Class A company is a covered entity with at least $20 million in gross annual revenue from New York business in each of the last two fiscal years, and either more than 2,000 employees on average over those years or more than $1 billion in gross annual revenue in each of them. Employees and revenue of affiliates are included in the count.

The second test is what catches subsidiaries of large Canadian banks and insurers: the affiliate group’s size counts even when the New York operation is small.

What Class A companies must add

  • An independent audit of the cybersecurity program, based on risk
  • Privileged access management, with automatic blocking of commonly used passwords
  • Endpoint detection and response to spot anomalous activity
  • Centralized logging and security event alerting

Incident and extortion payment notices

The clocks are short, and they start when you determine that a reportable incident has occurred, not when it is fully understood.
  1. 72 hours: incident notice

    Notify DFS through its portal within 72 hours of determining that a cybersecurity incident has occurred that must be reported. This includes incidents that require notice to another regulator, are reasonably likely to cause material harm, or involve ransomware deployed in a material part of your systems.
  2. 24 hours: extortion payment

    If you or an affiliate makes an extortion payment in connection with a cybersecurity event, notify DFS within 24 hours of the payment.
  3. 30 days: written explanation

    Within 30 days of the payment, file a written description of why it was necessary, the alternatives considered, the diligence done to find other options and the checks against sanctions rules.

Keep updating

After the first notice, you must update DFS promptly about material changes or new information and give the information DFS requests. Rehearse the decision of when an event becomes reportable in a tabletop exercise, with the people who will sign the notice in the room.

Annual certification by April 15

Each year, covered entities file a written certification of material compliance for the previous calendar year, or an acknowledgment of noncompliance.

A certification of material compliance states that the entity complied with Part 500 in all material respects during the prior year. It must be supported by data and documentation, which you keep for five years. If the entity did not comply, it files an acknowledgment that identifies each section not met, describes the nature and extent of the gap, and gives a remediation timeline.

The certification is signed by the highest-ranking executive and the CISO (or the senior officer responsible for cybersecurity). DFS has made clear in enforcement actions that a certification filed without a sound basis is itself a violation.

Evidence worth having before you sign

  • The current risk assessment and the program it drives
  • Board minutes showing the CISO’s written report was received
  • MFA coverage evidence across every information system
  • The asset inventory and how it is kept up to date
  • Penetration test and vulnerability scan reports, with remediation
  • Incident response and continuity test records
  • Third-party service provider assessments
  • Training records, including social engineering

How ready are you for your next certification?

Ten yes, partly or no questions. You get an indicative score, your gaps grouped by area and where you sit on the path.
Readiness quick check

NYDFS Part 500 readiness quick check

Ten questions on the requirements DFS examiners focus on, including the November 2023 amendments now fully in force.

0 of 10 answeredAbout 3 minutes
  1. Question 1: Is your cybersecurity program based on a documented risk assessment that is reviewed at least annually?

    Governance

  2. Question 2: Does a qualified CISO report in writing to the board (or senior governing body) at least once a year?

    Governance

  3. Question 3: Are your cybersecurity policies approved by the board or a senior officer at least annually?

    Governance

  4. Question 4: Is MFA enforced for every individual accessing any of your information systems, including remote, third-party and privileged access?

    Access

  5. Question 5: Are privileged accounts limited, and are user access privileges reviewed at least once a year?

    Access

  6. Question 6: Do you keep a written asset inventory with owner, location, classification, support dates and recovery objectives for each asset?

    Assets and vulnerabilities

  7. Question 7: Do you run automated vulnerability scans, an annual penetration test, and fix findings by risk?

    Assets and vulnerabilities

  8. Question 8: Are activity logs monitored, with an incident response plan that has been tested in the last year?

    Detection and response

  9. Question 9: Can you notify DFS within 72 hours of determining a reportable incident, and within 24 hours of any extortion payment?

    Detection and response

  10. Question 10: Is your April 15 certification (or acknowledgment of noncompliance) backed by documented evidence for each requirement?

    Certification

Our NYDFS Compliance Process

A structured four-phase approach to achieving and maintaining 23 NYCRR 500 compliance
  1. 12-4 Weeks

    23 NYCRR 500 Gap Analysis

    Thorough assessment of your current cybersecurity program against all 23 NYCRR 500 requirements, including the 2023 amendments.
    • Current state assessment
    • Control gap identification
    • Risk assessment review
    • 2023 amendment gap analysis
  2. 24-8 Weeks

    Program Design & Remediation

    Design and document the cybersecurity program, policies, and procedures required to satisfy all regulatory requirements.
    • Cybersecurity policy development
    • CISO role establishment
    • Incident response planning
    • Third-party security policy
  3. 36-10 Weeks

    Technical Controls Implementation

    Deploy required technical controls including MFA, encryption, monitoring, vulnerability management, and access controls.
    • MFA deployment
    • Encryption implementation
    • SIEM/monitoring setup
    • Vulnerability scanning program
  4. 4Ongoing

    Certification & Continuous Compliance

    Prepare annual certification of compliance, maintain ongoing monitoring, and adapt to regulatory updates from DFS.
    • Annual certification filing
    • Penetration testing program
    • Board reporting preparation
    • Regulatory change management

Benefits of NYDFS Compliance

Strengthen your cybersecurity posture while meeting regulatory obligations
  • Avoid DFS enforcement actions and consent orders exceeding $10M+
  • Meet annual certification of compliance requirements with confidence
  • Strengthen cybersecurity posture against financial sector threats
  • Satisfy the 2023 NYDFS amendment requirements on schedule
  • Establish qualified CISO function (in-house or virtual)
  • Demonstrate regulatory compliance to customers and partners
  • Reduce cyber insurance premiums with documented controls
  • Align with NIST CSF and other frameworks for multi-standard efficiency

Who Must Comply

DFS-regulated entities required to meet 23 NYCRR 500 cybersecurity standards

Banks & Credit Unions

State-chartered banks, savings institutions, and credit unions regulated by DFS

Mortgage Companies

Mortgage brokers, bankers, and servicers licensed in New York

Insurance Companies

Property, casualty, life, and health insurers authorized in New York

Investment Firms

Licensed lenders, money transmitters, and financial service companies

Health Insurers

Health insurance providers and managed care organizations in New York

Fintech & Digital Assets

Virtual currency businesses, fintech companies, and digital asset firms licensed by DFS

Evidence, not assumptions

NYDFS Cybersecurity Compliance: evidence and assessment handoff

Readiness is preparation, not an outcome determination. The exact evidence and external review process depend on the applicable requirements and agreed scope.

Readiness support

Define the boundary, review control design, coordinate remediation and organize an evidence index. Control owners remain responsible for operating controls and supplying accurate records.

Independent audit or certification

Where applicable to NYDFS Cybersecurity Compliance, an independent auditor, assessor, certification body or authority sets its own procedures, evaluates the evidence and reaches its own conclusion. Readiness support does not replace that work or guarantee its outcome.

Evidence examples

Control design and governance

  • Approved policies, standards and procedures with version and ownership history.
  • A scope and control matrix showing requirement coverage and control owners.
  • Risk decisions, exceptions, remediation approvals and leadership review records.

Operating and technical records

  • Dated access reviews, change tickets, training completion and vulnerability follow-up.
  • Source exports for identity, MFA, logging, backup and other in-scope configurations.
  • Records that show both the review period and any gaps, failures or corrective actions.

Data, third parties and testing

  • Relevant data inventories or flow maps, vendor records and contractual control evidence.
  • Test plans and results, exercise records, incident timelines and tracked follow-up actions.
  • An evidence index linking each source item to its owner, control and assessment request.

Roles and handoff

Your control owners

Operate controls, provide authentic source evidence, explain variations and complete remediation.

GuardsArm readiness team

Map requests, review completeness and consistency, track gaps and prepare the handoff package.

Independent reviewer, where applicable

Defines its requests and procedures, evaluates evidence independently and issues conclusions within its remit.

  1. 1

    Request

    Tie each evidence request to the agreed scope, criterion, owner and review period.

  2. 2

    Collect

    Preserve source context and record dates, coverage and known limitations.

  3. 3

    Review

    Mark items ready, open or not applicable, with rationale and follow-up ownership.

  4. 4

    Hand off

    Provide the index, source access and outstanding-item log to the intended reviewer.

NYDFS Cybersecurity Regulation FAQs

Common questions about 23 NYCRR 500 compliance for financial institutions

Who must comply with 23 NYCRR 500?

The NYDFS Cybersecurity Regulation applies to all entities operating under or required to operate under a DFS license, registration, charter, certificate, permit, accreditation, or similar authorization. This includes state-chartered banks, insurance companies, mortgage companies, money transmitters, licensed lenders, virtual currency businesses, and other financial services companies regulated by DFS. Limited exemptions exist for small entities with fewer than 20 employees, under $5 million in gross annual revenue from New York operations, or under $10 million in year-end total assets.

What changed with the 2023 NYDFS amendments?

The November 2023 amendments significantly strengthened the regulation. Key changes include: enhanced governance requirements with Board oversight responsibilities, expanded CISO reporting obligations, mandatory business continuity and disaster recovery planning, stricter access privilege and MFA requirements, new requirements for asset inventory and incident notification within 72 hours, creation of a new "Class A" company category with additional obligations for larger entities (2,000+ employees or $1B+ gross revenue), and requirements for independent audits and endpoint detection for Class A companies. Compliance deadlines are phased through 2025.

What are the penalties for NYDFS non-compliance?

DFS has broad enforcement authority and can impose significant penalties for non-compliance. Notable enforcement actions include multi-million dollar consent orders: Robinhood was fined $30 million, EyeMed was fined $4.5 million, and Carnival Corporation was fined $5 million. Penalties can include monetary fines, consent orders requiring specific remediation, restrictions on business activities, revocation of licenses, and mandatory engagement of independent monitors. DFS evaluates the severity based on the nature of the violation, cooperation, and the entity's compliance history.

Does NYDFS require a dedicated CISO?

Yes, Section 500.04 requires covered entities to designate a qualified individual as CISO responsible for overseeing and implementing the cybersecurity program. The CISO must report in writing at least annually to the senior governing body (Board) on the cybersecurity program. The CISO does not need to be a full-time in-house employee; organizations may use a virtual CISO (vCISO) service or designate a qualified third-party provider to fulfill the role, provided the entity retains responsibility for compliance and maintains adequate oversight.

How does the annual certification of compliance work?

Covered entities must annually certify compliance with 23 NYCRR 500 by April 15 for the prior calendar year. The certification must be signed by the highest-ranking executive and the CISO, confirming the entity maintained a compliant cybersecurity program. If material gaps existed during the reporting period, the entity must file an acknowledgement of noncompliance identifying the areas of non-compliance and remediation timelines. Filing a false certification can result in significant enforcement action, so organizations should conduct thorough internal assessments before filing.

Still Have Questions?

Our cybersecurity experts are here to help. Get personalized answers and a free security consultation.

Related Compliance Services

Complementary services to strengthen your NYDFS compliance program

SOC 2 Compliance

Trust service criteria assessments complementing NYDFS cybersecurity controls.
Learn More

Penetration Testing

Annual penetration testing required under 23 NYCRR 500 Section 500.05.
Learn More

vCISO Services

Qualified CISO function to meet the NYDFS CISO designation requirement.
Learn More

Incident Response

72-hour breach notification readiness and incident response planning.
Learn More

Achieve NYDFS Cybersecurity Compliance

With DFS enforcement intensifying and the 2023 amendments introducing stricter requirements, ensure your financial institution meets every obligation under 23 NYCRR 500.