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

CRA vs GDPR

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

GDPRControllers and processors

At a Glance

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

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

What This Covers

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

Included

  • 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

  • GDPR Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

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

GDPR: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Threshold

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

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

Goes to

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

GDPR: Controller (Processors); Data subjects (Controllers)

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.

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

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

GDPR: Competent supervisory authority (Controllers)

First notice of an incident

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

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

Incident notification

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

GDPR: 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

GDPR: In phases, without undue further delay (Controllers)

Final report

CRA: Within one month of the incident notification

GDPR: Not in the acts covered

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)

GDPR: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Review of the risk framework

CRA: Not in the acts covered

GDPR: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Testing of critical systems

CRA: Not in the acts covered

GDPR: Regularly

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)

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher Highest stated

Governance

Roles and independence

Both cover it read the wording below

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

  • Joint controllers

    Applies to: Joint controllers

    Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.

    GDPR, Article 26

  • EU representative

    Applies to: Controllers and processors not established in the EU, under Article 3(2)

    A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.

    GDPR, Article 27

Risk management

Risk management framework

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

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

Nothing in the acts covered.

  • Measures to ensure and show compliance

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.

    GDPR, Article 24

Risk assessment

Both cover it read the wording below

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)

  • Assess security risk

    When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.

    GDPR, Article 32(2)

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

Both cover it read the wording below

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)

  • Pseudonymisation and encryption

    Apply pseudonymisation and encryption of personal data, as appropriate to the risk.

    GDPR, Article 32(1)(a)

Data security

Both cover it read the wording below

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)

  • Integrity and confidentiality

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.

    GDPR, Article 5(1)(f)

  • Security of systems and services

    Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.

    GDPR, Article 32(1)(b)

Secure acquisition and development

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

Nothing in the acts covered.

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.

Human resources security

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

Nothing in the acts covered.

  • Staff act only on instructions

    Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.

    GDPR, Articles 29 and 32(4)

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 handling

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

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

Nothing in the acts covered.

  • Document every breach

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.

    GDPR, Article 33(5)

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

Both cover it read the wording below

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)

  • Notify a personal data breach

    Applies to: Controllers

    Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.

    GDPR, Article 33(1)

  • Processor tells the controller

    Applies to: Processors

    Tell the controller of a personal data breach without undue delay after becoming aware of it.

    GDPR, Article 33(2)

  • What the breach notice contains

    Applies to: Controllers

    Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.

    GDPR, Article 33(3) and (4)

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)

  • Tell the people affected

    Applies to: Controllers

    Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.

    GDPR, Article 34(1) to (4)

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.

Backup and recovery

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

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

Nothing in the acts covered.

  • Restoring access after an incident

    Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.

    GDPR, Article 32(1)(c)

Security testing

Both cover it read the wording below

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)

  • Testing the measures

    Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.

    GDPR, Article 32(1)(d)

Third parties and supply chain

Supplier and third-party risk

CRA more detailed more requirements on this, not necessarily stricter

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)

  • Use only processors with sufficient guarantees

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.

    GDPR, Article 28(1)

  • Sub-processors

    Applies to: Processors

    Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.

    GDPR, Article 28(2) and (4)

Contract requirements

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

  • Processing contract

    Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.

    GDPR, Article 28(3) and (9)

Privacy and data protection

Lawful processing

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

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

  • Purpose limitation and data minimisation

    Applies to: Controllers

    Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.

    GDPR, Article 5(1)(b) and (c)

  • Accuracy and storage limitation

    Applies to: Controllers

    Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.

    GDPR, Article 5(1)(d) and (e)

  • Accountability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.

    GDPR, Article 5(2)

  • Lawful basis

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.

    GDPR, Articles 5(1)(a) and 6(1)

  • Conditions for consent

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.

    GDPR, Article 7

  • Children's consent to online services

    Applies to: Controllers offering information society services directly to children

    Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.

    GDPR, Article 8(1) and (2)

  • Special category and criminal offence data

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.

    GDPR, Articles 9 and 10

Transparency

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

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

  • Information when collecting from the person

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.

    GDPR, Articles 12(1) and 13

  • Information when data comes from elsewhere

    Applies to: Controllers

    Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.

    GDPR, Article 14

Rights of individuals

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

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

  • Answer rights requests in time

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.

    GDPR, Article 12(3) to (5)

  • Right of access

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.

    GDPR, Article 15

  • Rectification, restriction and telling recipients

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.

    GDPR, Articles 16, 18 and 19

  • Right to erasure

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.

    GDPR, Article 17

  • Right to data portability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.

    GDPR, Article 20

  • Right to object

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.

    GDPR, Article 21

  • Solely automated decisions

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.

    GDPR, Article 22

Privacy by design and by default

Both cover it read the wording below

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)

  • Data protection by design

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.

    GDPR, Article 25(1)

  • Data protection by default

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.

    GDPR, Article 25(2)

Impact assessment

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

NIST Privacy Framework ID.RA-P

Nothing in the acts covered.

  • When an impact assessment is needed

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.

    GDPR, Article 35(1) and (3)

  • What the assessment contains

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.

    GDPR, Article 35(2), (7), (9) and (11)

  • Prior consultation

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.

    GDPR, Article 36(1) to (3)

Records of processing

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

NIST Privacy Framework ID.IM-P

Nothing in the acts covered.

  • Controller's record of processing

    Applies to: Controllers

    Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.

    GDPR, Article 30(1), (3), (4) and (5)

  • Processor's record of processing

    Applies to: Processors

    Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.

    GDPR, Article 30(2) to (5)

Data protection officer

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

NIST Privacy Framework GV.PO-P

Nothing in the acts covered.

  • Designate a data protection officer

    Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.

    GDPR, Article 37(1), (5) and (7)

  • Position and tasks of the DPO

    Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.

    GDPR, Articles 38 and 39

International transfers

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

Nothing in the acts covered.

  • Transfers need a Chapter V ground

    Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.

    GDPR, Articles 44 and 45

  • Appropriate safeguards

    Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.

    GDPR, Articles 46 and 47

  • Third-country orders

    Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.

    GDPR, Article 48

  • Derogations for specific situations

    Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.

    GDPR, Article 49

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)

  • Cooperate with supervisory authority powers

    Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.

    GDPR, Articles 31 and 58

Penalties and liability

Both cover it read the wording below

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

  • Fines for operational obligations

    Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.

    GDPR, Article 83(1) to (4)

  • Fines for principles, rights and transfers

    Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.

    GDPR, Article 83(5) and (6)

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…