> Data Act 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.

# Data Act vs DORA

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

[Data Act](https://grc.plus/regulation/eu-data-act/)Manufacturers and related service providers, data holders, providers of data processing services

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

## At a Glance

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

- **Data Act** Asks more on 0 topics Alone on 5 topics More detailed on 3 topics
- **DORA** Asks more on 0 topics Alone on 27 topics More detailed on 0 topics

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

- [Data Act](https://grc.plus/regulation/eu-data-act/) Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 Articles 3 to 9, 11, 13, 14, 18, 23, 25, 26, 28 to 32, 40 · 33 requirements
- [Druk nr 3266](https://grc.plus/regulation/poland-data-act-implementing-bill/) Druk nr 3266 (government bill) and Druk nr 3288 (committee report), Sejm of the Republic of Poland, 10th term 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

Data Act: Without undue delay after a simple request (Data holders); Without undue delay after the user's request (Data holders and gatekeepers designated under the Digital Markets Act); Without undue delay after a reasoned request (Data holders obliged to make data available); Decline within five working days of receipt for a public emergency, 30 working days of receipt otherwise (Data holders that are legal persons, other than public sector bodies); Notice of at most two months; transition of at most 30 calendar days after the notice period (Providers of data processing services); Retrieval for at least 30 calendar days after the end of the transitional period (Providers of data processing services); Notify within 14 working days of the switching request; alternative period of at most seven months (Providers of data processing services); No switching charges from 12 January 2027 (Providers of data processing services); Compatibility at least 12 months after publication of the references in the central Union standards repository (Providers of data processing services)

DORA: Not in the acts covered

### Threshold

Data Act: Micro and small enterprises; medium-sized for under one year; a medium-sized enterprise's products for one year after market placement (Micro and small enterprises, and medium-sized enterprises in their first year or for products in their first year on the market)

DORA: Not in the acts covered

### Goes to

Data Act: Competent authority designated under Article 37 (Data holders); User or third party in writing; competent authority notified (Data holders); Customer, before complying (Providers of data processing services)

DORA: Not in the acts covered

### Incident reports go to

Data Act: Not in the acts covered

DORA: Financial supervisor (competent authority)

### First notice of an incident

Data Act: Not in the acts covered

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

Data Act: Not in the acts covered

DORA: Within 72 hours of the initial notification

### Final report

Data Act: Not in the acts covered

DORA: Within one month of the latest intermediate report

### Deadline to have the measures in place

Data Act: Products and related services placed on the market after 12 September 2026 (Manufacturers of connected products and providers of related services)

DORA: Not in the acts covered

### Review of the risk framework

Data Act: Not in the acts covered

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

### Testing of critical systems

Data Act: Not in the acts covered

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

### Threat-led penetration testing

Data Act: 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

Data Act: Not in the acts covered

DORA: Required, for every ICT service arrangement

### Management body training

Data Act: Not in the acts covered

DORA: Required, on a regular basis

### Management body liability

Data Act: Not in the acts covered

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

### Maximum fines

Data Act: Set by each Member State; for Chapters II, III and V, data protection authorities may fine up to the GDPR Article 83(5) amount (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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

**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.15, A.5.18, A.8.2, A.8.3

Nothing in the acts covered.

- 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

**Data Act more detailed** more requirements on this, not necessarily stricter

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

- Restricting access for product security Optional
  Applies to: Data holders
  Users and data holders may agree by contract to restrict or prohibit access, use or further sharing where it could undermine the product's legal security requirements and seriously harm the health, safety or security of people. A data holder that refuses to share on this ground notifies the competent authority.
  [Data Act, Article 4(2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Protect trade secrets when sharing
  Applies to: Data holders and trade secret holders
  Identify data protected as trade secrets, including in the metadata, and agree with the user or third party proportionate technical and organisational measures to keep it confidential. Disclosure happens only once those measures are in place, and to a third party only as far as strictly necessary for the purpose agreed with the user.
  [Data Act, Articles 4(6) and 5(9)](https://grc.plus/regulation/eu-data-act/#requirements)
- Withhold or refuse data to protect trade secrets Optional
  Applies to: Data holders
  A data holder may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentiality is undermined. In exceptional cases a trade secret holder may refuse a specific request if it shows serious economic damage is highly likely. The decision is reasoned and given in writing without undue delay, and the competent authority is notified.
  [Data Act, Articles 4(7), 4(8), 5(10) and 5(11)](https://grc.plus/regulation/eu-data-act/#requirements)
- Third party limits on received data
  Applies to: Third parties receiving data at the user's request
  Process the data only for the purposes and under the conditions agreed with the user, and erase it when no longer needed for that purpose unless otherwise agreed for non-personal data. Do not make the user's choices unduly difficult, profile people unless needed for the requested service, or pass the data to another third party except under a contract with the user and with the agreed trade secret measures. Do not pass it to a gatekeeper, use it to develop a competing product or derive insights about the data holder, harm the product's security, disregard agreed trade secret measures, or stop a consumer user from sharing the data.
  [Data Act, Article 6(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Data retrieval and erasure
  Applies to: Providers of data processing services
  Specify all categories of data and digital assets that can be ported, including at least all exportable data. Give a data retrieval period of at least 30 calendar days after the transitional period, and guarantee full erasure of exportable data and digital assets after that period once switching has succeeded.
  [Data Act, Article 25(2)(e), (g) and (h)](https://grc.plus/regulation/eu-data-act/#requirements)
- Prevent unlawful governmental access
  Applies to: Providers of data processing services
  Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal data held in the Union where it would conflict with Union or national law. A third-country decision is recognised or enforceable only if it is based on an international agreement.
  [Data Act, Article 32(1) and (2)](https://grc.plus/regulation/eu-data-act/#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

- Data accessible by design and by default
  Applies to: Manufacturers of connected products and providers of related services
  Design and manufacture connected products, and design and provide related services, so that product and related service data and the metadata needed to use them are accessible to the user by default. Access is easy, secure, free of charge and in a comprehensive, structured, commonly used and machine-readable format, and direct where relevant and technically feasible. This applies to products and services placed on the market after 12 September 2026.
  [Data Act, Article 3(1)](https://grc.plus/regulation/eu-data-act/#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

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

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

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

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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

- Handling third-country access requests
  Applies to: Providers of data processing services
  Without an international agreement, give access only where the Article 32(3) conditions on reasons, review and consideration of protected interests are met. If the provider asks the competent national body for its opinion and gets no reply within one month, or the body finds the conditions are not met, the provider may reject the request. It must ask that body where national security or defence may be affected. Provide the minimum data permissible, and inform the customer before complying unless the request serves law enforcement and only for as long as needed to keep that effective.
  [Data Act, Article 32(3) to (5)](https://grc.plus/regulation/eu-data-act/#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

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

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

Nothing in the acts covered.

- 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

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

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

Nothing in the acts covered.

- 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

**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.19, A.5.21 to A.5.23

Nothing in the acts covered.

- 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

**Data Act more detailed** more requirements on this, not necessarily stricter

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

- Protect trade secrets when sharing
  Applies to: Data holders and trade secret holders
  Identify data protected as trade secrets, including in the metadata, and agree with the user or third party proportionate technical and organisational measures to keep it confidential. Disclosure happens only once those measures are in place, and to a third party only as far as strictly necessary for the purpose agreed with the user.
  [Data Act, Articles 4(6) and 5(9)](https://grc.plus/regulation/eu-data-act/#requirements)
- Limits on the data holder's own use
  Applies to: Data holders
  Use readily available non-personal data only under a contract with the user, and do not use it to derive insights that could undermine the commercial position of the user. Do not pass non-personal product data to third parties beyond fulfilling the user contract, and bind third parties not to share further. The same insight ban protects third parties unless they give a permission they can easily withdraw.
  [Data Act, Articles 4(13), 4(14) and 5(6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Fair, reasonable and non-discriminatory terms
  Applies to: Data holders obliged to make data available
  Where a business-to-business data sharing duty applies under Article 5 or other law, agree the arrangements with the data recipient on fair, reasonable and non-discriminatory terms and in a transparent manner. Terms that are unfair under Article 13, or that reduce the user's Chapter II rights to the user's detriment, are not binding.
  [Data Act, Article 8(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)
- No discrimination and no unrequested sharing
  Applies to: Data holders obliged to make data available
  Do not discriminate between comparable categories of data recipients, including partner and linked enterprises, and on a reasoned request show that no discrimination took place. Do not make data available to a recipient, including exclusively, unless the user requested it under Chapter II.
  [Data Act, Article 8(3) and (4)](https://grc.plus/regulation/eu-data-act/#requirements)
- Reasonable compensation
  Applies to: Data holders obliged to make data available
  Compensation agreed between businesses is non-discriminatory and reasonable and may include a margin, taking into account the costs of making data available and investments in collecting and producing it. For an SME or not-for-profit research organisation without larger partner or linked enterprises it does not exceed those costs of making data available. Give the recipient enough detail on the calculation to check this.
  [Data Act, Article 9(1), (2), (4) and (7)](https://grc.plus/regulation/eu-data-act/#requirements)
- Unfair terms imposed unilaterally are not binding
  Applies to: Enterprises contracting on data
  A term on data access and use, or on liability and remedies for data obligations, that one enterprise imposes unilaterally on another is not binding on that other enterprise if it is unfair. A term is unfair if its use grossly deviates from good commercial practice, contrary to good faith and fair dealing. The party that supplied the term has to prove it was not imposed unilaterally.
  [Data Act, Article 13(1), (3) and (6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Terms that are or are presumed unfair
  Applies to: Enterprises contracting on data
  Always unfair: excluding liability for intent or gross negligence, excluding remedies for non-performance, or reserving the sole right to judge conformity or interpret the contract. Presumed unfair: among others, limiting remedies inappropriately, significantly detrimental use of the other party's data, blocking its use of or copies of its own data, blocking termination within a reasonable period, terminating at unreasonably short notice, or substantially changing price or conditions without a valid reason and a right to terminate.
  [Data Act, Article 13(4) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)
- Switching terms in a written contract
  Applies to: Providers of data processing services
  Set out switching rights and obligations in a written contract, available to the customer before signing. Allow the customer to switch or port on request after a notice period of at most two months, within a transitional period of at most 30 calendar days. During the transition give reasonable assistance, keep the service running, tell the customer about known risks to continuity and keep a high level of security. Support the customer's exit strategy.
  [Data Act, Article 25(1) and (2)(a), (b) and (d)](https://grc.plus/regulation/eu-data-act/#requirements)

- 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

**Data Act more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 GV.SC

- Remove obstacles to switching
  Applies to: Providers of data processing services
  Take the measures in Articles 25, 26, 27, 29 and 30, and neither impose nor keep pre-commercial, commercial, technical, contractual or organisational obstacles to terminating the contract, signing with another provider, porting exportable data and digital assets, achieving functional equivalence, or unbundling where technically feasible.
  [Data Act, Article 23](https://grc.plus/regulation/eu-data-act/#requirements)
- Switching terms in a written contract
  Applies to: Providers of data processing services
  Set out switching rights and obligations in a written contract, available to the customer before signing. Allow the customer to switch or port on request after a notice period of at most two months, within a transitional period of at most 30 calendar days. During the transition give reasonable assistance, keep the service running, tell the customer about known risks to continuity and keep a high level of security. Support the customer's exit strategy.
  [Data Act, Article 25(1) and (2)(a), (b) and (d)](https://grc.plus/regulation/eu-data-act/#requirements)
- Data retrieval and erasure
  Applies to: Providers of data processing services
  Specify all categories of data and digital assets that can be ported, including at least all exportable data. Give a data retrieval period of at least 30 calendar days after the transitional period, and guarantee full erasure of exportable data and digital assets after that period once switching has succeeded.
  [Data Act, Article 25(2)(e), (g) and (h)](https://grc.plus/regulation/eu-data-act/#requirements)
- Longer transition where 30 days is not feasible
  Applies to: Providers of data processing services
  Where the 30 day transition is technically unfeasible, notify the customer within 14 working days of the switching request, justify it and propose an alternative period of at most seven months, keeping the service running throughout. The contract also lets the customer extend the transitional period once.
  [Data Act, Article 25(4) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)
- Information on switching
  Applies to: Providers of data processing services
  Tell the customer about available switching and porting procedures, methods, formats and known limitations, and refer it to an up-to-date online register of data structures, formats, standards and open interoperability specifications for the exportable data.
  [Data Act, Article 26](https://grc.plus/regulation/eu-data-act/#requirements)
- Withdrawal of switching charges
  Applies to: Providers of data processing services
  Charge nothing for switching from 12 January 2027. From 11 January 2024 to 12 January 2027, reduced charges may be applied, limited to the costs directly linked to the switching. Before contracting, give clear information on standard fees, early termination penalties and any reduced switching charges, and on services where switching is highly complex or costly.
  [Data Act, Article 29(1) to (6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Technical support for switching
  Applies to: Providers of data processing services
  Infrastructure providers take all reasonable measures in their power to help the customer reach functional equivalence with the destination service. Other providers offer open interfaces free of charge to customers and destination providers, and become compatible with common specifications or harmonised standards within 12 months of their publication in the central Union standards repository. Until those are published, export all exportable data in a structured, commonly used and machine-readable format on request.
  [Data Act, Article 30(1), (2), (3) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)

- 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

### Lawful processing

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

NIST Privacy Framework CT.PO-P

- Legal basis for personal data
  Applies to: Data holders
  Where the user is not the data subject, make personal data available to the user or third party only with a valid legal basis under GDPR Article 6 and, where relevant, under GDPR Article 9 and ePrivacy Article 5(3).
  [Data Act, Articles 4(12) and 5(7)](https://grc.plus/regulation/eu-data-act/#requirements)
- Third party limits on received data
  Applies to: Third parties receiving data at the user's request
  Process the data only for the purposes and under the conditions agreed with the user, and erase it when no longer needed for that purpose unless otherwise agreed for non-personal data. Do not make the user's choices unduly difficult, profile people unless needed for the requested service, or pass the data to another third party except under a contract with the user and with the agreed trade secret measures. Do not pass it to a gatekeeper, use it to develop a competing product or derive insights about the data holder, harm the product's security, disregard agreed trade secret measures, or stop a consumer user from sharing the data.
  [Data Act, Article 6(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)

Nothing in the acts covered.

### Transparency

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

NIST Privacy Framework CM.AW-P

- Pre-contract information on the data
  Applies to: Sellers, rentors and lessors of connected products, and providers of related services
  Before the contract, tell the user clearly what data the product generates or the service obtains, its type, format and estimated volume, where it is stored and for how long, and how the user can access, retrieve or erase it. Related service providers also state who the data holder is, how it intends to use the data, how to share data with a third party, the right to complain, any trade secrets, and the contract term and exit arrangements.
  [Data Act, Article 3(2) and (3)](https://grc.plus/regulation/eu-data-act/#requirements)
- Information on switching
  Applies to: Providers of data processing services
  Tell the customer about available switching and porting procedures, methods, formats and known limitations, and refer it to an up-to-date online register of data structures, formats, standards and open interoperability specifications for the exportable data.
  [Data Act, Article 26](https://grc.plus/regulation/eu-data-act/#requirements)
- Publish jurisdiction and access safeguards
  Applies to: Providers of data processing services
  Publish on the website, and keep up to date, the jurisdiction of the ICT infrastructure used for each service and a general description of the measures against international governmental access to non-personal data held in the Union where that conflicts with Union or national law. List those websites in contracts.
  [Data Act, Article 28](https://grc.plus/regulation/eu-data-act/#requirements)
- Withdrawal of switching charges
  Applies to: Providers of data processing services
  Charge nothing for switching from 12 January 2027. From 11 January 2024 to 12 January 2027, reduced charges may be applied, limited to the costs directly linked to the switching. Before contracting, give clear information on standard fees, early termination penalties and any reduced switching charges, and on services where switching is highly complex or costly.
  [Data Act, Article 29(1) to (6)](https://grc.plus/regulation/eu-data-act/#requirements)

Nothing in the acts covered.

### Rights of individuals

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

NIST Privacy Framework CT.DM-P

- Data accessible by design and by default
  Applies to: Manufacturers of connected products and providers of related services
  Design and manufacture connected products, and design and provide related services, so that product and related service data and the metadata needed to use them are accessible to the user by default. Access is easy, secure, free of charge and in a comprehensive, structured, commonly used and machine-readable format, and direct where relevant and technically feasible. This applies to products and services placed on the market after 12 September 2026.
  [Data Act, Article 3(1)](https://grc.plus/regulation/eu-data-act/#requirements)
- Give the user access to readily available data
  Applies to: Data holders
  Where the user cannot access data directly, make readily available data and metadata accessible on a simple request, without undue delay, of the same quality as the data holder has, easily, securely, free of charge and in a machine-readable format, and continuously and in real time where relevant and technically feasible. Do not make the user's choices unduly difficult, ask only for the information needed to verify the user, and keep no access logs beyond what is necessary.
  [Data Act, Article 4(1), (4) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)
- Share data with a third party at the user's request
  Applies to: Data holders and gatekeepers designated under the Digital Markets Act
  At the request of the user, or a party acting for the user, make readily available data and metadata available to a third party without undue delay, of the same quality as the data holder has, free of charge to the user and in a machine-readable format, under the terms of Articles 8 and 9. Gatekeepers under the Digital Markets Act are not eligible third parties.
  [Data Act, Article 5(1) and (3)](https://grc.plus/regulation/eu-data-act/#requirements)
- Exclusion for micro and small enterprises Optional
  Applies to: Micro and small enterprises, and medium-sized enterprises in their first year or for products in their first year on the market
  The Chapter II access and sharing obligations do not apply to data from products made or designed, or related services provided, by a micro or small enterprise, unless it has a larger partner or linked enterprise or is subcontracted to make, design or provide them. The same applies to an enterprise that has been medium-sized for less than one year, and to a medium-sized enterprise's products for one year after market placement.
  [Data Act, Article 7(1)](https://grc.plus/regulation/eu-data-act/#requirements)

Nothing in the acts covered.

### International transfers

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

- Publish jurisdiction and access safeguards
  Applies to: Providers of data processing services
  Publish on the website, and keep up to date, the jurisdiction of the ICT infrastructure used for each service and a general description of the measures against international governmental access to non-personal data held in the Union where that conflicts with Union or national law. List those websites in contracts.
  [Data Act, Article 28](https://grc.plus/regulation/eu-data-act/#requirements)
- Prevent unlawful governmental access
  Applies to: Providers of data processing services
  Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal data held in the Union where it would conflict with Union or national law. A third-country decision is recognised or enforceable only if it is based on an international agreement.
  [Data Act, Article 32(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Handling third-country access requests
  Applies to: Providers of data processing services
  Without an international agreement, give access only where the Article 32(3) conditions on reasons, review and consideration of protected interests are met. If the provider asks the competent national body for its opinion and gets no reply within one month, or the body finds the conditions are not met, the provider may reject the request. It must ask that body where national security or defence may be affected. Provide the minimum data permissible, and inform the customer before complying unless the request serves law enforcement and only for as long as needed to keep that effective.
  [Data Act, Article 32(3) to (5)](https://grc.plus/regulation/eu-data-act/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Cooperation with supervisors

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

- Restricting access for product security Optional
  Applies to: Data holders
  Users and data holders may agree by contract to restrict or prohibit access, use or further sharing where it could undermine the product's legal security requirements and seriously harm the health, safety or security of people. A data holder that refuses to share on this ground notifies the competent authority.
  [Data Act, Article 4(2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Withhold or refuse data to protect trade secrets Optional
  Applies to: Data holders
  A data holder may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentiality is undermined. In exceptional cases a trade secret holder may refuse a specific request if it shows serious economic damage is highly likely. The decision is reasoned and given in writing without undue delay, and the competent authority is notified.
  [Data Act, Articles 4(7), 4(8), 5(10) and 5(11)](https://grc.plus/regulation/eu-data-act/#requirements)
- Provide data to public bodies on an exceptional need
  Applies to: Data holders that are legal persons, other than public sector bodies
  On a duly reasoned request showing an exceptional need, make the data available to the public sector body, Commission, European Central Bank or Union body without undue delay. Decline or seek a change only on the listed grounds, within five working days for a public emergency and within 30 working days in other cases. Where declining because of an earlier request for the same purpose, name the body that made it. Anonymise personal data, or pseudonymise it where the request requires personal data.
  [Data Act, Articles 14 and 18(1) to (4)](https://grc.plus/regulation/eu-data-act/#requirements)

Nothing in the acts covered.

### Penalties and liability

**Both cover it** read the wording below

- Penalties
  Applies to: Member States
  Member States set effective, proportionate and dissuasive penalties and notify the requirements to the Commission by 12 September 2025. For Chapters II, III and V, data protection supervisory authorities may also impose fines within their competence, up to the GDPR Article 83(5) amount.
  [Data Act, Article 40(1), (2) and (4)](https://grc.plus/regulation/eu-data-act/#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 Data Act](https://grc.plus/compare/data-act/)
- [Compare DORA](https://grc.plus/compare/dora/)

Source: https://grc.plus/compare/data-act-vs-dora/
