> CRA 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.

# CRA vs DORA

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

[CRA](https://grc.plus/regulation/cyber-resilience-act-cra/)Manufacturers of products with digital elements

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

## At a Glance

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

- **CRA** Asks more on 0 topics Alone on 2 topics More detailed on 4 topics
- **DORA** Asks more on 1 topic Alone on 13 topics More detailed on 7 topics

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

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

- [CRA](https://grc.plus/regulation/cyber-resilience-act-cra/) Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 Articles 13 to 16, 19 to 22, 28, 30 to 32, 64 · Annex · 42 requirements
- [CRA Product Categories](https://grc.plus/regulation/cra-implementing-regulation-product-categories/) Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 on the technical description of the categories of important and critical products with digital elements pursuant to Regulation (EU) 2024/2847 of the European Parliament and of the Council (OJ L, 2025/2392, 1.12.2025) Articles 2, 7, 8, 32 · Annex · 4 requirements
- [Kamerstuk 36875](https://grc.plus/regulation/netherlands-cra-implementation-act/) Kamerstukken 36875, Regels ter uitvoering van Verordening (EU) 2024/2847 (Uitvoeringswet verordening cyberweerbaarheid), voorstel van wet (36875, nr. 2) and memorie van toelichting (36875, nr. 3) Articles 1 to 3, 5, 7 · 5 requirements
- [S.L. 591.06](https://grc.plus/regulation/malta-cyber-resilience-regulations/) L.N. 238 of 2026, Cyber Resilience Regulations, 2026, made under article 58 of the Malta Digital Innovation Authority Act (Cap. 591); Government Gazette No. 21,717, 11 September 2026; S.L. 591.06 4 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

CRA: Final report within 14 days of a corrective or mitigating measure being available

DORA: Not in the acts covered

### Threshold

CRA: Harm to protection of sensitive or important data or functions, or malicious code

DORA: Not in the acts covered

### Goes to

CRA: Manufacturer and market surveillance authorities (Importers); Manufacturer and market surveillance authorities (Distributors)

DORA: Not in the acts covered

### Evidence to keep

CRA: Documented risk assessment in the technical documentation; EU declaration of conformity, at least 10 years or the support period if longer (Importers); Technical documentation and EU declaration, at least 10 years or the support period if longer; Software bill of materials

DORA: Not in the acts covered

### Incident reports go to

CRA: Coordinating CSIRT and ENISA, via the single reporting platform; Coordinating CSIRT and ENISA, via the single reporting platform; Coordinating CSIRT of the main establishment and ENISA

DORA: Financial supervisor (competent authority)

### First notice of an incident

CRA: Within 24 hours of becoming aware; 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

### Incident notification

CRA: Within 72 hours of becoming aware; Within 72 hours of becoming aware

DORA: Not in the acts covered

### Intermediate report

CRA: On request of the coordinating CSIRT; On request of the coordinating CSIRT

DORA: Within 72 hours of the initial notification

### Final report

CRA: Within one month of the incident notification

DORA: Within one month of the latest intermediate report

### External assessment or certification

CRA: Module A, modules B and C, module H, or an EU certification scheme; Third-party assessment or certification, depending on class (Manufacturers of important and critical products)

DORA: Not in the acts covered

### Review of the risk framework

CRA: Not in the acts covered

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

### Testing of critical systems

CRA: Not in the acts covered

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

### Threat-led penetration testing

CRA: 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

CRA: Not in the acts covered

DORA: Required, for every ICT service arrangement

### Management body training

CRA: Not in the acts covered

DORA: Required, on a regular basis

### Management body liability

CRA: Not in the acts covered

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

### Maximum fines

CRA: Up to EUR 15,000,000 or 2.5% of worldwide annual turnover, whichever is higher (Manufacturers); Up to EUR 10,000,000 or 2% of worldwide annual turnover, whichever is higher (Economic operators and others subject to the listed articles); Up to EUR 5,000,000 or 1% of worldwide annual turnover, whichever is higher (Economic operators)

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

- When others become the manufacturer
  Applies to: Importers and distributors who sell a product under their own name or trademark or substantially modify it, and others who substantially modify a product
  An importer or distributor that sells a product under its own name or trademark, or substantially modifies it, is treated as the manufacturer and is subject to Articles 13 and 14. Any other person who substantially modifies a product and makes it available is also a manufacturer, for the affected part or the whole product if its overall cybersecurity is affected.
  [CRA, Articles 21, 22](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

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

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

- Cybersecurity risk assessment
  Assess the product's cybersecurity risks and use the result across planning, design, development, production, delivery and maintenance. Document it, update it during the support period, base it on intended and foreseeable use, and include it in the technical documentation with a justification for any requirement that does not apply.
  [CRA, Article 13(2) to (4)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

- Correct non-conformity
  If you know or have reason to believe the product or your processes do not meet Annex I, immediately take corrective measures, or withdraw or recall the product as appropriate.
  [CRA, Article 13(21)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- EU declaration of conformity
  Once conformity is shown, draw up the EU declaration, following the Annex V structure, and supply it or a simplified version with the product. Use a single declaration where several Union acts apply. By drawing it up you assume responsibility for the product's compliance.
  [CRA, Articles 13(12), (20), 28](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Technical documentation
  Draw up technical documentation with at least the Annex VII elements before placing the product on the market and update it as needed, at least during the support period. Keep it and the EU declaration available to the market surveillance authorities for at least 10 years after the product is placed on the market, or for the support period if longer.
  [CRA, Articles 13(13), 31(1), (2)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Choose a conformity route
  Assess the product and your processes against Annex I using internal control (module A), EU-type examination with conformity to type (modules B and C), full quality assurance (module H), or a European cybersecurity certification scheme where available and applicable.
  [CRA, Article 32(1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Third-party assessment by product class
  Applies to: Manufacturers of important and critical products
  Important products in class I use modules B and C or module H unless harmonised standards, common specifications or a scheme at assurance level substantial were fully applied. Class II use modules B and C, module H or a scheme at that level. Critical products use a certification scheme under Article 8(1), or the class II procedures where its conditions are not met.
  [CRA, Article 32(2) to (4)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

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

- Software bill of materials
  Identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.
  [CRA, Annex I, Part II, point (1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

- Protect against unauthorised access
  Where applicable, protect against unauthorised access with appropriate controls such as authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

**Both cover it** read the wording below

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

- Protect against unauthorised access
  Where applicable, protect against unauthorised access with appropriate controls such as authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

**Both cover it** read the wording below

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

- Confidentiality and integrity of data
  Where applicable, protect the confidentiality of stored, transmitted or processed data, such as by state-of-the-art encryption at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.
  [CRA, Annex I, Part I, point (2)(e), (f)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

**Both cover it** read the wording below

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

- Confidentiality and integrity of data
  Where applicable, protect the confidentiality of stored, transmitted or processed data, such as by state-of-the-art encryption at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.
  [CRA, Annex I, Part I, point (2)(e), (f)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Minimise data and allow removal
  Where applicable, process only data that is adequate, relevant and limited to the product's purpose. Let users securely and easily remove all data and settings permanently, and make any transfer to other products secure.
  [CRA, Annex I, Part I, point (2)(g), (m)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

**Both cover it** read the wording below

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

- Meet the essential requirements
  When placing a product on the market, ensure it was designed, developed and produced in line with the cybersecurity requirements in Annex I, Part I.
  [CRA, Article 13(1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- No known vulnerabilities, secure by default and reduced attack surface
  Where applicable on the basis of the risk assessment, supply the product without known exploitable vulnerabilities and with a secure-by-default configuration that can be reset. Limit attack surfaces and reduce the impact of incidents with exploitation mitigation.
  [CRA, Annex I, Part I, point (2)(a), (b), (j), (k)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

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

- Keep security updates available
  Keep each security update issued during the support period available for at least 10 years after it is issued, or for the rest of the support period if longer.
  [CRA, Article 13(9)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Test, fix and disclose vulnerabilities
  Remediate vulnerabilities without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosure policy, provide a reporting contact, and publish information on fixed vulnerabilities.
  [CRA, Annex I, Part II, points (2) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

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

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

- Third-party components
  Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a vulnerability in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.
  [CRA, Article 13(5), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Set and state the support period
  Handle vulnerabilities effectively for a support period that reflects expected use and is at least five years, or the expected use time if shorter. State the end date, at least month and year, clearly at the time of purchase, and notify users when support ends where technically feasible.
  [CRA, Article 13(8), (19)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Report actively exploited vulnerabilities
  Notify any actively exploited vulnerability you become aware of to the coordinating CSIRT and ENISA at the same time. Send an early warning within 24 hours and a vulnerability notification with general information and mitigations within 72 hours. Send a final report describing the vulnerability, any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRT may ask for an intermediate report.
  [CRA, Article 14(1), (2), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer corrective action and alerts
  Applies to: Importers
  Hold back non-conforming products and take corrective measures, withdraw or recall those already placed. Inform the manufacturer of any vulnerability without undue delay, and where a product presents a significant cybersecurity risk, immediately inform the market surveillance authorities.
  [CRA, Article 19(3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor corrective action and alerts
  Applies to: Distributors
  Make sure corrective measures, withdrawal or recall take place for non-conforming products. Inform the manufacturer of any vulnerability without undue delay. Immediately inform market surveillance authorities of a significant cybersecurity risk. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.
  [CRA, Article 20(4), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Software bill of materials
  Identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.
  [CRA, Annex I, Part II, point (1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Test, fix and disclose vulnerabilities
  Remediate vulnerabilities without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosure policy, provide a reporting contact, and publish information on fixed vulnerabilities.
  [CRA, Annex I, Part II, points (2) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#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)
- 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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

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

- Record and monitor activity
  Where applicable, provide security-related information by recording and monitoring relevant internal activity, including access to or changes of data, services or functions, with a user opt-out.
  [CRA, Annex I, Part I, point (2)(l)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

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

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

Nothing in the acts covered.

- 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

- When an incident is severe
  Treat an incident as severe if it harms or could harm the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or if it has introduced or could introduce malicious code into the product or a user's systems.
  [CRA, Article 14(5)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

- Report actively exploited vulnerabilities
  Notify any actively exploited vulnerability you become aware of to the coordinating CSIRT and ENISA at the same time. Send an early warning within 24 hours and a vulnerability notification with general information and mitigations within 72 hours. Send a final report describing the vulnerability, any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRT may ask for an intermediate report.
  [CRA, Article 14(1), (2), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Report severe incidents
  Notify any severe incident affecting the product's security to the coordinating CSIRT and ENISA at the same time. Send an early warning within 24 hours stating whether unlawful or malicious acts are suspected, and an incident notification with an initial assessment and mitigations within 72 hours. Send a final report with the root cause and measures within one month of the incident notification. The coordinating CSIRT may ask for an intermediate report.
  [CRA, Article 14(3), (4), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Reporting route
  Submit notifications through ENISA's single reporting platform, using the end-point of the coordinating CSIRT in the Member State of your main establishment. Manufacturers without one follow the order in Article 14(7). You may ask for dissemination of a sensitive notification to be delayed on justified cybersecurity grounds.
  [CRA, Articles 14(7), 16(1), (2)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Voluntary reporting Optional
  Applies to: Manufacturers and any other natural or legal person
  Any person may voluntarily notify a coordinating CSIRT or ENISA of vulnerabilities, cyber threats, incidents and near misses. Doing so creates no additional obligations for the person notifying.
  [CRA, Article 15(1), (2), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

NIST CSF 2.0 RS.CO, RC.CO

- Set and state the support period
  Handle vulnerabilities effectively for a support period that reflects expected use and is at least five years, or the expected use time if shorter. State the end date, at least month and year, clearly at the time of purchase, and notify users when support ends where technically feasible.
  [CRA, Article 13(8), (19)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Product identity, contact point and instructions
  Give the product a type, batch or serial number and show your name and contact details. Designate a single point of contact for users that is not limited to automated tools. Supply the Annex II information and instructions and keep them available for at least 10 years or the support period, whichever is longer.
  [CRA, Article 13(15) to (18)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Cooperate with authorities and announce cessation
  On a reasoned request, give the market surveillance authority the information needed to show conformity and cooperate on measures to remove risks. If you are ceasing operations and cannot comply, inform the authorities and, as far as possible, users before this takes effect.
  [CRA, Article 13(22), (23)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Inform users
  After becoming aware of an actively exploited vulnerability or severe incident, inform impacted users, and where appropriate all users, and tell them about mitigations they can deploy, where appropriate in a structured, machine-readable format.
  [CRA, Article 14(8)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

- Voluntary reporting Optional
  Applies to: Manufacturers and any other natural or legal person
  Any person may voluntarily notify a coordinating CSIRT or ENISA of vulnerabilities, cyber threats, incidents and near misses. Doing so creates no additional obligations for the person notifying.
  [CRA, Article 15(1), (2), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

- Availability of essential functions
  Where applicable, protect the availability of essential and basic functions, also after an incident, including resilience against denial-of-service attacks. Minimise the product's negative impact on services provided by other devices or networks.
  [CRA, Annex I, Part I, point (2)(h), (i)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

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

- Test, fix and disclose vulnerabilities
  Remediate vulnerabilities without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosure policy, provide a reporting contact, and publish information on fixed vulnerabilities.
  [CRA, Annex I, Part II, points (2) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- 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

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

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

- Third-party components
  Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a vulnerability in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.
  [CRA, Article 13(5), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer checks
  Applies to: Importers
  Place on the market only products and manufacturer processes that meet Annex I. First ensure the conformity assessment and technical documentation exist, the product has CE marking, EU declaration and instructions, and the identification and support-date duties are met. Show your own contact details on the product, its packaging or an accompanying document.
  [CRA, Article 19(1), (2), (4)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor checks and cooperation
  Applies to: Distributors
  Act with due care. Before making a product available, verify the CE marking and that the manufacturer and importer met their identification, instruction, support-date and declaration duties. Hold back non-conforming products and cooperate with the authority on reasoned request.
  [CRA, Article 20(1), (2), (3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Software bill of materials
  Identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.
  [CRA, Annex I, Part II, point (1)](https://grc.plus/regulation/cyber-resilience-act-cra/#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)

## Privacy and data protection

### Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

- Minimise data and allow removal
  Where applicable, process only data that is adequate, relevant and limited to the product's purpose. Let users securely and easily remove all data and settings permanently, and make any transfer to other products secure.
  [CRA, Annex I, Part I, point (2)(g), (m)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Cooperation with supervisors

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

- Cooperate with authorities and announce cessation
  On a reasoned request, give the market surveillance authority the information needed to show conformity and cooperate on measures to remove risks. If you are ceasing operations and cannot comply, inform the authorities and, as far as possible, users before this takes effect.
  [CRA, Article 13(22), (23)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer corrective action and alerts
  Applies to: Importers
  Hold back non-conforming products and take corrective measures, withdraw or recall those already placed. Inform the manufacturer of any vulnerability without undue delay, and where a product presents a significant cybersecurity risk, immediately inform the market surveillance authorities.
  [CRA, Article 19(3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer records and cooperation
  Applies to: Importers
  Keep the EU declaration of conformity for at least 10 years after the product is placed on the market, or for the support period if longer, and ensure the technical documentation can be made available on request. Provide information to the authority on reasoned request and cooperate. If the manufacturer has ceased operations, inform the authorities and, where possible, users.
  [CRA, Article 19(6) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor checks and cooperation
  Applies to: Distributors
  Act with due care. Before making a product available, verify the CE marking and that the manufacturer and importer met their identification, instruction, support-date and declaration duties. Hold back non-conforming products and cooperate with the authority on reasoned request.
  [CRA, Article 20(1), (2), (3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor corrective action and alerts
  Applies to: Distributors
  Make sure corrective measures, withdrawal or recall take place for non-conforming products. Inform the manufacturer of any vulnerability without undue delay. Immediately inform market surveillance authorities of a significant cybersecurity risk. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.
  [CRA, Article 20(4), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Technical documentation
  Draw up technical documentation with at least the Annex VII elements before placing the product on the market and update it as needed, at least during the support period. Keep it and the EU declaration available to the market surveillance authorities for at least 10 years after the product is placed on the market, or for the support period if longer.
  [CRA, Articles 13(13), 31(1), (2)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Fines for misleading information
  Applies to: Economic operators
  Supplying incorrect, incomplete or misleading information to notified bodies and market surveillance authorities in reply to a request carries fines of up to EUR 5 million or 1% of total worldwide annual turnover, whichever is higher.
  [CRA, Article 64(4)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

### Penalties and liability

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

- Fines for essential requirements and reporting
  Applies to: Manufacturers
  Breach of Annex I or of Articles 13 and 14 carries fines of up to EUR 15 million or 2.5% of total worldwide annual turnover, whichever is higher. Micro and small enterprises are not fined for missing the 24-hour early warning, and open-source software stewards are not fined for any infringement.
  [CRA, Article 64(2), (10)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Fines for other operator obligations
  Applies to: Economic operators and others subject to the listed articles
  Breach of Articles 18 to 23, 28, 30(1) to (4), 31(1) to (4), 32(1) to (3), 33(5) and certain other listed articles carries fines of up to EUR 10 million or 2% of total worldwide annual turnover, whichever is higher.
  [CRA, Article 64(3)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Fines for misleading information
  Applies to: Economic operators
  Supplying incorrect, incomplete or misleading information to notified bodies and market surveillance authorities in reply to a request carries fines of up to EUR 5 million or 1% of total worldwide annual turnover, whichever is higher.
  [CRA, Article 64(4)](https://grc.plus/regulation/cyber-resilience-act-cra/#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 CRA](https://grc.plus/compare/cra/)
- [Compare DORA](https://grc.plus/compare/dora/)

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