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

CRA vs Data Act

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

CRAManufacturers of products with digital elements

Data ActManufacturers and related service providers, data holders, providers of data processing services

At a Glance

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

  • CRA Asks more on 0 topics Alone on 17 topics More detailed on 3 topics
  • Data Act Asks more on 0 topics Alone on 6 topics More detailed on 1 topic
Requirements per topic and verdict
Topic CRAData Act Verdict
Governance
Roles and independence CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Risk management
Risk assessment CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Review, audit and improvement CRA: 5 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Asset management CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Protection
Access control CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Authentication CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Cryptography and encryption CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Data security CRA: 2 Data Act: 6 Data Act more detailedmore requirements on this, not necessarily stricter
Secure acquisition and development CRA: 2 Data Act: 1 Both cover itread the wording below
Configuration, change and patch management CRA: 2 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Vulnerability handling CRA: 7 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Incident classification CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Reporting to authorities CRA: 4 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Informing customers and the public CRA: 4 Data Act: 1 CRA more detailedmore requirements on this, not necessarily stricter
Threat intelligence and information sharing CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Security testing CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk CRA: 4 Data Act: – Only CRAno specific requirement on the other side in the acts covered
Contract requirements CRA: – Data Act: 8 Only Data Actno specific requirement on the other side in the acts covered
Exit and termination CRA: – Data Act: 7 Only Data Actno specific requirement on the other side in the acts covered
Privacy and data protection
Lawful processing CRA: – Data Act: 2 Only Data Actno specific requirement on the other side in the acts covered
Transparency CRA: – Data Act: 4 Only Data Actno specific requirement on the other side in the acts covered
Rights of individuals CRA: – Data Act: 4 Only Data Actno specific requirement on the other side in the acts covered
Privacy by design and by default CRA: 1 Data Act: – Only CRAno specific requirement on the other side in the acts covered
International transfers CRA: – Data Act: 3 Only Data Actno specific requirement on the other side in the acts covered
Supervision and enforcement
Cooperation with supervisors CRA: 7 Data Act: 3 CRA more detailedmore requirements on this, not necessarily stricter
Penalties and liability CRA: 3 Data Act: 1 CRA more detailedmore requirements on this, not necessarily stricter

What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

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

Status

Reviewed against the official texts.

Included

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

Key Numbers

Deadline

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

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

Threshold

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

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)

Goes to

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

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

Evidence to keep

CRA: Documented 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. in the technical documentation; EU declaration of conformity, at least 10 years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer (Importers); Technical documentation and EU declaration, at least 10 years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer; Software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies.

Data Act: Not in the acts covered

Incident reports go to

CRA: Coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity, via the single reporting platform; Coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity, via the single reporting platform; Coordinating CSIRTComputer Security Incident Response Team of the main establishment and ENISAEuropean Union Agency for Cybersecurity

Data Act: Not in the acts covered

First notice of an incident

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

Data Act: Not in the acts covered

Incident notification

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

Data Act: Not in the acts covered

Intermediate report

CRA: On request of the coordinating CSIRTComputer Security Incident Response Team; On request of the coordinating CSIRTComputer Security Incident Response Team

Data Act: Not in the acts covered

Final report

CRA: Within one month of the incident notification

Data Act: Not in the acts covered

Deadline to have the measures in place

CRA: Not in the acts covered

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

External assessment or certification

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

Data Act: Not in the acts covered

Maximum fines

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

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)

Governance

Roles and independence

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

  • When others become the manufacturer

    Applies to: Importers and distributors who sell a product under their own name or trademark or substantially modify it, and others who substantially modify a product

    An importer or distributor that sells a product under its own name or trademark, or substantially modifies it, is treated as the manufacturer and is subject to Articles 13 and 14. Any other person who substantially modifies a product and makes it available is also a manufacturer, for the affected part or the whole product if its overall 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. is affected.

    CRA, Articles 21, 22

Nothing in the acts covered.

Risk management

Risk assessment

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

  • Cybersecurity risk assessment

    Assess the product's 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. risks and use the result across planning, design, development, production, delivery and maintenance. Document it, update it during the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years., base it on intended and foreseeable use, and include it in the technical documentation with a justification for any requirement that does not apply.

    CRA, Article 13(2) to (4)

Nothing in the acts covered.

Review, audit and improvement

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

  • Correct non-conformity

    If you know or have reason to believe the product or your processes do not meet Annex I, immediately take corrective measures, or withdraw or recall the product as appropriate.

    CRA, Article 13(21)

  • EU declaration of conformity

    Once conformity is shown, draw up the EU declaration, following the Annex V structure, and supply it or a simplified version with the product. Use a single declaration where several Union acts apply. By drawing it up you assume responsibility for the product's compliance.

    CRA, Articles 13(12), (20), 28

  • Technical documentation

    Draw up technical documentation with at least the Annex VII elements before placing the product on the market and update it as needed, at least during the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years.. Keep it and the EU declaration available to the market surveillance authorities for at least 10 years after the product is placed on the market, or for the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer.

    CRA, Articles 13(13), 31(1), (2)

  • Choose a conformity route

    Assess the product and your processes against Annex I using internal control (module A), EU-type examination with conformity to type (modules B and C), full quality assurance (module H), or a European cybersecurity certification schemeA comprehensive set of requirements, technical requirements, standards and procedures set at EU level for the certification or conformity assessment of specific ICT products, services or processes. Schemes are adopted under the Cybersecurity Act, and NIS2 and the CRA can require their use. where available and applicable.

    CRA, Article 32(1)

  • Third-party assessment by product class

    Applies to: Manufacturers of important and critical products

    Important products in class I use modules B and C or module H unless harmonised standards, common specifications or a scheme at assurance level substantial were fully applied. Class II use modules B and C, module H or a scheme at that level. Critical products use a certification scheme under Article 8(1), or the class II procedures where its conditions are not met.

    CRA, Article 32(2) to (4)

Nothing in the acts covered.

Asset management

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

  • Software bill of materials

    Identify and document 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 components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.

    CRA, Annex I, Part II, point (1)

Nothing in the acts covered.

Protection

Access control

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

  • Protect against unauthorised access

    Where applicable, protect against unauthorised access with appropriate controls such as 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., identity or access management, and report possible unauthorised access.

    CRA, Annex I, Part I, point (2)(d)

Nothing in the acts covered.

Authentication

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

  • Protect against unauthorised access

    Where applicable, protect against unauthorised access with appropriate controls such as 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., identity or access management, and report possible unauthorised access.

    CRA, Annex I, Part I, point (2)(d)

Nothing in the acts covered.

Cryptography and encryption

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

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

  • Confidentiality and integrity of data

    Where applicable, protect the confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of stored, transmitted or processed data, such as by state-of-the-art 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. at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.

    CRA, Annex I, Part I, point (2)(e), (f)

Nothing in the acts covered.

Data security

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

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

  • Confidentiality and integrity of data

    Where applicable, protect the confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of stored, transmitted or processed data, such as by state-of-the-art 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. at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.

    CRA, Annex I, Part I, point (2)(e), (f)

  • Minimise data and allow removal

    Where applicable, process only data that is adequate, relevant and limited to the product's purpose. Let users securely and easily remove all data and settings permanently, and make any transfer to other products secure.

    CRA, Annex I, Part I, point (2)(g), (m)

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

Secure acquisition and development

Both cover it read the wording below

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

  • Meet the essential requirements

    When placing a product on the market, ensure it was designed, developed and produced in line with the 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. requirements in Annex I, Part I.

    CRA, Article 13(1)

  • No known vulnerabilities, secure by default and reduced attack surface

    Where applicable on the basis of the 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., supply the product without known exploitable 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 with a secure-by-default configuration that can be reset. Limit attack surfaces and reduce the impact of incidents with exploitation mitigation.

    CRA, Annex I, Part I, point (2)(a), (b), (j), (k)

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

Configuration, change and patch management

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

  • Keep security updates available

    Keep each security update issued during the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. available for at least 10 years after it is issued, or for the rest of the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer.

    CRA, Article 13(9)

  • Test, fix and disclose vulnerabilities

    Remediate 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. without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed 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..

    CRA, Annex I, Part II, points (2) to (8)

Nothing in the acts covered.

Vulnerability handling

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

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

  • Third-party components

    Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a 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. in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.

    CRA, Article 13(5), (6)

  • Set and state the support period

    Handle 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. effectively for a support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. that reflects expected use and is at least five years, or the expected use time if shorter. State the end date, at least month and year, clearly at the time of purchase, and notify users when support ends where technically feasible.

    CRA, Article 13(8), (19)

  • Report actively exploited vulnerabilities

    Notify any actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. you become aware of to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity at the same time. Send an early warning within 24 hours and a 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. notification with general information and mitigations within 72 hours. Send a final report describing the 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., any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRTComputer Security Incident Response Team may ask for an intermediate report.

    CRA, Article 14(1), (2), (6)

  • Importer corrective action and alerts

    Applies to: Importers

    Hold back non-conforming products and take corrective measures, withdraw or recall those already placed. Inform the manufacturer of any 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. without undue delay, and where a product presents a significant 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, immediately inform the market surveillance authorities.

    CRA, Article 19(3), (5)

  • Distributor corrective action and alerts

    Applies to: Distributors

    Make sure corrective measures, withdrawal or recall take place for non-conforming products. Inform the manufacturer of any 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. without undue delay. Immediately inform market surveillance authorities of a significant 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. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.

    CRA, Article 20(4), (6)

  • Software bill of materials

    Identify and document 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 components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.

    CRA, Annex I, Part II, point (1)

  • Test, fix and disclose vulnerabilities

    Remediate 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. without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed 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..

    CRA, Annex I, Part II, points (2) to (8)

Nothing in the acts covered.

Detection and response

Monitoring and detection

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

  • Record and monitor activity

    Where applicable, provide security-related information by recording and monitoring relevant internal activity, including access to or changes of data, services or functions, with a user opt-outAn opt-out is a way for a person to refuse an activity or stop further participation. In direct marketing, it means taking a step such as unsubscribing from messages. In a default-on arrangement, the activity proceeds unless the person refuses. Having an opt-out does not establish valid consent where the applicable law requires a positive agreement beforehand..

    CRA, Annex I, Part I, point (2)(l)

Nothing in the acts covered.

Incident classification

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

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

  • When an incident is severe

    Treat an incident as severe if it harms or could harm the product's ability to protect the availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity 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. of sensitive or important data or functions, or if it has introduced or could introduce malicious code into the product or a user's systems.

    CRA, Article 14(5)

Nothing in the acts covered.

Reporting to authorities

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

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

  • Report actively exploited vulnerabilities

    Notify any actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. you become aware of to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity at the same time. Send an early warning within 24 hours and a 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. notification with general information and mitigations within 72 hours. Send a final report describing the 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., any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRTComputer Security Incident Response Team may ask for an intermediate report.

    CRA, Article 14(1), (2), (6)

  • Report severe incidents

    Notify any severe incident affecting the product's security to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity at the same time. Send an early warning within 24 hours stating whether unlawful or malicious acts are suspected, and an incident notification with an initial assessment and mitigations within 72 hours. Send a final report with the root cause and measures within one month of the incident notification. The coordinating CSIRTComputer Security Incident Response Team may ask for an intermediate report.

    CRA, Article 14(3), (4), (6)

  • Reporting route

    Submit notifications through ENISAEuropean Union Agency for Cybersecurity's single reporting platform, using the end-point of the coordinating CSIRTComputer Security Incident Response Team in the Member State of your main establishment. Manufacturers without one follow the order in Article 14(7). You may ask for dissemination of a sensitive notification to be delayed on justified 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. grounds.

    CRA, Articles 14(7), 16(1), (2)

  • Voluntary reporting Optional

    Applies to: Manufacturers and any other natural or legal person

    Any person may voluntarily notify a coordinating CSIRTComputer Security Incident Response Team or ENISAEuropean Union Agency for Cybersecurity of vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition., incidents and near missesAn event that could have compromised the availability, authenticity, integrity or confidentiality of data or of services offered by network and information systems, but was prevented or did not materialise. NIS2 allows voluntary reporting of near misses, and the CRA uses the same definition.. Doing so creates no additional obligations for the person notifying.

    CRA, Article 15(1), (2), (5)

Nothing in the acts covered.

Informing customers and the public

CRA more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 RS.CO, RC.CO

  • Set and state the support period

    Handle 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. effectively for a support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. that reflects expected use and is at least five years, or the expected use time if shorter. State the end date, at least month and year, clearly at the time of purchase, and notify users when support ends where technically feasible.

    CRA, Article 13(8), (19)

  • Product identity, contact point and instructions

    Give the product a type, batch or serial number and show your name and contact details. Designate a single point of contact for users that is not limited to automated tools. Supply the Annex II information and instructions and keep them available for at least 10 years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years., whichever is longer.

    CRA, Article 13(15) to (18)

  • Cooperate with authorities and announce cessation

    On a reasoned request, give the market surveillance authority the information needed to show conformity and cooperate on measures to remove risks. If you are ceasing operations and cannot comply, inform the authorities and, as far as possible, users before this takes effect.

    CRA, Article 13(22), (23)

  • Inform users

    After becoming aware of an actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. or severe incident, inform impacted users, and where appropriate all users, and tell them about mitigations they can deploy, where appropriate in a structured, machine-readable format.

    CRA, Article 14(8)

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

Threat intelligence and information sharing

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

  • Voluntary reporting Optional

    Applies to: Manufacturers and any other natural or legal person

    Any person may voluntarily notify a coordinating CSIRTComputer Security Incident Response Team or ENISAEuropean Union Agency for Cybersecurity of vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition., incidents and near missesAn event that could have compromised the availability, authenticity, integrity or confidentiality of data or of services offered by network and information systems, but was prevented or did not materialise. NIS2 allows voluntary reporting of near misses, and the CRA uses the same definition.. Doing so creates no additional obligations for the person notifying.

    CRA, Article 15(1), (2), (5)

Nothing in the acts covered.

Continuity and resilience

Business continuity and crisis management

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

  • Availability of essential functions

    Where applicable, protect the availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable. of essential and basic functions, also after an incident, including resilience against denial-of-service attacks. Minimise the product's negative impact on services provided by other devices or networks.

    CRA, Annex I, Part I, point (2)(h), (i)

Nothing in the acts covered.

Security testing

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

  • Test, fix and disclose vulnerabilities

    Remediate 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. without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed 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..

    CRA, Annex I, Part II, points (2) to (8)

Nothing in the acts covered.

Third parties and supply chain

Supplier and third-party risk

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

  • Third-party components

    Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a 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. in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.

    CRA, Article 13(5), (6)

  • Importer checks

    Applies to: Importers

    Place on the market only products and manufacturer processes that meet Annex I. First ensure the conformity assessmentThe process of verifying whether a product, service or system meets the requirements set by the applicable EU act, for example the essential cybersecurity requirements of the CRA or the high-risk requirements of the AI Act. Depending on the risk class, the manufacturer does it alone or with a notified body. and technical documentation exist, the product has CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws., EU declaration and instructions, and the identification and support-date duties are met. Show your own contact details on the product, its packaging or an accompanying document.

    CRA, Article 19(1), (2), (4)

  • Distributor checks and cooperation

    Applies to: Distributors

    Act with due care. Before making a product available, verify the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws. and that the manufacturer and importer met their identification, instruction, support-date and declaration duties. Hold back non-conforming products and cooperate with the authority on reasoned request.

    CRA, Article 20(1), (2), (3), (5)

  • Software bill of materials

    Identify and document 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 components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.

    CRA, Annex I, Part II, point (1)

Nothing in the acts covered.

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

Nothing in the acts covered.

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

Exit and termination

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

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

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

Nothing in the acts covered.

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

Transparency

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

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

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

Rights of individuals

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

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

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

Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

  • Minimise data and allow removal

    Where applicable, process only data that is adequate, relevant and limited to the product's purpose. Let users securely and easily remove all data and settings permanently, and make any transfer to other products secure.

    CRA, Annex I, Part I, point (2)(g), (m)

Nothing in the acts covered.

International transfers

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

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

Supervision and enforcement

Cooperation with supervisors

CRA more detailed more requirements on this, not necessarily stricter

  • Cooperate with authorities and announce cessation

    On a reasoned request, give the market surveillance authority the information needed to show conformity and cooperate on measures to remove risks. If you are ceasing operations and cannot comply, inform the authorities and, as far as possible, users before this takes effect.

    CRA, Article 13(22), (23)

  • Importer corrective action and alerts

    Applies to: Importers

    Hold back non-conforming products and take corrective measures, withdraw or recall those already placed. Inform the manufacturer of any 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. without undue delay, and where a product presents a significant 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, immediately inform the market surveillance authorities.

    CRA, Article 19(3), (5)

  • Importer records and cooperation

    Applies to: Importers

    Keep the EU declaration of conformity for at least 10 years after the product is placed on the market, or for the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer, and ensure the technical documentation can be made available on request. Provide information to the authority on reasoned request and cooperate. If the manufacturer has ceased operations, inform the authorities and, where possible, users.

    CRA, Article 19(6) to (8)

  • Distributor checks and cooperation

    Applies to: Distributors

    Act with due care. Before making a product available, verify the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws. and that the manufacturer and importer met their identification, instruction, support-date and declaration duties. Hold back non-conforming products and cooperate with the authority on reasoned request.

    CRA, Article 20(1), (2), (3), (5)

  • Distributor corrective action and alerts

    Applies to: Distributors

    Make sure corrective measures, withdrawal or recall take place for non-conforming products. Inform the manufacturer of any 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. without undue delay. Immediately inform market surveillance authorities of a significant 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. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.

    CRA, Article 20(4), (6)

  • Technical documentation

    Draw up technical documentation with at least the Annex VII elements before placing the product on the market and update it as needed, at least during the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years.. Keep it and the EU declaration available to the market surveillance authorities for at least 10 years after the product is placed on the market, or for the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer.

    CRA, Articles 13(13), 31(1), (2)

  • Fines for misleading information

    Applies to: Economic operators

    Supplying incorrect, incomplete or misleading information to notified bodiesA conformity assessment body that a Member State has notified to the Commission as competent to carry out third-party assessment under EU legislation. Whether a manufacturer or provider must involve one depends on the applicable act, system or product classification and conformity assessment route; not every high-risk AI system requires a notified body. and market surveillance authorities in reply to a request carries fines of up to EUR 5 million or 1% of total worldwide annual turnover, whichever is higher.

    CRA, Article 64(4)

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

Penalties and liability

CRA more detailed more requirements on this, not necessarily stricter

  • Fines for essential requirements and reporting

    Applies to: Manufacturers

    Breach of Annex I or of Articles 13 and 14 carries fines of up to EUR 15 million or 2.5% of total worldwide annual turnover, whichever is higher. Micro and small enterprises are not fined for missing the 24-hour early warning, and open-source software stewardsA legal person, other than a manufacturer, that systematically provides sustained support for the development of free and open-source software intended for commercial activities and ensures its viability, such as a foundation. The CRA gives stewards a lighter regime instead of full manufacturer obligations. are not fined for any infringement.

    CRA, Article 64(2), (10)

  • Fines for other operator obligations

    Applies to: Economic operators and others subject to the listed articles

    Breach of Articles 18 to 23, 28, 30(1) to (4), 31(1) to (4), 32(1) to (3), 33(5) and certain other listed articles carries fines of up to EUR 10 million or 2% of total worldwide annual turnover, whichever is higher.

    CRA, Article 64(3)

  • Fines for misleading information

    Applies to: Economic operators

    Supplying incorrect, incomplete or misleading information to notified bodiesA conformity assessment body that a Member State has notified to the Commission as competent to carry out third-party assessment under EU legislation. Whether a manufacturer or provider must involve one depends on the applicable act, system or product classification and conformity assessment route; not every high-risk AI system requires a notified body. and market surveillance authorities in reply to a request carries fines of up to EUR 5 million or 1% of total worldwide annual turnover, whichever is higher.

    CRA, Article 64(4)

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

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…