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

Data Act vs NIS2

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

NIS2Essential and important entities

At a Glance

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

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

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

Status

Reviewed against the official texts.

Key Numbers

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

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

NIS2: 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.)

NIS2: Not in the acts covered

Incident reports go to

Data Act: Not in the acts covered

NIS2: CSIRTComputer Security Incident Response Team or competent authority

First notice of an incident

Data Act: Not in the acts covered

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

Incident notification

Data Act: Not in the acts covered

NIS2: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)

Intermediate report

Data Act: Not in the acts covered

NIS2: On request

Final report

Data Act: Not in the acts covered

NIS2: Within one month of the incident notification

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

NIS2: Not in the acts covered

Review of the risk framework

Data Act: Not in the acts covered

NIS2: 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. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

Register of third-party arrangements

Data Act: Not in the acts covered

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

Registration with the authority

Data Act: Not in the acts covered

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

Management body training

Data Act: Not in the acts covered

NIS2: Required

Management body liability

Data Act: Not in the acts covered

NIS2: Yes, for infringements of Article 21

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)

NIS2: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance.: maximum of at least EUR 7 million or 1.4%, whichever is higher.

Governance

Management accountability

Only NIS2 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 approves and oversees the measures

    The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.

    NIS2, Article 20(1)

Roles and independence

Only NIS2 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.

  • Roles, responsibilities and authorities

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.2

Security policy

Only NIS2 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.

  • Risk analysis and security policies

    Policies on risk analysis and on information system security.

    NIS2, Article 21(2)(a)

  • Network and information system security policy

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A security policy approved by the management body, reviewed at least annually and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.1

Awareness and training

Only NIS2 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 follow training to identify risks and assess cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management practices. Entities are encouraged to offer similar training to employees regularly.

    NIS2, Article 20(2)

  • Cyber hygiene and training

    Basic cyber hygiene practices and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. training.

    NIS2, Article 21(2)(g)

Risk management

Risk management framework

Only NIS2 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.

  • Appropriate and proportionate measures

    Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.

    NIS2, Article 21(1)

  • All-hazards approach

    The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.

    NIS2, Article 21(2)

  • Risk management framework

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1

Risk assessment

Only NIS2 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.

  • Risk analysis and security policies

    Policies on risk analysis and on information system security.

    NIS2, Article 21(2)(a)

  • Risk management framework

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1

Review, audit and improvement

Only NIS2 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.

  • Assessing effectiveness

    Policies and procedures to assess whether the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures work.

    NIS2, Article 21(2)(f)

  • Corrective measures

    An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.

    NIS2, Article 21(4)

  • Independent review

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Independent reviews of network and information 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. at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.3

Asset management

Only NIS2 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.

  • Asset management

    Asset managementAsset Management in Information Security.

    NIS2, Article 21(2)(i)

  • Asset inventory

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.

    NIS2 Implementing Regulation, Annex, point 12.4

Protection

Access control

Only NIS2 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.

  • Access control policies

    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.

    NIS2, Article 21(2)(i)

  • Access rights and privileged accounts

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Management of access rights, and stricter controls on privileged and system administration accounts.

    NIS2 Implementing Regulation, Annex, points 11.2 and 11.3

Authentication

Only NIS2 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.

  • Multi-factor authentication

    Multi-factor or continuous 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. solutions, where appropriate.

    NIS2, Article 21(2)(j)

  • Multi-factor authentication

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Multi-factor or continuous 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. where appropriate, in line with the classification of the asset accessed.

    NIS2 Implementing Regulation, Annex, point 11.7

Cryptography and encryption

Only NIS2 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.

  • Cryptography

    Policies and procedures on the use of cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. and, where appropriate, 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..

    NIS2, Article 21(2)(h)

Data security

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

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

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

Nothing in the acts covered.

Network security

Only NIS2 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 security and segmentation

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.

    NIS2 Implementing Regulation, Annex, points 6.7 and 6.8

Secure communications

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

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

Nothing in the acts covered.

  • Secured communications

    Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.

    NIS2, Article 21(2)(j)

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)

  • Secure acquisition, development and maintenance

    Security in the acquisition, development and maintenance of network and information systems, including 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. handling and disclosure.

    NIS2, Article 21(2)(e)

Configuration, change and patch management

Only NIS2 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.

  • Configuration, change and patch management

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. benefits and the reasons are documented.

    NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6

Vulnerability handling

Only NIS2 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.

  • Secure acquisition, development and maintenance

    Security in the acquisition, development and maintenance of network and information systems, including 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. handling and disclosure.

    NIS2, Article 21(2)(e)

Human resources security

Only NIS2 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 security

    Human resources security.

    NIS2, Article 21(2)(i)

  • Background verification

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.

    NIS2 Implementing Regulation, Annex, point 10.2

Physical and environmental security

Only NIS2 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.

  • All-hazards approach

    The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.

    NIS2, Article 21(2)

  • Physical and environmental security

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Supporting utilities, protection against physical and environmental threats, and perimeter and physical access 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..

    NIS2 Implementing Regulation, Annex, points 13.1 to 13.3

Detection and response

Monitoring and detection

Only NIS2 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.

  • Monitoring and logging

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Monitoring and logging of network and information systems to detect events that could be incidents.

    NIS2 Implementing Regulation, Annex, point 3.2

Incident handling

Only NIS2 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.

Incident classification

Only NIS2 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.

  • When an incident is significant

    An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.

    NIS2, Article 23(3)

  • Event assessment and classification

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.

    NIS2 Implementing Regulation, Annex, point 3.4

  • When an incident is significant

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).

    NIS2 Implementing Regulation, Articles 3 to 14

Reporting to authorities

Only NIS2 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.

  • Notify significant incidents

    Notify the CSIRTComputer Security Incident Response Team or competent authority without undue delay of any significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident., with the information needed to judge any cross-border impact.

    NIS2, Article 23(1)

  • Early warning

    An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.

    NIS2, Article 23(4)(a)

  • Incident notification

    An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.

    NIS2, Article 23(4)(b)

  • Intermediate report

    An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.

    NIS2, Article 23(4)(c)

  • Final report

    A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.

    NIS2, Article 23(4)(d) and (e)

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)

  • Inform affected recipients

    Where appropriate, notify recipients of the services without undue delay of significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. likely to affect the provision of those services.

    NIS2, Article 23(1)

  • Warn of significant cyber threats

    Where applicable, tell recipients potentially affected by a significant cyber threatA 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., without undue delay, what they can do about it and, where appropriate, about the threat itself.

    NIS2, Article 23(2)

Threat intelligence and information sharing

Only NIS2 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.

  • Information-sharing arrangements Optional

    Entities may exchange cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. information such as threats, 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 indicators of compromise within information-sharing arrangements. Essential and important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. notify the competent authority when they join or withdraw.

    NIS2, Article 29

Continuity and resilience

Business continuity and crisis management

Only NIS2 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.

  • Business continuity and crisis management

    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., such as 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. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.

    NIS2, Article 21(2)(c)

Backup and recovery

Only NIS2 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.

  • Business continuity and crisis management

    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., such as 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. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.

    NIS2, Article 21(2)(c)

  • Backup and redundancy

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    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. copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.

    NIS2 Implementing Regulation, Annex, point 4.2

Security testing

Only NIS2 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.

  • Security testing

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A policy and procedures for security testing of network and information systems.

    NIS2 Implementing Regulation, Annex, point 6.5

Third parties and supply chain

Supplier and third-party risk

Only NIS2 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.

  • Supply chain security

    Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.

    NIS2, Article 21(2)(d)

  • What to weigh for each supplier and service provider

    Entities weigh the specific 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. of each direct supplier and service provider, the quality of their products and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. practices, including secure development, and the results of EU coordinated risk assessmentsRisk Assessment of critical supply chains.

    NIS2, Article 21(3)

Contract requirements

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

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)

Nothing in the acts covered.

Register of third-party arrangements

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

  • Directory of suppliers

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A directory of direct suppliers and service providers, kept up to date.

    NIS2 Implementing Regulation, Annex, point 5.2

Exit and termination

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

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)

Nothing in the acts covered.

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

Registration with authorities

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

Nothing in the acts covered.

  • Register with the authority

    Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.

    NIS2, Article 3(4)

  • Registry of digital providers

    DNSDomain Name System, TLDTop-Level Domain, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISAEuropean Union Agency for Cybersecurity registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).

    NIS2, Article 27

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)

  • Management approves and oversees the measures

    The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.

    NIS2, Article 20(1)

  • Administrative fines

    Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.

    NIS2, Article 34(4) and (5)

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…