> DORA vs NIS2 side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# DORA vs NIS2

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

[DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/)Financial entities

[NIS2](https://grc.plus/regulation/nis2/)Essential and important entities

## At a Glance

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

- **DORA** Asks more on 1 topic Alone on 4 topics More detailed on 8 topics
- **NIS2** Asks more on 0 topics Alone on 2 topics More detailed on 1 topic

| Topic | DORA | NIS2 | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Roles and independence | DORA: 1 | NIS2: 1 | **Both cover it**read the wording below |
| Security policy | DORA: 3 | NIS2: 2 | **Both cover it**read the wording below |
| Awareness and training | DORA: 2 | NIS2: 2 | **Both cover it**read the wording below |
| Risk management |  |  |  |
| Risk management framework | DORA: 2 | NIS2: 3 | **Both cover it**read the wording below |
| Risk assessment | DORA: 3 | NIS2: 2 | **Both cover it**read the wording below |
| Review, audit and improvement | DORA: 4 | NIS2: 3 | **Both cover it**read the wording below |
| Asset management | DORA: 3 | NIS2: 2 | **Both cover it**read the wording below |
| Protection |  |  |  |
| Access control | DORA: 3 | NIS2: 2 | **Both cover it**read the wording below |
| Authentication | DORA: 2 | NIS2: 2 | **Both cover it**read the wording below |
| Cryptography and encryption | DORA: 2 | NIS2: 1 | **Both cover it**read the wording below |
| Data security | DORA: 3 | NIS2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Network security | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Secure communications | DORA: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Secure acquisition and development | DORA: 2 | NIS2: 1 | **Both cover it**read the wording below |
| Configuration, change and patch management | DORA: 5 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Vulnerability handling | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Human resources security | DORA: 1 | NIS2: 2 | **Both cover it**read the wording below |
| Physical and environmental security | DORA: 1 | NIS2: 2 | **Both cover it**read the wording below |
| Detection and response |  |  |  |
| Monitoring and detection | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Incident handling | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Incident classification | DORA: 1 | NIS2: 3 | **NIS2 more detailed**more requirements on this, not necessarily stricter |
| Reporting to authorities | DORA: 5 | NIS2: 5 | **Both cover it**read the wording below |
| Informing customers and the public | DORA: 2 | NIS2: 2 | **Both cover it**read the wording below |
| Threat intelligence and information sharing | DORA: 2 | NIS2: 1 | **DORA asks more**binding, where the other is optional |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Backup and recovery | DORA: 1 | NIS2: 2 | **Both cover it**read the wording below |
| Security testing | DORA: 3 | NIS2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Threat-led penetration testing | DORA: 1 | NIS2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | DORA: 2 | NIS2: 2 | **Both cover it**read the wording below |
| Contract requirements | DORA: 2 | NIS2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Register of third-party arrangements | DORA: 1 | NIS2: 1 | **Both cover it**read the wording below |
| Exit and termination | DORA: 1 | NIS2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | DORA: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Penalties and liability | DORA: 1 | NIS2: 2 | **Both cover it**read the wording below |

## 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

- [DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/) Regulation (EU) 2022/2554 Articles 5, 6, 8 to 14, 16 to 19, 24 to 26, 28, 30, 45, 50 · 43 requirements
- [DORA ICT Risk Management RTS](https://grc.plus/regulation/dora-rts-ict-risk-management/) Commission Delegated Regulation (EU) 2024/1774 Articles 2 to 31, 33 to 41 · 26 requirements Applies to: Financial entities, except those on the simplified framework
- [JC 2024 34](https://grc.plus/regulation/dora-guidelines-incident-costs-and-losses/) Joint Guidelines on the estimation of aggregated annual costs and losses caused by major ICT-related incidents under Regulation (EU) 2022/2554, JC 2024 34 (Final Report of 17 July 2024), issued under Article 11(11) of Regulation (EU) 2022/2554 5 requirements

Not yet included

- [DORA Third-Party Policy RTS](https://grc.plus/regulation/dora-rts-ict-third-party-policy/)
- [DORA Subcontracting RTS](https://grc.plus/regulation/dora-rts-subcontracting/)
- [DORA Register of Information ITS](https://grc.plus/regulation/dora-its-register-of-information/)
- [DORA Incident Classification RTS](https://grc.plus/regulation/dora-rts-incident-classification/)
- [DORA Incident Reporting RTS](https://grc.plus/regulation/dora-rts-incident-reporting/)
- [DORA Incident Reporting ITS](https://grc.plus/regulation/dora-its-incident-reporting-templates/)
- [DORA TLPT RTS](https://grc.plus/regulation/dora-rts-tlpt/)
- [DORA Critical Provider Criteria](https://grc.plus/regulation/dora-da-critical-provider-criteria/)
- [DORA Oversight Conditions RTS](https://grc.plus/regulation/dora-rts-oversight-conditions/)

Status

Reviewed against the official texts.

Included

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

Status

Reviewed against the official texts.

## Key Numbers

### Incident reports go to

DORA: Financial supervisor (competent authority)

NIS2: CSIRT or competent authority

### First notice of an incident

DORA: Within 4 hours of classifying it as major, and no later than 24 hours of becoming aware; if classified as major after that, within 4 hours of classifying it

NIS2: Without undue delay and in any event within 24 hours of becoming aware

### Incident notification

DORA: Not in the acts covered

NIS2: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

### Intermediate report

DORA: Within 72 hours of the initial notification

NIS2: On request

### Final report

DORA: Within one month of the latest intermediate report

NIS2: Within one month of the incident notification

### Review of the risk framework

DORA: At least once a year (periodically for microenterprises), and after major incidents

NIS2: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Testing of critical systems

DORA: At least yearly, for systems supporting critical or important functions

NIS2: Not in the acts covered

### Threat-led penetration testing

DORA: At least every 3 years, for entities the authority identifies; the authority may request a lower or higher frequency

NIS2: Not in the acts covered

### Register of third-party arrangements

DORA: Required, for every ICT service arrangement

NIS2: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Registration with the authority

DORA: Not in the acts covered

NIS2: Required; changes without delay and in any event within two weeks

### Management body training

DORA: Required, on a regular basis

NIS2: Required

### Management body liability

DORA: Ultimate responsibility for ICT risk; penalties on members are subject to national law (Article 50(5))

NIS2: Yes, for infringements of Article 21

### Maximum fines

DORA: Set by each Member State (Competent authorities and Member States)

NIS2: Essential entities: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entities: maximum of at least EUR 7 million or 1.4%, whichever is higher.

## Governance

### Management accountability

**DORA more detailed** more requirements on this, not necessarily stricter

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

- Management body responsibility
  The management body defines, approves, oversees and is responsible for implementing every arrangement of the ICT risk management framework, and bears ultimate responsibility for managing ICT risk.
  [DORA, Article 5(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Budget for resilience
  The management body allocates and reviews the budget for digital operational resilience, including awareness programmes, training and ICT skills for all staff.
  [DORA, Article 5(2)(g)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Governance (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Governance and organisation of the simplified ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 28](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements)

### Roles and independence

**Both cover it** read the wording below

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

- Independent control function
  A control function with appropriate independence manages and oversees ICT risk (not required of microenterprises). Risk management, control and internal audit functions are kept appropriately segregated and independent.
  [DORA, Article 6(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Roles, responsibilities and authorities
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Security policy

**Both cover it** read the wording below

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

- Information security policy
  A documented information security policy with requirements to protect the availability, authenticity, integrity and confidentiality of data and assets, including customers' where applicable.
  [DORA, Article 9(4)(a)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT security policies
  Applies to: Financial entities, except those on the simplified framework
  ICT security policies, procedures, protocols and tools, with their general elements, approved and reviewed as part of the framework.
  [DORA ICT Risk Management RTS, Article 2](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Information security policy (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An information security policy and measures.
  [DORA ICT Risk Management RTS, Article 29](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- Network and information system security policy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A security policy approved by the management body, reviewed at least annually and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Awareness and training

**Both cover it** read the wording below

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Management body training
  Members of the management body keep their knowledge and skills on ICT risk up to date, including by following specific training regularly.
  [DORA, Article 5(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Staff awareness and training
  ICT security awareness programmes and digital operational resilience training are compulsory for all employees and senior management.
  [DORA, Article 13(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Management body training
  Members of the management body follow training to identify risks and assess cybersecurity risk-management practices. Entities are encouraged to offer similar training to employees regularly.
  [NIS2, Article 20(2)](https://grc.plus/regulation/nis2/#requirements)
- Cyber hygiene and training
  Basic cyber hygiene practices and cybersecurity training.
  [NIS2, Article 21(2)(g)](https://grc.plus/regulation/nis2/#requirements)

## Risk management

### Risk management framework

**Both cover it** read the wording below

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

- ICT risk management framework
  A sound, comprehensive and well-documented ICT risk management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICT assets.
  [DORA, Article 6(1) and (2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Simplified ICT risk management framework
  Applies to: Entities on the simplified framework (DORA Article 16)
  Small and non-interconnected investment firms, exempted payment and e-money institutions, small occupational pension funds, and institutions exempted under Directive 2013/36/EU that their Member State has not excluded under Article 2(4) follow a simplified framework instead of Articles 5 to 15.
  [DORA, Article 16(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Appropriate and proportionate measures
  Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.
  [NIS2, Article 21(1)](https://grc.plus/regulation/nis2/#requirements)
- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Risk assessment

**Both cover it** read the wording below

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

- Identify ICT risk
  Identify all sources of ICT risk continuously, assess cyber threats and vulnerabilities, and review risk scenarios at least yearly.
  [DORA, Article 8(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT risk management policy
  Applies to: Financial entities, except those on the simplified framework
  A policy and procedures for ICT risk management: risk tolerance, identification, assessment and treatment of risks, and the monitoring of residual risk.
  [DORA ICT Risk Management RTS, Article 3](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT risk management (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Identification and management of ICT risk.
  [DORA ICT Risk Management RTS, Article 31](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Review, audit and improvement

**Both cover it** read the wording below

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

- Yearly review of the framework
  The framework is documented and reviewed at least once a year (periodically for microenterprises), after major ICT-related incidents and following supervisory instructions or conclusions from testing or audits, and improved continuously.
  [DORA, Article 6(5)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Internal audit
  Auditors with sufficient ICT risk expertise audit the framework regularly, in line with the audit plan. Not required of microenterprises.
  [DORA, Article 6(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Report on the framework review
  Applies to: Financial entities, except those on the simplified framework
  The format and content of the report on the review of the ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 27](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Framework review report (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  The format and content of the report on the review of the simplified framework.
  [DORA ICT Risk Management RTS, Article 41](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Assessing effectiveness
  Policies and procedures to assess whether the cybersecurity risk-management measures work.
  [NIS2, Article 21(2)(f)](https://grc.plus/regulation/nis2/#requirements)
- Corrective measures
  An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
  [NIS2, Article 21(4)](https://grc.plus/regulation/nis2/#requirements)
- Independent review
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Independent reviews of network and information security at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Asset management

**Both cover it** read the wording below

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

- Identify and classify assets
  Identify, classify and document all ICT-supported business functions, information and ICT assets and their dependencies, and review the classification at least yearly.
  [DORA, Article 8(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT asset management
  Applies to: Financial entities, except those on the simplified framework
  An ICT asset management policy and procedure, including an inventory of assets and their criticality.
  [DORA ICT Risk Management RTS, Articles 4 and 5](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Asset classification (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Classification of information assets and ICT assets.
  [DORA ICT Risk Management RTS, Article 30](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Asset management
  Asset management.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Asset inventory
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.
  [NIS2 Implementing Regulation, Annex, point 12.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

## Protection

### Access control

**Both cover it** read the wording below

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

- Limit access
  Limit physical and logical access to what legitimate and approved functions need, with policies, procedures and controls for access rights.
  [DORA, Article 9(4)(c)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Access control (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Access control.
  [DORA ICT Risk Management RTS, Article 33](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Access control policies
  Access control policies.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Access rights and privileged accounts
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Management of access rights, and stricter controls on privileged and system administration accounts.
  [NIS2 Implementing Regulation, Annex, points 11.2 and 11.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Authentication

**Both cover it** read the wording below

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

- Strong authentication and key protection
  Strong authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Multi-factor authentication
  Multi-factor or continuous authentication solutions, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements)
- Multi-factor authentication
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Multi-factor or continuous authentication where appropriate, in line with the classification of the asset accessed.
  [NIS2 Implementing Regulation, Annex, point 11.7](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Cryptography and encryption

**Both cover it** read the wording below

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

- Strong authentication and key protection
  Strong authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Encryption and key management
  Applies to: Financial entities, except those on the simplified framework
  Encryption and cryptographic controls, and the management of cryptographic keys through their whole life cycle.
  [DORA ICT Risk Management RTS, Articles 6 and 7](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Cryptography
  Policies and procedures on the use of cryptography and, where appropriate, encryption.
  [NIS2, Article 21(2)(h)](https://grc.plus/regulation/nis2/#requirements)

### Data security

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

- Protect data
  Policies, protocols and tools that keep data available, authentic, intact and confidential at rest, in use and in transit.
  [DORA, Article 9(2) and (3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT operations and data security
  Applies to: Financial entities, except those on the simplified framework
  Policies and procedures for ICT operations, capacity and performance management, and data and system security.
  [DORA ICT Risk Management RTS, Articles 8, 9 and 11](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

Nothing in the acts covered.

### Network security

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

- Network and infrastructure management
  Network and infrastructure management on a risk basis, designed so that connections can be severed or segmented instantly to stop contagion.
  [DORA, Article 9(4)(b)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Network security
  Applies to: Financial entities, except those on the simplified framework
  Network security management and the protection of information in transit.
  [DORA ICT Risk Management RTS, Articles 13 and 14](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Network security and segmentation
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.
  [NIS2 Implementing Regulation, Annex, points 6.7 and 6.8](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Secure communications

**Only NIS2** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14

Nothing in the acts covered.

- Secured communications
  Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements)

### Secure acquisition and development

**Both cover it** read the wording below

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

- Projects, acquisition and development
  Applies to: Financial entities, except those on the simplified framework
  ICT project management, and the acquisition, development and maintenance of ICT systems.
  [DORA ICT Risk Management RTS, Articles 15 and 16](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements)

### Configuration, change and patch management

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

- Change management
  Documented change management, so that every change to software, hardware, firmware, systems or security parameters is recorded, tested, assessed, approved, implemented and verified.
  [DORA, Article 9(4)(e)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT change management
  Applies to: Financial entities, except those on the simplified framework
  ICT change management procedures.
  [DORA ICT Risk Management RTS, Article 17](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Configuration, change and patch management
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurity benefits and the reasons are documented.
  [NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Vulnerability handling

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements)

### Human resources security

**Both cover it** read the wording below

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

- Human resources policy
  Applies to: Financial entities, except those on the simplified framework
  A human resources policy covering ICT security.
  [DORA ICT Risk Management RTS, Article 19](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Human resources security
  Human resources security.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Background verification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.
  [NIS2 Implementing Regulation, Annex, point 10.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Physical and environmental security

**Both cover it** read the wording below

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

- Physical and environmental security
  Applies to: Financial entities, except those on the simplified framework
  A physical and environmental security policy.
  [DORA ICT Risk Management RTS, Article 18](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Physical and environmental security
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Supporting utilities, protection against physical and environmental threats, and perimeter and physical access control.
  [NIS2 Implementing Regulation, Annex, points 13.1 to 13.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

## Detection and response

### Monitoring and detection

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

- Detect anomalous activity
  Mechanisms to detect anomalous activity promptly, with several layers of control, alert thresholds and automatic alerts, tested regularly.
  [DORA, Article 10](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Logging
  Applies to: Financial entities, except those on the simplified framework
  Logging procedures, protocols and tools: what is logged, how logs are protected and how long they are kept.
  [DORA ICT Risk Management RTS, Article 12](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Monitoring and logging
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Monitoring and logging of network and information systems to detect events that could be incidents.
  [NIS2 Implementing Regulation, Annex, point 3.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Incident handling

**DORA more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

- Post-incident reviews
  A review after a major ICT-related incident disrupts core activities, to find the causes and the improvements needed.
  [DORA, Article 13(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management process
  A process to detect, manage and notify ICT-related incidents: record all incidents and significant cyber threats, assign roles, escalate, and find and fix root causes.
  [DORA, Article 17](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Incident handling
  Procedures to handle incidents.
  [NIS2, Article 21(2)(b)](https://grc.plus/regulation/nis2/#requirements)

### Incident classification

**NIS2 more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

- Classify incidents
  Classify incidents by the clients affected, reputational impact, duration, geographical spread, data losses, critical services affected and economic impact. The thresholds are in Delegated Regulation (EU) 2024/1772.
  [DORA, Article 18(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- When an incident is significant
  An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.
  [NIS2, Article 23(3)](https://grc.plus/regulation/nis2/#requirements)
- Event assessment and classification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.
  [NIS2 Implementing Regulation, Annex, point 3.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)
- When an incident is significant
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).
  [NIS2 Implementing Regulation, Articles 3 to 14](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Reporting to authorities

**Both cover it** read the wording below

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

- Report major incidents
  Report major ICT-related incidents to the competent authority, using the common templates.
  [DORA, Article 19(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Initial notification
  An initial notification once the incident is classified as major.
  [DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Intermediate report
  An intermediate report, updated when regular activities have been recovered.
  [DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Final report
  A final report once the root cause analysis is complete, whether or not mitigation is in place, and actual impact figures are available to replace estimates.
  [DORA, Article 19(4)(c); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Voluntary notice of cyber threats Optional
  Significant cyber threats may be notified to the competent authority.
  [DORA, Article 19(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Notify significant incidents
  Notify the CSIRT or competent authority without undue delay of any significant incident, with the information needed to judge any cross-border impact.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements)
- Early warning
  An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
  [NIS2, Article 23(4)(a)](https://grc.plus/regulation/nis2/#requirements)
- Incident notification
  An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
  [NIS2, Article 23(4)(b)](https://grc.plus/regulation/nis2/#requirements)
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements)
- Final report
  A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
  [NIS2, Article 23(4)(d) and (e)](https://grc.plus/regulation/nis2/#requirements)

### Informing customers and the public

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO, RC.CO

- Crisis communication
  Crisis communication plans to disclose major incidents or vulnerabilities to clients, counterparts and the public, and a person in charge of public and media communication.
  [DORA, Article 14](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Inform affected clients
  When a major incident affects clients' financial interests, inform them without undue delay of the incident and the measures taken.
  [DORA, Article 19(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Inform affected recipients
  Where appropriate, notify recipients of the services without undue delay of significant incidents likely to affect the provision of those services.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements)
- Warn of significant cyber threats
  Where applicable, tell recipients potentially affected by a significant cyber threat, without undue delay, what they can do about it and, where appropriate, about the threat itself.
  [NIS2, Article 23(2)](https://grc.plus/regulation/nis2/#requirements)

### Threat intelligence and information sharing

**DORA asks more** binding, where the other is optional

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

- Threat and vulnerability intelligence
  Capabilities and staff to gather information on vulnerabilities, cyber threats and incidents and to analyse their likely impact.
  [DORA, Article 13(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Information-sharing arrangements Optional
  Financial entities may exchange cyber threat information within trusted communities, under arrangements that protect confidentiality and personal data. They must tell the competent authority when they join or leave.
  [DORA, Article 45](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Information-sharing arrangements Optional
  Entities may exchange cybersecurity information such as threats, vulnerabilities and indicators of compromise within information-sharing arrangements. Essential and important entities notify the competent authority when they join or withdraw.
  [NIS2, Article 29](https://grc.plus/regulation/nis2/#requirements)

## Continuity and resilience

### Business continuity and crisis management

**DORA more detailed** more requirements on this, not necessarily stricter

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

- ICT business continuity
  An ICT business continuity policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functions, and a business impact analysis.
  [DORA, Article 11](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT business continuity
  Applies to: Financial entities, except those on the simplified framework
  The components of the ICT business continuity policy, the testing of continuity plans, and ICT response and recovery plans.
  [DORA ICT Risk Management RTS, Articles 24 to 26](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Business continuity (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An ICT business continuity plan and its testing.
  [DORA ICT Risk Management RTS, Articles 39 and 40](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)

### Backup and recovery

**Both cover it** read the wording below

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

- Backup and restoration
  Backup policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICT capacity (microenterprises assess the need based on their risk profile).
  [DORA, Article 12](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)
- Backup and redundancy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Backup copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.
  [NIS2 Implementing Regulation, Annex, point 4.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Security testing

**DORA more detailed** more requirements on this, not necessarily stricter

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

- Resilience testing programme
  A risk-based testing programme run by independent testers, with all ICT systems and applications supporting critical or important functions tested at least yearly. Not required of microenterprises.
  [DORA, Article 24](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Security testing (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT security testing.
  [DORA ICT Risk Management RTS, Article 36](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Security testing
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A policy and procedures for security testing of network and information systems.
  [NIS2 Implementing Regulation, Annex, point 6.5](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Threat-led penetration testing

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM

- Threat-led penetration testing
  Entities identified by the competent authority, other than microenterprises and Article 16(1) entities, run threat-led penetration tests on live production systems. Details are in Delegated Regulation (EU) 2025/1190.
  [DORA, Article 26(1), (2) and (8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

## Third parties and supply chain

### Supplier and third-party risk

**Both cover it** read the wording below

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

- Manage ICT third-party risk
  ICT third-party risk is managed within the ICT risk management framework, and the entity stays fully responsible for compliance.
  [DORA, Article 28(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Third-party risk strategy
  A regularly reviewed strategy on ICT third-party risk, with a policy on ICT services supporting critical or important functions. The management body regularly reviews the risks from those arrangements. Not required of microenterprises or Article 16 entities.
  [DORA, Article 28(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Supply chain security
  Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
  [NIS2, Article 21(2)(d)](https://grc.plus/regulation/nis2/#requirements)
- What to weigh for each supplier and service provider
  Entities weigh the specific vulnerabilities of each direct supplier and service provider, the quality of their products and cybersecurity practices, including secure development, and the results of EU coordinated risk assessments of critical supply chains.
  [NIS2, Article 21(3)](https://grc.plus/regulation/nis2/#requirements)

### Contract requirements

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

- Minimum contract terms
  Contracts set out the services, locations of service and data, data protection, access and return of data, service levels, incident assistance, cooperation with authorities, termination rights and participation in training.
  [DORA, Article 30(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Terms for critical or important functions
  Contracts for services supporting critical or important functions add full service level descriptions, notice periods, business contingency plans, participation in TLPT, unrestricted rights of access, inspection and audit (microenterprises may agree to delegate these to an independent third party), and exit strategies with a transition period.
  [DORA, Article 30(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

### Register of third-party arrangements

**Both cover it** read the wording below

NIST CSF 2.0 GV.SC

- Register of information
  A register of all contractual arrangements for ICT services, at entity, sub-consolidated and consolidated level, given to the competent authority on request, with a report at least yearly on new arrangements and timely notice of planned arrangements supporting critical or important functions.
  [DORA, Article 28(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Directory of suppliers
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A directory of direct suppliers and service providers, kept up to date.
  [NIS2 Implementing Regulation, Annex, point 5.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Exit and termination

**Only DORA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

- Exit strategies
  Exit strategies for ICT services supporting critical or important functions, covering provider failure, falling quality and business disruption.
  [DORA, Article 28(8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Registration with authorities

**Only NIS2** no specific requirement on the other side in the acts covered

Nothing in the acts covered.

- Register with the authority
  Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.
  [NIS2, Article 3(4)](https://grc.plus/regulation/nis2/#requirements)
- Registry of digital providers
  DNS, TLD, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISA registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
  [NIS2, Article 27](https://grc.plus/regulation/nis2/#requirements)

### Penalties and liability

**Both cover it** read the wording below

- Administrative penalties
  Applies to: Competent authorities and Member States
  Competent authorities have supervisory, investigatory and sanctioning powers; Member States set the administrative penalties and remedial measures.
  [DORA, Article 50](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements)
- Administrative fines
  Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
  [NIS2, Article 34(4) and (5)](https://grc.plus/regulation/nis2/#requirements)

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.

## More Comparisons

- [Compare DORA](https://grc.plus/compare/dora/)
- [Compare NIS2](https://grc.plus/compare/nis2/)

Source: https://grc.plus/compare/dora-vs-nis2/
