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

# CER vs DORA

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

[CER](https://grc.plus/regulation/critical-entities-resilience-directive-cer/)Critical entities identified by Member States

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

## At a Glance

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

- **CER** Asks more on 0 topics Alone on 2 topics More detailed on 1 topic
- **DORA** Asks more on 0 topics Alone on 16 topics More detailed on 4 topics

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

- [CER](https://grc.plus/regulation/critical-entities-resilience-directive-cer/) Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022 Articles 6, 8, 12 to 17, 21, 22 · 29 requirements

Status

Reviewed against the official texts.

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.

## Key Numbers

### Deadline

CER: By 17 July 2026 (Member States); Member State notifies within one month of identification (Member States); Within nine months of receiving the notification; Central authorities reply within 10 working days of receiving the request (Member States); Rules notified to the Commission by 17 October 2024 (Member States)

DORA: Not in the acts covered

### How often

CER: List reviewed at least every four years (Member States); Whenever necessary, and at least every four years

DORA: Not in the acts covered

### Threshold

CER: Actual or potential significant disruption of essential services; Essential services to or in six or more Member States

DORA: Not in the acts covered

### Goes to

CER: Competent authority

DORA: Not in the acts covered

### Evidence to keep

CER: Resilience plan or equivalent documents; Information and evidence on the Article 13 measures (Critical entities that are also entities under Directive (EU) 2022/2555)

DORA: Not in the acts covered

### Incident reports go to

CER: Competent authority

DORA: Financial supervisor (competent authority)

### First notice of an incident

CER: Within 24 hours of becoming aware

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

### Intermediate report

CER: Not in the acts covered

DORA: Within 72 hours of the initial notification

### Final report

CER: Within one month of the initial notification, where relevant

DORA: Within one month of the latest intermediate report

### Deadline to have the measures in place

CER: 10 months after the date of the notification (Member States)

DORA: Not in the acts covered

### External assessment or certification

CER: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entities that are also entities under Directive (EU) 2022/2555)

DORA: Not in the acts covered

### Review of the risk framework

CER: Not in the acts covered

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

### Testing of critical systems

CER: Not in the acts covered

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

### Threat-led penetration testing

CER: Not in the acts covered

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

### Register of third-party arrangements

CER: Not in the acts covered

DORA: Required, for every ICT service arrangement

### Management body training

CER: Not in the acts covered

DORA: Required, on a regular basis

### Management body liability

CER: Not in the acts covered

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

### Maximum fines

CER: Set by each Member State; effective, proportionate and dissuasive (Member States)

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

## Governance

### Management accountability

**Only DORA** 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.

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

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

- Liaison officer
  Designate a liaison officer or equivalent as the point of contact with the competent authorities.
  [CER, Article 13(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Security policy

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

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

- Resilience plan
  Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 13(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Awareness and training

**Both cover it** read the wording below

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

- Raise staff awareness
  Raise awareness of the resilience measures among relevant personnel, considering training courses, information materials and exercises.
  [CER, Article 13(1)(f)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

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

- Proportionate measures and incident prevention
  Take appropriate and proportionate technical, security and organisational measures to ensure resilience, based on the Member State risk assessment and the entity's own. The measures include preventing incidents, with due regard to disaster risk reduction and climate adaptation.
  [CER, Article 13(1), opening words and point (a)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Encouraging standards
  Applies to: Member States
  Where useful, and without imposing or favouring a particular technology, Member States encourage the use of European and international standards and technical specifications relevant to the security and resilience measures of critical entities. The article places no duty on the entity itself to use them.
  [CER, Article 16](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

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

- Carry out a critical entity risk assessment
  Carry out a risk assessment within nine months of being notified as a critical entity, then whenever necessary and at least every four years. Assess all relevant risks that could disrupt the provision of the essential services, using the Member State risk assessments and other relevant sources of information.
  [CER, Article 12(1)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- All-hazards scope and dependencies
  Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 12(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Review, audit and improvement

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

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

- Inspections, audits and remedial orders
  Applies to: Competent authorities
  Competent authorities can inspect critical infrastructure and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entities. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
  [CER, Article 21(1) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Provide information and audit evidence
  Applies to: Critical entities that are also entities under Directive (EU) 2022/2555
  Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
  [CER, Article 21(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Asset management

**Only DORA** 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.

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

## Protection

### Access control

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

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

- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Authentication

**Only DORA** 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.

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

### Cryptography and encryption

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

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

Nothing in the acts covered.

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

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

Nothing in the acts covered.

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

### Network security

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

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

Nothing in the acts covered.

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

### Secure acquisition and development

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

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

Nothing in the acts covered.

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

### Configuration, change and patch management

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

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

Nothing in the acts covered.

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

### Vulnerability handling

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

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

Nothing in the acts covered.

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

### Human resources security

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

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

- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Request background checks where permitted Optional
  Under conditions set by the Member State and in duly reasoned cases, the entity may request background checks on people in sensitive roles, people with direct or remote access to its premises, information or control systems, and candidates for those positions.
  [CER, Article 14(1)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Limits and content of background checks
  Applies to: Member States
  Checks are proportionate, strictly limited to what is necessary and carried out only to evaluate a potential security risk to the entity. At a minimum they confirm the person's identity and check criminal records for offences relevant to the position. Central authorities answer requests for criminal records held in other Member States within 10 working days.
  [CER, Article 14(2) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### 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 protection of premises and infrastructure
  Ensure adequate physical protection of premises and critical infrastructure, considering for example fencing, barriers, perimeter monitoring, detection equipment and access controls.
  [CER, Article 13(1)(b)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

## Detection and response

### Monitoring and detection

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

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

Nothing in the acts covered.

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

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

- Respond to and mitigate incidents
  Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
  [CER, Article 13(1)(c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

**Both cover it** read the wording below

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

- Judging the significance of a disruption
  Determine significance by taking into account in particular the number and proportion of users affected, the duration of the disruption, and the geographical area affected, including whether it is geographically isolated.
  [CER, Article 15(1)(a) to (c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Reporting to authorities

**Both cover it** read the wording below

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

- Initial incident notification
  Notify the competent authority without undue delay of incidents that significantly disrupt, or could significantly disrupt, the provision of essential services. Send the initial notification within 24 hours of becoming aware of the incident, unless operationally unable to do so.
  [CER, Article 15(1), first subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Detailed incident report
  Where relevant, follow the initial notification with a detailed report within one month.
  [CER, Article 15(1), first subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Content of the notification
  Include any available information that lets the competent authority understand the nature, cause and possible consequences of the incident, including any cross-border impact. Notifying does not expose the entity to increased liability.
  [CER, Article 15(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Informing customers and the public

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO, RC.CO

- Follow-up to the entity and informing the public
  Applies to: Competent authorities and Member States
  After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
  [CER, Article 15(4)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Threat intelligence and information sharing

**Both cover it** read the wording below

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

- Follow-up to the entity and informing the public
  Applies to: Competent authorities and Member States
  After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
  [CER, Article 15(4)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

## Continuity and resilience

### Business continuity and crisis management

**Both cover it** read the wording below

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

- Respond to and mitigate incidents
  Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
  [CER, Article 13(1)(c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Recover and resume the essential service
  Recover from incidents and resume the essential service, considering business continuity measures and alternative supply chains.
  [CER, Article 13(1)(d)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Resilience plan
  Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 13(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Backup and recovery

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

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

Nothing in the acts covered.

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

### Security testing

**Only DORA** 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.

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

### Threat-led penetration testing

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

NIST CSF 2.0 ID.IM

Nothing in the acts covered.

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

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

- All-hazards scope and dependencies
  Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 12(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Recover and resume the essential service
  Recover from incidents and resume the essential service, considering business continuity measures and alternative supply chains.
  [CER, Article 13(1)(d)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

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

Nothing in the acts covered.

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

### Register of third-party arrangements

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

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

### Exit and termination

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

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

## Supervision and enforcement

### Registration with authorities

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

- Identification of critical entities
  Applies to: Member States
  Each Member State identifies the critical entities in the sectors and subsectors of the Annex by 17 July 2026 and reviews the list at least every four years. An entity qualifies when it provides an essential service, operates on that territory with its critical infrastructure located there, and an incident would significantly disrupt that service or a dependent one.
  [CER, Article 6(1), (2) and (5)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Notification and start of obligations
  Applies to: Member States
  The Member State notifies each critical entity within one month of identifying it and tells it which obligations apply and from when. The resilience obligations in Chapter III apply to the entity from 10 months after the date of that notification.
  [CER, Article 6(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Carve-out for banking, financial market and digital infrastructure
  Applies to: Member States, for critical entities in banking, financial market infrastructure and digital infrastructure
  Article 11 and Chapters III, IV and VI do not apply to critical entities identified in banking, financial market infrastructure and digital infrastructure (points 3, 4 and 8 of the Annex). Member States may keep or adopt national requirements for a higher level of resilience if they are consistent with Union law.
  [CER, Article 8](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Report services in six or more Member States
  After being notified as a critical entity, tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
  [CER, Article 17(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

### Cooperation with supervisors

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

- Liaison officer
  Designate a liaison officer or equivalent as the point of contact with the competent authorities.
  [CER, Article 13(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Report services in six or more Member States
  After being notified as a critical entity, tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
  [CER, Article 17(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Inspections, audits and remedial orders
  Applies to: Competent authorities
  Competent authorities can inspect critical infrastructure and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entities. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
  [CER, Article 21(1) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Provide information and audit evidence
  Applies to: Critical entities that are also entities under Directive (EU) 2022/2555
  Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
  [CER, Article 21(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

### Penalties and liability

**Both cover it** read the wording below

- Penalties
  Applies to: Member States
  Member States lay down the penalties for infringements of the national measures and take the steps needed to implement them. The penalties are effective, proportionate and dissuasive. Member States notify the Commission of these provisions by 17 October 2024 and of any later change without delay.
  [CER, Article 22](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

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 CER](https://grc.plus/compare/cer/)
- [Compare DORA](https://grc.plus/compare/dora/)

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