Skip to content
ContentLora

    Tip: press / anywhere to search.

    Explainer

    The EU Cyber Resilience Act explained

    The Cyber Resilience Act (Regulation (EU) 2024/2847) sets mandatory cybersecurity requirements for hardware and software products sold in the EU, with compliant products carrying the CE marking.[1][2] It entered into force on 10 December 2024. Since 11 September 2026 manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours, and its main obligations apply from 11 December 2027.[1][3]

    Editor reviewedUpdated Explainer14 claims · 100% primaryCybersecurity, Phones, PCs and devices

    This page summarises the European Commission’s description of the regulation. It is not legal advice. Whether and how the CRA applies to a product depends on the official text; check with the relevant authority or a lawyer.

    What the CRA does

    The Cyber Resilience Act sets mandatory cybersecurity requirements for manufacturers of hardware and software products with digital elements. The requirements cover planning, design, development and maintenance. Compliant products carry the CE marking, and national market surveillance authorities enforce the rules.[2]

    Products not supplied in the course of a commercial activity are outside the CRA. Certain products are excluded, particularly where other EU legislation covers them.[4]

    Key dates

    DateWhat applies
    10 December 2024Regulation enters into force[1]
    11 June 2026Rules on notifying conformity assessment bodies (Chapter IV)[5]
    11 September 2026Manufacturers’ reporting obligations (Article 14)[5]
    11 December 2027Main obligations, and reporting by open-source software stewards[1][6]

    On 27 July 2026, the European Commission published practical guidance to help manufacturers, developers and businesses meet their obligations.[7]

    Reporting since September 2026

    From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents that affect the security of their products.[3] The clock has three steps:[3]

    1. Early warning within 24 hours of becoming aware.
    2. Notification within 72 hours.
    3. Final report within 14 days of a fix being available, for vulnerabilities, or within a month of the notification, for severe incidents.

    Notifications go through the Single Reporting Platform run by the EU cybersecurity agency enisa, which has operated since 11 September 2026. Each report reaches the national CSIRT where the manufacturer has its main establishment and, save in exceptional circumstances, ENISA at the same time.[8] Reporting covers all products on the EU market, including those placed on it before December 2027.[9]

    Duties for manufacturers

    Manufacturers must set a support period during which they handle vulnerabilities in the product. The end date, including month and year, must be clearly stated at the time of purchase.[10]

    Makers of “important” class II products and “critical” products must use a third-party assessment or, where available, an EU cybersecurity certification scheme.[11]

    Penalties and open source

    Member states set penalties nationally. Micro and small manufacturers cannot be fined for missing the 24-hour reporting deadline, and open-source software stewards are not subject to penalties.[12] Older products that are already on sale fall under the main rules only if they are substantially modified from December 2027.[9]

    How it fits with other rules

    The CRA sets requirements for products.[2] The NIS2 Directive covers medium-sized and large organisations in critical sectors,[13] with its own 24-hour early-warning clock for significant incidents.[14] For a comparison of reporting regimes, see cyber-incident reporting rules. For a US approach to connected-device security, see the Cyber Trust Mark.

    More in Cybersecurity

    Questions readers ask

    What does the Cyber Resilience Act cover?

    Hardware and software products with digital elements that are supplied in the course of a commercial activity. Some products are excluded, particularly where other EU legislation already covers them.[2][4]

    When does it apply?

    It entered into force on 10 December 2024. Rules on notified conformity assessment bodies apply from 11 June 2026, reporting obligations from 11 September 2026, and the main obligations from 11 December 2027.[1][5]

    What must manufacturers report, and how fast?

    Actively exploited vulnerabilities and severe incidents affecting product security. An early warning is due within 24 hours, a notification within 72 hours, and a final report within 14 days of a fix being available for vulnerabilities, or within a month for severe incidents.[3]

    Does it apply to products already on sale?

    Reporting duties apply to all products on the EU market, including older ones. Otherwise, products placed on the market before 11 December 2027 fall under the CRA only if they are substantially modified from that date.[9]

    Will buyers know how long a product gets security updates?

    Manufacturers must set a support period for handling vulnerabilities, and the end date, including month and year, must be clearly stated at the time of purchase.[10]

    How does it treat open-source software?

    Open-source software stewards are not subject to CRA penalties, and their reporting obligations start on 11 December 2027.[12][6]

    Sources

    · 14 claims from 3 publishers

    Each numbered claim is a statement we checked against the sources listed with it. Tap a number in the text to see its sources in place.

    1. [1]

      The EU Cyber Resilience Act, Regulation (EU) 2024/2847, entered into force on 10 December 2024; its reporting obligations apply from 11 September 2026 and its main obligations from 11 December 2027. confirmedas of 2026-11-14

    2. [2]

      The CRA sets mandatory cybersecurity requirements for manufacturers of hardware and software products with digital elements, covering planning, design, development and maintenance, and compliant products carry the CE marking, with national market surveillance authorities enforcing the rules. confirmedas of 2026-11-14

      • Cyber Resilience Act · European Commission (Shaping Europe's digital future) · Primary source (retrieved 2026-11-14)
      • Cyber Resilience Act · European Commission (Shaping Europe's digital future) · Primary source (retrieved 2026-11-14)
      • Cyber Resilience Act · European Commission (Shaping Europe's digital future) · Primary source (retrieved 2026-11-14)
    3. [3]

      From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting the security of their products, with an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days of a fix being available (for vulnerabilities) or within a month (for severe incidents). confirmedas of 2026-11-14

    4. [4]

      Products not supplied in the course of a commercial activity are outside the CRA, and certain products are excluded, particularly where other EU legislation covers them. confirmedas of 2026-11-14

    5. [5]

      The CRA's rules on notifying conformity assessment bodies (Chapter IV) apply from 11 June 2026, and its Article 14 reporting obligations from 11 September 2026. confirmedas of 2026-11-14

    6. [6]

      Open-source software stewards' CRA reporting obligations apply from 11 December 2027. confirmedas of 2026-11-14

    7. [7]

      On 27 July 2026, the European Commission published practical guidance to help manufacturers, developers and businesses meet their CRA obligations. confirmedas of 2026-11-14

      • Cyber Resilience Act · European Commission (Shaping Europe's digital future) · Primary source (retrieved 2026-11-14)
    8. [8]

      Manufacturers submit CRA notifications through ENISA's Single Reporting Platform, operational from 11 September 2026; a notification goes to the national CSIRT where the manufacturer has its main establishment and, save in exceptional circumstances, is made available to ENISA at the same time. confirmedas of 2026-11-14

    9. [9]

      CRA reporting duties cover all products with digital elements on the EU market, including those placed on it before 11 December 2027, but older products otherwise fall under the CRA only if they are substantially modified from that date. confirmedas of 2026-11-14

    10. [10]

      Under the CRA, manufacturers must set a support period during which they handle the product's vulnerabilities, and the end date (month and year) must be clearly stated at the time of purchase. confirmedas of 2026-11-14

    11. [11]

      Under the CRA, some products need a third-party assessment by a notified body; makers of "important" class II products and "critical" products must use a third-party assessment or, where available, an EU cybersecurity certification scheme. confirmedas of 2026-11-14

    12. [12]

      CRA penalties are set at national level; micro and small manufacturers cannot be fined for missing the 24-hour reporting deadline, and open-source software stewards are not subject to penalties. confirmedas of 2026-11-14

    13. [13]

      As a rule, NIS2 applies to medium-sized and large entities in the covered sectors, which must take cybersecurity risk-management measures and notify national authorities of significant incidents. confirmedas of 2026-11-14

    14. [14]

      The EU's NIS2 Directive requires essential and important entities to send an early warning within 24 hours of becoming aware of a significant incident, an incident notification with an initial assessment within 72 hours, and a final report within one month of the notification. confirmedas of 2026-11-08

    Revision history (1)
    1. Page created.

    Created Nov 14, 2026. Last reviewed by an editor on Nov 15, 2026. Next scheduled review: Nov 14, 2027.

    Cite this page

    "The EU Cyber Resilience Act explained." ContentLora, updated Nov 14, 2026. https://contentlora.com/explain/eu-cyber-resilience-act-explained

    Spotted an error? Suggest a correction or emailcorrections@contentlora.com.