> CRA vs Data Act side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# CRA vs Data Act

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

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

[Data Act](https://grc.plus/regulation/eu-data-act/)Manufacturers 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

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

## What This Covers

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

Included

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

Status

Reviewed against the official texts.

Included

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

Status

Reviewed against the official texts.

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

### 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 holders); User or third party in writing; competent authority notified (Data holders); Customer, before complying (Providers of data processing services)

### Evidence to keep

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

Data Act: Not in the acts covered

### Incident reports go to

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

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 CSIRT; On request of the coordinating CSIRT

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 services placed on the market after 12 September 2026 (Manufacturers of connected products and providers of related services)

### 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 authorities may fine up to the GDPR 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 cybersecurity is affected.
  [CRA, Articles 21, 22](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

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

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

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

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 authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

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 authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

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

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

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

### Secure acquisition and development

**Both cover it** read the wording below

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

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

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

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

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

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-out.
  [CRA, Annex I, Part I, point (2)(l)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

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

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

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

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

### 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 CSIRT or ENISA of vulnerabilities, cyber threats, incidents and near misses. Doing so creates no additional obligations for the person notifying.
  [CRA, Article 15(1), (2), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

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

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

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

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

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

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

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

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

### Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

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

Nothing in the acts covered.

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

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

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

### Penalties and liability

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

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

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

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare CRA](https://grc.plus/compare/cra/)
- [Compare Data Act](https://grc.plus/compare/data-act/)

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