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

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 ActManufacturers and related service providers, data holders, providers of data processing services

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

Status

Reviewed against the official texts.

Key Numbers

Deadline

Data Act: Without undue delay after a simple request (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.); Without undue delay after the user's request (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and gatekeepersAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions. designated under the Digital Markets ActRegulation (EU) 2022/1925, an EU law intended to make digital markets fairer and easier for businesses to enter and compete in. It sets duties for providers that the European Commission designates as gatekeepers for specified core platform services, such as app stores or online search. Business users and end users benefit from the requirements even when they are not gatekeepers themselves. The DMA is separate from the Digital Services Act.); Without undue delay after a reasoned request (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available); Decline within five working days of receipt for a public emergency, 30 working days of receipt otherwise (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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 servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); Retrieval for at least 30 calendar days after the end of the transitional period (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); Notify within 14 working days of the switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. request; alternative period of at most seven months (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); No switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. charges from 12 January 2027 (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.); Compatibility at least 12 months after publication of the references in the central Union standards repository (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.)

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 holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.); User or third party in writing; competent authority notified (Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.); Customer, before complying (Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.)

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 servicesRelated Service (Data Act) placed on the market after 12 September 2026 (Manufacturers of connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets. and providers of related servicesRelated Service (Data Act))

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 microenterprisesMicroenterprise Under DORA), 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 functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these 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 ICTInformation and Communication Technology 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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment.; 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 authoritiesData Protection Authority may fine up to the GDPRGeneral Data Protection Regulation 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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and bears ultimate responsibility for managing ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..

    DORA, Article 5(2)

  • Budget for resilience

    The management body allocates and reviews the budget for digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA., including awareness programmes, training and ICTInformation and Communication Technology skills for all staff.

    DORA, Article 5(2)(g)

  • Governance (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Governance and organisation of the simplified ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.

    DORA ICT Risk Management RTS, Article 28

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. (not required of microenterprisesMicroenterprise Under DORA). Risk management, control and internal audit functions are kept appropriately segregated and independent.

    DORA, Article 6(4)

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 availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity and confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of data and assets, including customers' where applicable.

    DORA, Article 9(4)(a)

  • ICT security policies

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology 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

  • Information security policy (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    An information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy and measures.

    DORA ICT Risk Management RTS, Article 29

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. up to date, including by following specific training regularly.

    DORA, Article 5(4)

  • Staff awareness and training

    ICTInformation and Communication Technology security awareness programmes and digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA. training are compulsory for all employees and senior management.

    DORA, Article 13(6)

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICTInformation and Communication Technology assets.

    DORA, Article 6(1) and (2)

  • Simplified ICT risk management framework

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Small and non-interconnected investment firms, exempted payment and e-moneyElectronic 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)

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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. continuously, assess cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., and review risk scenarios at least yearly.

    DORA, Article 8(2)

  • ICT risk management policy

    Applies to: Financial entities, except those on the simplified framework

    A policy and procedures for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management: risk toleranceAn organisation's or other actor's readiness to bear a risk in order to achieve its objectives. Risk tolerance can be shaped by legal or regulatory requirements and changes with context, so frameworks ask organisations to state it rather than prescribing it., identification, assessment and treatment of risks, and the monitoring of residual riskThe risk that remains after risk treatment has been applied. The NIST AI RMF notes that residual risk directly affects end users and affected communities, and asks system providers to document it so users understand the possible negative impacts..

    DORA ICT Risk Management RTS, Article 3

  • ICT risk management (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Identification and management of ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..

    DORA ICT Risk Management RTS, Article 31

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 microenterprisesMicroenterprise Under DORA), after major ICT-related incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. and following supervisory instructions or conclusions from testing or audits, and improved continuously.

    DORA, Article 6(5)

  • Internal audit

    Auditors with sufficient ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. expertise audit the framework regularly, in line with the audit plan. Not required of microenterprisesMicroenterprise Under DORA.

    DORA, Article 6(6)

  • 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 riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.

    DORA ICT Risk Management RTS, Article 27

  • Framework review report (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    The format and content of the report on the review of the simplified framework.

    DORA ICT Risk Management RTS, Article 41

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 ICTInformation and Communication Technology-supported business functions, information and ICTInformation and Communication Technology assets and their dependencies, and review the classification at least yearly.

    DORA, Article 8(1)

  • ICT asset management

    Applies to: Financial entities, except those on the simplified framework

    An ICTInformation and Communication Technology asset managementAsset Management in Information Security policy and procedure, including an inventory of assets and their criticality.

    DORA ICT Risk Management RTS, Articles 4 and 5

  • Asset classification (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Classification of information assets and ICTInformation and Communication Technology assets.

    DORA ICT Risk Management RTS, Article 30

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)

  • Identity management and access control

    Applies to: Financial entities, except those on the simplified framework

    Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence..

    DORA ICT Risk Management RTS, Articles 20 and 21

  • Access control (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..

    DORA ICT Risk Management RTS, Article 33

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 authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    DORA, Article 9(4)(d)

  • Identity management and access control

    Applies to: Financial entities, except those on the simplified framework

    Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence..

    DORA ICT Risk Management RTS, Articles 20 and 21

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 authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    DORA, Article 9(4)(d)

  • Encryption and key management

    Applies to: Financial entities, except those on the simplified framework

    EncryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. and cryptographic controls, and the management of cryptographic keys through their whole life cycle.

    DORA ICT Risk Management RTS, Articles 6 and 7

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 holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Users and data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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 holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. that refuses to share on this ground notifies the competent authority.

    Data Act, Article 4(2)

  • Protect trade secrets when sharing

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and trade secret holders

    Identify data protected as trade secrets, including in the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it., 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)

  • Withhold or refuse data to protect trade secrets Optional

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    A data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. 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)

  • 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 dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections.. 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 gatekeeperAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions., use it to develop a competing product or derive insights about the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties., 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)

  • Data retrieval and erasure

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    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 switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. has succeeded.

    Data Act, Article 25(2)(e), (g) and (h)

  • Prevent unlawful governmental access

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. 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)

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

  • ICT operations and data security

    Applies to: Financial entities, except those on the simplified framework

    Policies and procedures for ICTInformation and Communication Technology operations, capacity and performance management, and data and system security.

    DORA ICT Risk Management RTS, Articles 8, 9 and 11

  • Operations, data and network security (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology operations security, and data, system and network security.

    DORA ICT Risk Management RTS, Articles 34 and 35

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)

  • 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

  • Operations, data and network security (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology operations security, and data, system and network security.

    DORA ICT Risk Management RTS, Articles 34 and 35

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 productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets. and providers of related servicesRelated Service (Data Act)

    Design and manufacture connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets., and design and provide related servicesRelated Service (Data Act), so that product and related service data and the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. 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)

  • Projects, acquisition and development

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology project management, and the acquisition, development and maintenance of ICTInformation and Communication Technology systems.

    DORA ICT Risk Management RTS, Articles 15 and 16

  • Development and change (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.

    DORA ICT Risk Management RTS, Articles 37 and 38

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)

  • Patches and updates

    Documented policies for patches and updates.

    DORA, Article 9(4)(f)

  • Vulnerability and patch management

    Applies to: Financial entities, except those on the simplified framework

    Procedures to identify and fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and to apply patches and updates.

    DORA ICT Risk Management RTS, Article 10

  • ICT change management

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology change management procedures.

    DORA ICT Risk Management RTS, Article 17

  • Development and change (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.

    DORA ICT Risk Management RTS, Articles 37 and 38

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)

  • Tests to run

    Appropriate tests such as vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.

    DORA, Article 25

  • Vulnerability and patch management

    Applies to: Financial entities, except those on the simplified framework

    Procedures to identify and fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and to apply patches and updates.

    DORA ICT Risk Management RTS, Article 10

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 ICTInformation and Communication Technology security.

    DORA ICT Risk Management RTS, Article 19

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.

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

  • 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

  • Incident management and detection

    Applies to: Financial entities, except those on the simplified framework

    An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..

    DORA ICT Risk Management RTS, Articles 22 and 23

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 incidentAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. disrupts core activities, to find the causes and the improvements needed.

    DORA, Article 13(2)

  • Incident management process

    A process to detect, manage and notify ICT-related incidentsA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident.: record all incidents and significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., assign roles, escalate, and find and fix root causes.

    DORA, Article 17

  • Incident management and detection

    Applies to: Financial entities, except those on the simplified framework

    An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..

    DORA ICT Risk Management RTS, Articles 22 and 23

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)

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 incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. to the competent authority, using the common templates.

    DORA, Article 19(1)

  • Initial notification

    An initial notification once the incident is classified as major.

    DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5

  • Intermediate report

    An intermediate report, updated when regular activities have been recovered.

    DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5

  • Final report

    A final report once the root cause analysisA structured investigation into the underlying causes of a problem or incident, rather than only its visible effects. For an IT incident, it examines how technical failures, working practices or other conditions combined to cause the disruption. The findings help an organisation choose corrective measures that address those causes and reduce the chance of recurrence. 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

  • Voluntary notice of cyber threats Optional

    Significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident. may be notified to the competent authority.

    DORA, Article 19(2)

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 servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    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)

  • Crisis communication

    Crisis communication plans to disclose major incidents or vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. to clients, counterparts and the public, and a person in charge of public and media communication.

    DORA, Article 14

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

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 vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and incidents and to analyse their likely impact.

    DORA, Article 13(1)

  • Information-sharing arrangements Optional

    Financial entities may exchange cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. information within trusted communities, under arrangements that protect confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. and personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity.. They must tell the competent authority when they join or leave.

    DORA, Article 45

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 ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., and a business impact analysisThe process of analysing operational functions and the effect a disruption might have on them. Its results inform recovery priorities in continuity planning..

    DORA, Article 11

  • ICT business continuity

    Applies to: Financial entities, except those on the simplified framework

    The components of the ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, the testing of continuity plans, and ICTInformation and Communication Technology response and recovery plans.

    DORA ICT Risk Management RTS, Articles 24 to 26

  • Business continuity (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    An ICTInformation and Communication Technology business continuity planThe documented, predetermined instructions or procedures that keep an organisation's core operations running during and after a significant disruption. DORA, for example, requires financial entities to have an ICT business continuity policy. and its testing.

    DORA ICT Risk Management RTS, Articles 39 and 40

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

    BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICTInformation and Communication Technology capacity (microenterprisesMicroenterprise Under DORA assess the need based on their risk profile).

    DORA, Article 12

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 ICTInformation and Communication Technology systems and applications supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. tested at least yearly. Not required of microenterprisesMicroenterprise Under DORA.

    DORA, Article 24

  • Tests to run

    Appropriate tests such as vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.

    DORA, Article 25

  • Security testing (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology security testing.

    DORA ICT Risk Management RTS, Article 36

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 microenterprisesMicroenterprise Under DORA 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)

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 riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running. is managed within the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and the entity stays fully responsible for compliance.

    DORA, Article 28(1)

  • Third-party risk strategy

    A regularly reviewed strategy on ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running., with a policy on ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.. The management body regularly reviews the risks from those arrangements. Not required of microenterprisesMicroenterprise Under DORA or Article 16 entities.

    DORA, Article 28(2)

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 holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and trade secret holders

    Identify data protected as trade secrets, including in the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it., 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)

  • Limits on the data holder's own use

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Use readily available non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. 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)

  • Fair, reasonable and non-discriminatory terms

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available

    Where a business-to-businessBusiness-to-business describes services or sales between companies, as opposed to services for consumers. NIS2 uses it in Annex I, which lists 'ICT service management (business-to-business)' as one of its sectors. IT service providers that serve business customers should therefore check whether NIS2 applies to them. data sharing duty applies under Article 5 or other law, agree the arrangements with the data recipientData Recipient (Data Act) 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)

  • No discrimination and no unrequested sharing

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. obliged to make data available

    Do not discriminate between comparable categories of data recipientsData Recipient (Data Act), 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)

  • Reasonable compensation

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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 SMESmall and Medium-Sized Enterprises 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)

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

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

  • Switching terms in a written contract

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Set out switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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)

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

  • Terms for critical or important functions

    Contracts for services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. add full service level descriptions, notice periods, business contingency plans, participation in TLPTThreat-Led Penetration Testing, unrestricted rights of access, inspection and audit (microenterprisesMicroenterprise Under DORA may agree to delegate these to an independent third party), and exit strategies with a transition period.

    DORA, Article 30(3)

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 ICTInformation and Communication Technology 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 functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions..

    DORA, Article 28(3)

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 servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    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

  • Switching terms in a written contract

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Set out switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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)

  • Data retrieval and erasure

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    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 switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. has succeeded.

    Data Act, Article 25(2)(e), (g) and (h)

  • Longer transition where 30 days is not feasible

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Where the 30 day transition is technically unfeasible, notify the customer within 14 working days of the switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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)

  • Information on switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Tell the customer about available switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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 interoperabilityThe ability of different systems or organisations to communicate and work together. In data sharing, this means exchanging information in ways that allow the receiving system or organisation to understand and use it. In payments, it means making different payment accounts, providers or systems work together, for example through shared platforms or common acceptance standards. The practical requirements depend on the relevant service and requirements; the term alone does not establish a particular legal duty. specifications for the exportable data.

    Data Act, Article 26

  • Withdrawal of switching charges

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Charge nothing for switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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 switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges.. Before contracting, give clear information on standard fees, early termination penalties and any reduced switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. charges, and on services where switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. is highly complex or costly.

    Data Act, Article 29(1) to (6)

  • Technical support for switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    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)

  • Exit strategies

    Exit strategies for ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., covering provider failure, falling quality and business disruption.

    DORA, Article 28(8)

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 holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Where the user is not the data subjectThe identified or identifiable natural person to whom personal data relate. The GDPR gives data subjects rights such as access, rectification, erasure, objection and data portability, which controllers must be able to handle., make personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. available to the user or third party only with a valid legal basis under GDPRGeneral Data Protection Regulation Article 6 and, where relevant, under GDPRGeneral Data Protection Regulation Article 9 and ePrivacy Article 5(3).

    Data Act, Articles 4(12) and 5(7)

  • 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 dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections.. 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 gatekeeperAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions., use it to develop a competing product or derive insights about the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties., 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)

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 productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets., and providers of related servicesRelated Service (Data Act)

    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 serviceRelated Service (Data Act) providers also state who the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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)

  • Information on switching

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Tell the customer about available switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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 interoperabilityThe ability of different systems or organisations to communicate and work together. In data sharing, this means exchanging information in ways that allow the receiving system or organisation to understand and use it. In payments, it means making different payment accounts, providers or systems work together, for example through shared platforms or common acceptance standards. The practical requirements depend on the relevant service and requirements; the term alone does not establish a particular legal duty. specifications for the exportable data.

    Data Act, Article 26

  • Publish jurisdiction and access safeguards

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Publish on the website, and keep up to date, the jurisdiction of the ICTInformation and Communication Technology infrastructure used for each service and a general description of the measures against international governmental access to non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. held in the Union where that conflicts with Union or national law. List those websites in contracts.

    Data Act, Article 28

  • Withdrawal of switching charges

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Charge nothing for switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. 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 switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges.. Before contracting, give clear information on standard fees, early termination penalties and any reduced switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. charges, and on services where switchingUnder the Data Act, the process in which a customer moves from one data processing service to another of the same service type, to another provider's service or to its own on-premises ICT infrastructure, including by extracting, transforming and uploading data. Providers must remove obstacles and phase out switching charges. is highly complex or costly.

    Data Act, Article 29(1) to (6)

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 productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets. and providers of related servicesRelated Service (Data Act)

    Design and manufacture connected productsAn item that obtains, generates or collects data about its use or environment, can communicate product data through an electronic communications service, a physical connection or on-device access and whose primary function is not storing, processing or transmitting data on behalf of a party other than the user. The Data Act gives users access rights for covered product data under the conditions it sets., and design and provide related servicesRelated Service (Data Act), so that product and related service data and the metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. 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)

  • Give the user access to readily available data

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Where the user cannot access data directly, make readily available data and metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. accessible on a simple request, without undue delay, of the same quality as the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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)

  • Share data with a third party at the user's request

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. and gatekeepersAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions. designated under the Digital Markets ActRegulation (EU) 2022/1925, an EU law intended to make digital markets fairer and easier for businesses to enter and compete in. It sets duties for providers that the European Commission designates as gatekeepers for specified core platform services, such as app stores or online search. Business users and end users benefit from the requirements even when they are not gatekeepers themselves. The DMA is separate from the Digital Services Act.

    At the request of the user, or a party acting for the user, make readily available data and metadataInformation describing other data, such as its format, structure, meaning or security labels. It helps people and systems find, interpret and use the underlying information. In the EU Data Act, metadata specifically means a structured description of the contents or use of data that facilitates finding or using it. The Act's access provisions can therefore concern both the data and the information needed to understand it. available to a third party without undue delay, of the same quality as the data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. has, free of charge to the user and in a machine-readable format, under the terms of Articles 8 and 9. GatekeepersAn undertaking providing core platform services that the Commission has designated under the Digital Markets Act because it has a significant impact on the internal market, runs an important gateway between business users and end users and holds an entrenched and durable position. Gatekeepers must follow DMA obligations and prohibitions. under the Digital Markets ActRegulation (EU) 2022/1925, an EU law intended to make digital markets fairer and easier for businesses to enter and compete in. It sets duties for providers that the European Commission designates as gatekeepers for specified core platform services, such as app stores or online search. Business users and end users benefit from the requirements even when they are not gatekeepers themselves. The DMA is separate from the Digital Services Act. are not eligible third parties.

    Data Act, Article 5(1) and (3)

  • 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 servicesRelated Service (Data Act) 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)

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 servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Publish on the website, and keep up to date, the jurisdiction of the ICTInformation and Communication Technology infrastructure used for each service and a general description of the measures against international governmental access to non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. held in the Union where that conflicts with Union or national law. List those websites in contracts.

    Data Act, Article 28

  • Prevent unlawful governmental access

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal dataIn the EU Data Act, data that is not personal data: it does not relate to an identified or identifiable individual. This can include machine measurements with no link to a person, or information genuinely anonymised so people cannot be identified. Removing names alone may not be enough. Non-personal data can still be commercially sensitive and subject to contractual, security or other legal protections. 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)

  • Handling third-country access requests

    Applies to: Providers of data processing servicesA digital service that gives a customer on-demand network access to a shared pool of configurable, scalable and elastic computing resources that can be rapidly provisioned and released. It covers cloud and edge services, and the Data Act requires providers to make switching between them possible.

    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)

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 holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    Users and data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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 holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. that refuses to share on this ground notifies the competent authority.

    Data Act, Article 4(2)

  • Withhold or refuse data to protect trade secrets Optional

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties.

    A data holderUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. 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)

  • Provide data to public bodies on an exceptional need

    Applies to: Data holdersUnder the Data Act, a person or organisation with the right or obligation under EU or national law to use and make available data, including relevant product or related service data. The DGA has a separate data-holder definition covering legal persons and certain natural persons, not only public-sector bodies, and EHDS defines health data holders. The applicable act must be identified before assigning data-holder duties. 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 BankThe central bank for the euro area, the EU countries that use the euro. Its main task is to keep prices stable. It also supports financial stability and payment infrastructure. In European banking supervision, it works with participating national supervisory authorities to oversee banks and strengthen the banking system. 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 dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity., or pseudonymise it where the request requires personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity..

    Data Act, Articles 14 and 18(1) to (4)

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 GDPRGeneral Data Protection Regulation Article 83(5) amount.

    Data Act, Article 40(1), (2) and (4)

  • 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

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

Subject to more than one?

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

Loading the form…