Incident to report to a regulator?Incident to report? Intake Line

Basic Security Controls vs NYDFS Part 500

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

At a Glance

They differ on 9 of 9 topics. Each verdict names what it rests on; read the wording before relying on it.

  • Basic Security Controls Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
  • NYDFS Part 500 Asks more on 0 topics Alone on 9 topics More detailed on 0 topics
Requirements per topic and verdict
Topic Basic Security ControlsNYDFS Part 500 Verdict
Governance
Management accountability Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Security policy Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Risk management
Asset management Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Protection
Access control Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Authentication Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Detection and response
Reporting to authorities Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Security testing Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk Basic Security Controls: – NYDFS Part 500: 1 Only NYDFS Part 500no specific requirement on the other side in the acts covered

What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

Status

Reviewed against the official texts.

Included

  • NYDFS Part 500 23 NYCRR Part 500, as amended by the Second Amendment of 1 November 2023 9 requirements

Status

Reviewed against the official texts.

Governance

Management accountability

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

  • Governance

    A qualified CISOChief Information Security Officer who reports to the governing body at least yearly; the governing body oversees cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk management.

    NYDFS Part 500, 500.4

Security policy

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

Nothing in the acts covered.

  • Cybersecurity program and policies

    A program based on the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change., with written policies approved by a senior officer or the governing body; independent audits for Class A companiesA NYDFS covered entity with at least USD 20 million in gross annual revenue in each of the last two fiscal years from all its own business operations plus its affiliates' business operations in New York. It must also have either more than 2,000 employees averaged over those two years or more than USD 1 billion in gross annual revenue in each year from all business operations of the entity and its affiliates. For these tests, affiliates are included only when they share information systems, cybersecurity resources or all or part of a cybersecurity programme with the covered entity, as section 500.1(d) specifies..

    NYDFS Part 500, 500.2-500.3

Risk management

Asset management

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

Nothing in the acts covered.

Protection

Access control

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

Nothing in the acts covered.

  • Access privileges

    Least privilegeThe principle that a security architecture gives each user, process or other entity only the system authorisations and resources it needs to perform its function. It limits the damage a compromised account or component can do., yearly access reviews and privileged access managementTools and processes that manage and monitor privileged access, such as administrator rights on critical systems. CISA recommends PAM on domain controllers and notes that PAM solutions can log and alert on unusual use. for Class A companiesA NYDFS covered entity with at least USD 20 million in gross annual revenue in each of the last two fiscal years from all its own business operations plus its affiliates' business operations in New York. It must also have either more than 2,000 employees averaged over those two years or more than USD 1 billion in gross annual revenue in each year from all business operations of the entity and its affiliates. For these tests, affiliates are included only when they share information systems, cybersecurity resources or all or part of a cybersecurity programme with the covered entity, as section 500.1(d) specifies..

    NYDFS Part 500, 500.7

Authentication

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

Nothing in the acts covered.

  • Multi-factor authentication

    For any individual accessing any information systems, since 1 November 2025, with limited exceptions.

    NYDFS Part 500, 500.12

Detection and response

Reporting to authorities

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

Nothing in the acts covered.

  • Notices to DFS

    Incidents within 72 hours, extortion payments within 24 hours, and the yearly certification by 15 April.

    NYDFS Part 500, 500.17

Continuity and resilience

Business continuity and crisis management

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

Nothing in the acts covered.

  • Incident response and business continuity

    Written plans, tested at least yearly, with backupsBackup protected from unauthorised changes.

    NYDFS Part 500, 500.16

Security testing

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

Nothing in the acts covered.

  • Vulnerability management

    Penetration testingA security assessment in which authorised testers simulate attacks on an application, system or network to find weaknesses that could actually be exploited. Testing takes place within agreed limits, such as the systems included and the techniques permitted. It can reveal how several weaknesses combine to give an attacker greater access, helping an organisation understand and correct the resulting exposure. at least yearly by a qualified internal or external independent party, and automated scans.

    NYDFS Part 500, 500.5

Third parties and supply chain

Supplier and third-party risk

Only NYDFS Part 500 no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

Nothing in the acts covered.

  • Third-party service providers

    A written policy for the security of third-party service providers.

    NYDFS Part 500, 500.11

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…