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

CRA vs PLD

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

PLD

At a Glance

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

  • CRA Asks more on 0 topics Alone on 22 topics More detailed on 0 topics
  • PLD Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
Requirements per topic and verdict
Topic CRAPLD Verdict
Governance
Roles and independence CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Risk management
Risk assessment CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Review, audit and improvement CRA: 5 PLD: – Only CRAno specific requirement on the other side in the acts covered
Asset management CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Protection
Access control CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Authentication CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Cryptography and encryption CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Data security CRA: 2 PLD: – Only CRAno specific requirement on the other side in the acts covered
Secure acquisition and development CRA: 2 PLD: – Only CRAno specific requirement on the other side in the acts covered
Configuration, change and patch management CRA: 2 PLD: – Only CRAno specific requirement on the other side in the acts covered
Vulnerability handling CRA: 7 PLD: – Only CRAno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Incident classification CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Reporting to authorities CRA: 4 PLD: – Only CRAno specific requirement on the other side in the acts covered
Informing customers and the public CRA: 4 PLD: – Only CRAno specific requirement on the other side in the acts covered
Threat intelligence and information sharing CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Security testing CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk CRA: 4 PLD: – Only CRAno specific requirement on the other side in the acts covered
Privacy and data protection
Privacy by design and by default CRA: 1 PLD: – Only CRAno specific requirement on the other side in the acts covered
Supervision and enforcement
Cooperation with supervisors CRA: 7 PLD: – Only CRAno specific requirement on the other side in the acts covered
Penalties and liability CRA: 3 PLD: – Only CRAno specific requirement on the other side in the acts covered

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

  • PLD Directive (EU) 2024/2853 of the European Parliament and of the Council of 23 October 2024 Articles 7 to 11 · 5 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

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

PLD: Not in the acts covered

Threshold

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

PLD: Not in the acts covered

Goes to

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

PLD: Not in the acts covered

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.

PLD: Not in the acts covered

Incident reports go to

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

PLD: Not in the acts covered

First notice of an incident

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

PLD: Not in the acts covered

Incident notification

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

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

PLD: Not in the acts covered

Final report

CRA: Within one month of the incident notification

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

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

PLD: Not in the acts covered

Governance

Roles and independence

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

  • When others become the manufacturer

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

    An importer or distributor that sells a product under its own name or trademark, or substantially modifies it, is treated as the manufacturer and is subject to Articles 13 and 14. Any other person who substantially modifies a product and makes it available is also a manufacturer, for the affected part or the whole product if its overall cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. is affected.

    CRA, Articles 21, 22

Nothing in the acts covered.

Risk management

Risk assessment

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

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

  • Cybersecurity risk assessment

    Assess the product's cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risks and use the result across planning, design, development, production, delivery and maintenance. Document it, update it during the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years., base it on intended and foreseeable use, and include it in the technical documentation with a justification for any requirement that does not apply.

    CRA, Article 13(2) to (4)

Nothing in the acts covered.

Review, audit and improvement

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

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

  • Correct non-conformity

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

    CRA, Article 13(21)

  • EU declaration of conformity

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

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

  • Technical documentation

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

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

  • Choose a conformity route

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

    CRA, Article 32(1)

  • Third-party assessment by product class

    Applies to: Manufacturers of important and critical products

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

    CRA, Article 32(2) to (4)

Nothing in the acts covered.

Asset management

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

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

  • Software bill of materials

    Identify and document vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.

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

Nothing in the acts covered.

Protection

Access control

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

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

  • Protect against unauthorised access

    Where applicable, protect against unauthorised access with appropriate controls such as authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., identity or access management, and report possible unauthorised access.

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

Nothing in the acts covered.

Authentication

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

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

  • Protect against unauthorised access

    Where applicable, protect against unauthorised access with appropriate controls such as authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., identity or access management, and report possible unauthorised access.

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

Nothing in the acts covered.

Cryptography and encryption

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

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

  • Confidentiality and integrity of data

    Where applicable, protect the confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of stored, transmitted or processed data, such as by state-of-the-art encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.

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

Nothing in the acts covered.

Data security

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

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

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

Nothing in the acts covered.

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.

Detection and response

Monitoring and detection

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

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

  • Record and monitor activity

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

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

Nothing in the acts covered.

Incident classification

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

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

  • When an incident is severe

    Treat an incident as severe if it harms or could harm the product's ability to protect the availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity or confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of sensitive or important data or functions, or if it has introduced or could introduce malicious code into the product or a user's systems.

    CRA, Article 14(5)

Nothing in the acts covered.

Reporting to authorities

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

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

  • Report actively exploited vulnerabilities

    Notify any actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. you become aware of to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity at the same time. Send an early warning within 24 hours and a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. notification with general information and mitigations within 72 hours. Send a final report describing the vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRTComputer Security Incident Response Team may ask for an intermediate report.

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

  • Report severe incidents

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

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

  • Reporting route

    Submit notifications through ENISAEuropean Union Agency for Cybersecurity's single reporting platform, using the end-point of the coordinating CSIRTComputer Security Incident Response Team in the Member State of your main establishment. Manufacturers without one follow the order in Article 14(7). You may ask for dissemination of a sensitive notification to be delayed on justified cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. grounds.

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

  • Voluntary reporting Optional

    Applies to: Manufacturers and any other natural or legal person

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

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

Nothing in the acts covered.

Informing customers and the public

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

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)

Nothing in the acts covered.

Threat intelligence and information sharing

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

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

  • Voluntary reporting Optional

    Applies to: Manufacturers and any other natural or legal person

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

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

Nothing in the acts covered.

Continuity and resilience

Business continuity and crisis management

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

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

  • Availability of essential functions

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

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

Nothing in the acts covered.

Security testing

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

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

  • Test, fix and disclose vulnerabilities

    Remediate vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition..

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

Nothing in the acts covered.

Third parties and supply chain

Supplier and third-party risk

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

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

  • Third-party components

    Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.

    CRA, Article 13(5), (6)

  • Importer checks

    Applies to: Importers

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

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

  • Distributor checks and cooperation

    Applies to: Distributors

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

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

  • Software bill of materials

    Identify and document vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.

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

Nothing in the acts covered.

Privacy and data protection

Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

  • Minimise data and allow removal

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

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

Nothing in the acts covered.

Supervision and enforcement

Cooperation with supervisors

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

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

Nothing in the acts covered.

Penalties and liability

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

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

Nothing in the acts covered.

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…