In depth
Cyber Resilience Act: a guide to the regulation
What Regulation (EU) 2024/2847 requires of products with digital elements: dates, scope, important and critical products, essential requirements, reporting, substantial modification, open source and penalties, with references to the articles.
In short for businesses
- Who it concerns
- You make, import or sell in the EU hardware or software products that connect to a device or a network, from IP cameras to routers, from apps to business software. Products with their own sector rules, such as medical devices and vehicles, are excluded.
- What to do
- If you are the manufacturer: design the product to the security requirements of Annex I, fix vulnerabilities throughout the support period, prepare the technical documentation, carry out the conformity assessment and affix the CE marking. If you import or distribute: check that the product has the CE marking and the documents.
- When
- Since 11 September 2026 manufacturers must report exploited vulnerabilities and severe incidents within 24 hours through ENISA’s platform. Everything else applies from 11 December 2027.
A simplified summary: details and exceptions are below. Terms with a dotted underline link to the glossary.
Regulation (EU) 2024/2847, known as the Cyber Resilience Act (CRA), is the first EU law to set horizontal cybersecurity requirements, that is, requirements that apply to almost all hardware and software products sold in the Union. It covers the whole product lifecycle: from design until the end of the period during which the manufacturer must provide security updates.
The regulation lays down four groups of rules (Art. 1):
- essential cybersecurity requirements for the design, development and production of products;
- the vulnerability handling processes the manufacturer must maintain while the product is in use;
- the obligations of economic operators (manufacturers, importers, distributors), including conformity assessment and CE marking;
- market surveillance and penalties.
Key dates
| Date | What happens |
|---|---|
| 20 November 2024 | Publication in the Official Journal of the EU |
| 10 December 2024 | Entry into force (Art. 71(1)) |
| 1 December 2025 | Publication of Implementing Regulation (EU) 2025/2392, with the technical descriptions of important and critical products (Art. 7(4)); in force since 21 December 2025 |
| 11 June 2026 | Chapter IV (Arts 35-51) on the notification of conformity assessment bodies applies |
| 11 September 2026 | The reporting obligations of Art. 14 apply, also to products already on the market |
| 11 December 2026 | Member States strive to ensure a sufficient number of notified bodies, to avoid bottlenecks in conformity assessment (Art. 35(2)) |
| 11 December 2027 | The regulation applies in full (Art. 71(2)) |
| 11 June 2028 | EU-type examination certificates issued on cybersecurity under other EU legislation expire (Art. 69(1)) |
Other deadlines, such as the Commission’s reports, are listed in the document record.
Which products it covers
In practice: if you sell in the EU, as part of a commercial activity, a hardware or software product that connects to a device or network, even indirectly, the CRA applies to you, even if the product is free.
The CRA applies to products with digital elements made available on the market whose intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network (Art. 2(1)).
The definitions in Art. 3 explain the terms:
- product with digital elements: any software or hardware product and its remote data processing solutions, including components placed on the market separately (point 1);
- remote data processing: data processing at a distance designed by or under the responsibility of the manufacturer, without which the product could not perform one of its functions, such as the cloud service behind an app that controls a device (point 2);
- making available on the market: supply for distribution or use in the course of a commercial activity, whether in return for payment or free of charge (point 22).
An indirect connection is enough: a device that does not go online on its own but connects to a networked system is in scope. What matters is the commercial activity, not the price: a free product is covered if it is supplied in the course of a commercial activity.
Excluded products
In practice: medical devices, motor vehicles, certified aviation products and marine equipment follow their own sector rules. For other regulated products the CRA applies unless a delegated act excludes it.
Products already governed by sector rules that cover cybersecurity are excluded:
| Products | Sector rules | CRA article |
|---|---|---|
| Medical devices | Reg. (EU) 2017/745 | Art. 2(2) |
| In vitro diagnostic medical devices | Reg. (EU) 2017/746 | Art. 2(2) |
| Motor vehicles | Reg. (EU) 2019/2144 | Art. 2(2) |
| Civil aviation, if certified | Reg. (EU) 2018/1139 | Art. 2(3) |
| Marine equipment | Dir. 2014/90/EU | Art. 2(4) |
Other sector rules do not exclude the CRA automatically: the Commission can limit or exclude its application by a delegated act, where this is consistent with the regulatory framework for those products and the sector rules achieve at least the same level of protection (Art. 2(5)). Delegated Regulation (EU) 2025/1535 did so for L-category vehicles, except pedal-assisted L1e cycles.
Also excluded are:
- spare parts that replace identical components and are manufactured to the same specifications (Art. 2(6));
- products developed or modified exclusively for national security or defence purposes and products designed to process classified information (Art. 2(7)).
Default, important and critical products
In practice: the category does not change the requirements; it decides whether you can assess the product yourself or need a third-party body. What counts is the product’s core functionality, not the components inside it.
All products in scope must meet the same essential requirements. The category changes how conformity is demonstrated, and it depends on the product’s core functionality, that is, the function that characterises it, not its architecture (Art. 7(1)).
| Category | What it includes | How conformity is demonstrated |
|---|---|---|
| Default | All products whose core functionality is not listed in Annexes III and IV | The manufacturer may use internal control, module A (Art. 32(1)) |
| Important, class I (Annex III) | Among others: identity management and privileged access management systems, browsers, password managers, anti-malware software, VPNs, SIEM systems, operating systems, routers, modems and switches, smart home products with security functions (locks, cameras), connected toys with interactive or geolocation features | Internal control only if the manufacturer fully applies harmonised standards, common specifications or a European certification scheme; otherwise EU-type examination (modules B+C) or full quality assurance (module H) (Art. 32(2)) |
| Important, class II (Annex III) | Hypervisors and container runtime systems, firewalls, intrusion detection and prevention systems, tamper-resistant microprocessors and microcontrollers | Always with a notified body (modules B+C or H) or a European certification scheme at assurance level at least ‘substantial’ (Art. 32(3)) |
| Critical (Annex IV) | Hardware devices with security boxes, smart meter gateways and other devices for advanced security purposes, smartcards and secure elements | A European cybersecurity certificate, where a delegated act requires one (Art. 8(1)); until then, the class II procedures (Art. 32(4)) |
Important categories either perform functions that are essential for the cybersecurity of other products or networks (authentication, intrusion detection, network protection) or central system functions which, if compromised, can harm many other products or the health and safety of users (Art. 7(2)). The exact technical description of each category is in Implementing Regulation (EU) 2025/2392.
The regulation says so explicitly: integrating an important product does not by itself make the final product important (Art. 7(1)). A smart TV with a built-in firewall remains a default product, because its core function is playing content; a firewall sold as a product in its own right is class II.
Components and the supply chain
In practice: whoever sells the final product is also responsible for third-party components, open source included. A component sold on its own is a product in its own right, with its own CE marking.
The CRA distinguishes three cases.
- Component sold separately: it is a product with digital elements in its own right (Art. 3, point 1), with its own conformity assessment, CE marking and support period. Its category depends on its own core functionality: a microcontroller with security-related functionalities sold on its own falls under class I.
- Component integrated and not sold separately: it is not assessed on its own. The manufacturer of the final product is responsible and must exercise due diligence on third-party components, including open-source ones, so that they do not compromise the product’s cybersecurity (Art. 13(5)). If it finds a vulnerability in a component, it reports it to whoever maintains it (Art. 13(6)).
- Identical spare part: outside the CRA (Art. 2(6)). A spare part that differs from the original, or adds functions, must instead be assessed under the rules on substantial modification.
Example: a digital pressure transmitter for an industrial plant measures pressure and sends the value over a network. It is in scope of the CRA for its firmware, communication module (wireless, Ethernet, fieldbus) and any cloud portal; its core function is not listed in Annexes III and IV, so it is a default product even if it contains a microcontroller with security functions. The manufacturer is responsible for the whole product, components included, and for the support period.
Essential requirements (Annex I)
In practice: the product must be secure by design, with no known vulnerabilities and secure default settings; the manufacturer keeps an SBOM and fixes vulnerabilities with free updates throughout the support period, normally at least five years.
Annex I, Part I covers the properties of the product. On the basis of the risk assessment the manufacturer must carry out and document (Art. 13(2)-(3)), the product:
- is placed on the market without known exploitable vulnerabilities;
- has a secure by default configuration, with the possibility to reset it to its original state;
- receives security updates, where applicable automatic and enabled by default, with an easy way to opt out;
- protects against unauthorised access (authentication, identity management) and reports it;
- protects the confidentiality and integrity of data, for example through encryption, and processes only the data that are necessary;
- protects the availability of essential functions, including against denial-of-service attacks, and limits attack surfaces;
- records security-relevant activity and lets users delete data and settings securely and permanently.
Annex I, Part II covers vulnerability handling. The manufacturer:
- draws up a software bill of materials (SBOM) in a machine-readable format, covering at least the top-level dependencies;
- remediates vulnerabilities without delay and, where technically feasible, provides security updates separately from functionality updates;
- carries out regular security tests and reviews;
- publishes information on fixed vulnerabilities and puts in place a coordinated vulnerability disclosure policy, with a contact address for reports;
- distributes updates securely and, unless otherwise agreed for tailor-made products, free of charge.
The support period reflects the expected time the product will be in use and is at least five years, unless the product is expected to be used for less time (Art. 13(8)). The end date must be stated to users (Annex II, point 7). The technical documentation and the EU declaration of conformity are kept for at least ten years (Art. 13(13)).
Reporting vulnerabilities and incidents
In practice: from 11 September 2026, actively exploited vulnerabilities and severe incidents must be reported on the ENISA platform within 24 hours, also for products already sold.
From 11 September 2026 the manufacturer must notify any actively exploited vulnerability and any severe incident having an impact on the security of the product. Notifications go simultaneously to the CSIRT designated as coordinator and to ENISA, through the single reporting platform run by ENISA (Art. 14(1) and (3); Art. 16).
| Stage | Actively exploited vulnerability | Severe incident |
|---|---|---|
| Early warning | within 24 hours of the manufacturer becoming aware | within 24 hours |
| Notification | within 72 hours | within 72 hours |
| Final report | within 14 days after a corrective or mitigating measure is available | within one month of the notification |
The obligation also covers products placed on the market before 11 December 2027 (Art. 69(3)). The manufacturer also informs the affected users and, where needed, the measures they can take (Art. 14(8)). Micro and small enterprises are not fined for missing only the 24-hour early-warning deadline (Art. 64(10)).
The platform has been operational since 11 September 2026, in an initial version that ENISA will extend over the following months (it moved to version 1.3 on 4 November 2026). Access is through the platform portal (opens in a new tab) with an EU Login account with multi-factor authentication: a representative of the manufacturer registers, chooses the coordinating CSIRT (normally that of the Member State of main establishment, Art. 14(7)) and can invite colleagues; the CSIRT then verifies the registration. One notification per event is enough, even if the manufacturer has establishments in several Member States. For now the platform is in English only, does not accept the voluntary reports of Art. 15 and offers no API: these will come in later phases. Instructions and frequently asked questions are on ENISA’s page on the platform (opens in a new tab) and in the FAQ (opens in a new tab); the contacts of the coordinating CSIRTs are in ENISA’s list (opens in a new tab).
Who must report in the Member States, and to which authority, is summarised in Obligations compared.
Products already on the market and substantial modification
In practice: products placed on the market before 11 December 2027 need not be redesigned unless substantially modified afterwards; a security update is not a substantial modification. The reporting obligation applies anyway.
Products placed on the market before 11 December 2027 must meet the CRA requirements only if, from that date, they undergo a substantial modification (Art. 69(2)). They remain subject to the reporting obligations of Art. 14 in any case.
A substantial modification is a change after placing on the market which affects compliance with the essential requirements in Annex I, Part I, or which modifies the intended purpose for which the product was assessed (Art. 3, point 30). In practice, this is the case when the change alters functions, purpose or risk profile (for example by widening the attack surface) in a way not foreseen in the initial risk assessment.
Recital 39 applies the rule to software updates:
- a security update that does not modify the intended purpose is not a substantial modification, even if it changes some functions solely to reduce risk;
- a minor functionality update, such as a visual enhancement or new interface languages, generally is not one either;
- an update that modifies the intended purpose or increases the cybersecurity risk is.
The same test applies to repairs, maintenance and spare parts: if they do not change the core functionality and do not increase the risk already assessed, they are not substantial modifications. Anyone who substantially modifies a product is considered a manufacturer and takes on the manufacturer’s obligations (Arts 21 and 22).
High-risk AI systems
A product with digital elements that is also a high-risk AI system under Regulation (EU) 2024/1689 (AI Act) is deemed to comply with the cybersecurity requirements of Art. 15 of the AI Act if it meets the CRA’s essential requirements and the EU declaration of conformity shows this (Art. 12(1)). The AI Act conformity assessment procedure normally applies (Art. 12(2)); however, important and critical products under the CRA remain subject to the CRA’s stricter procedures for the cybersecurity part (Art. 12(3)).
Open-source software
In practice: publishing open-source software outside a commercial activity is outside the CRA; whoever integrates it into a product they sell is responsible for it as the manufacturer.
Free and open-source software developed or supplied outside a commercial activity is not covered by the CRA (Recitals 17-19). When it is made available in the course of a commercial activity, whoever does so is a manufacturer like any other.
The CRA creates an intermediate figure, the open-source software steward: a legal person, other than a manufacturer, that provides systematic and sustained support for the development of open-source software intended for commercial activities, such as certain foundations (Art. 3, point 14). Stewards have light obligations: they put in place and document a cybersecurity policy, cooperate with market surveillance authorities and report vulnerabilities and incidents to the extent they are involved in development (Art. 24). Stewards are not subject to administrative fines (Art. 64(10)).
Manufacturers of open-source products listed in Annex III may use internal control if they make the technical documentation public (Art. 32(5)).
Penalties
In practice: fines are set by each country, up to €15 million or 2.5% of worldwide turnover for the most serious breaches.
Member States set the penalties, within these maximum amounts (Art. 64):
| Infringement | Maximum |
|---|---|
| Essential requirements in Annex I and obligations in Arts 13 and 14 | EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher |
| Other obligations of operators and notified bodies | EUR 10 million or 2% of turnover |
| Incorrect, incomplete or misleading information to authorities and notified bodies | EUR 5 million or 1% of turnover |
Notified bodies and conformity assessment
In practice: for default products internal control is enough; class II and critical products, and class I products without fully applied harmonised standards, need a notified body, to be involved early.
Before affixing the CE marking, the manufacturer demonstrates that the product meets the essential requirements using one of the procedures in Annex VIII (Art. 32). For default products it can do so on its own. A notified body is involved for important products of class I that do not fully apply harmonised standards, common specifications or a European certification scheme, for class II products and for critical products without mandatory certification.
| Procedure (Annex VIII) | Who carries it out | What happens |
|---|---|---|
| Internal control (module A) | The manufacturer alone | It draws up the technical documentation and the EU declaration of conformity and affixes the CE marking |
| EU-type examination (module B) and conformity to type (module C) | The notified body for module B, the manufacturer for module C | The body examines the technical documentation and samples of the product, carries out the necessary tests and issues the EU-type examination certificate; it also carries out periodic audits of vulnerability handling. The manufacturer then ensures that production conforms to the certified type |
| Full quality assurance (module H) | The notified body | It assesses and approves the manufacturer’s quality system for design, development, testing and vulnerability handling, and then monitors it |
| European cybersecurity certification scheme | The certification body under the scheme | Possible where a scheme adopted under Regulation (EU) 2019/881 is available and applicable (Art. 27(9)) |
Who can become a notified body. A conformity assessment body with legal personality that is a third party independent of the manufacturer and of the products it assesses, with staff competent also in the Annex I requirements, civil liability insurance, professional secrecy and staff pay that does not depend on the number or results of assessments (Art. 39). If it complies with the harmonised standards for conformity assessment bodies, it is presumed to meet these requirements (Art. 40).
How it is notified. Each Member State designates a notifying authority (Art. 36). The body applies in the Member State where it is established, normally with an accreditation certificate (Art. 42); the authority notifies it to the Commission and the other Member States through the NANDO system, and the body may operate if no objections are raised within two weeks (with accreditation) or two months (without) (Art. 43). The Commission assigns an identification number and publishes the list of notified bodies (Art. 44).
What they must do. They carry out assessments proportionately, taking into account the size of the undertaking, in particular microenterprises and SMEs, without lowering the required rigour (Art. 47(2)-(3)). If the product does not conform they do not issue the certificate, and if it no longer conforms after issue they may suspend or withdraw it (Art. 47(4)-(6)). Fees for microenterprises and SMEs, including start-ups, are reduced in proportion to their needs (Art. 32(6)). An appeal procedure against the decisions of notified bodies must be available (Art. 48).
The dates. The rules on notifying bodies (Chapter IV) apply from 11 June 2026, and Member States endeavour to ensure that by 11 December 2026 there are enough notified bodies to avoid bottlenecks (Art. 35(2); Art. 71(2)). The up-to-date list of bodies is in the Commission’s NANDO database (opens in a new tab).
The CRA in the New Legislative Framework
The CRA follows the EU model for product safety (the “New Legislative Framework”): essential requirements set by law, harmonised standards that give a presumption of conformity, notified bodies for higher-risk products, the EU declaration of conformity and CE marking, and market surveillance under Regulation (EU) 2019/1020. It sits alongside other product rules, such as the Machinery Regulation, and the NIS 2 Directive, which instead covers the security of entities that provide services.
The status of national implementing measures (market surveillance authorities, penalties) is on the CRA transposition and implementation page.
Follow-up acts and guidance
Since its adoption, further acts have supplemented or amended the Regulation, and documents have been published to help apply it. The regulations are binding; the Commission guidance and ENISA’s technical guides help to interpret and apply the requirements, but they do not create new obligations or confer a presumption of conformity.
| Act | What it adds |
|---|---|
| Directive (EU) 2024/2853 on liability for defective products (23 October 2024) | Does not amend the CRA but links its obligations to civil liability: for products placed on the market after 8 December 2026, software is a product and the manufacturer is liable, without fault, for damage caused by a defective product. Safety-relevant cybersecurity requirements count when assessing defectiveness (Art. 7(2)(f)), and the manufacturer is not exempted where the defect is due to software or to the failure to supply the updates needed to maintain safety, as long as they are within its control (Art. 11(2)). To be transposed by 9 December 2026 |
| Regulation (EU) 2025/327 (opens in a new tab) on the European Health Data Space (11 February 2025), Art. 104 | Amends Arts 13, 31 and 32 of the CRA: manufacturers of electronic health record systems demonstrate conformity with the essential requirements through the conformity assessment procedure of that regulation (Art. 32(5a)); for products also subject to other EU acts, the risk assessment may be part of the one required by those acts, with a single set of technical documentation |
| Standardisation request M/606 (opens in a new tab) (Commission Implementing Decision C(2025) 618), accepted by CEN, CENELEC and ETSI on 3 April 2025 | Requests 41 European standards in support of the CRA: horizontal standards for all products (including on vulnerability handling) and vertical standards for the important and critical product categories in Annexes III and IV. Once cited in the Official Journal as harmonised standards, they will give a presumption of conformity to those who apply them (Art. 27) |
| Amendment to standardisation request M/606 (opens in a new tab) (Commission Implementing Decision C(2026) 7861, 10 November 2026) | Replaces Annex I of M/606 and moves the 2026 deadlines back by three months: the horizontal standard on secure design and the one on vulnerability handling move from 30 August to 30 November 2026, and the 26 vertical standards for important and critical products from 30 October 2026 to 31 January 2027; the other 13 horizontal standards stay at 30 October 2027. It applies unless CEN, CENELEC and ETSI reject it within one month (Art. 2) |
| Delegated Regulation (EU) 2025/1535 (opens in a new tab) (29 July 2025) | Excludes from the CRA products falling within Regulation (EU) No 168/2013 on L-category vehicles, except pedal-assisted L1e cycles (Art. 2(5)); in force since 18 November 2025 |
| Implementing Regulation (EU) 2025/2392 (opens in a new tab) (28 November 2025) | Gives the technical description of each category of important (classes I and II, Annex III) and critical (Annex IV) products: it determines which products fall within them and therefore which conformity assessment procedure applies (Art. 7(4)); in force since 21 December 2025 |
| Delegated Regulation (EU) 2026/881 (opens in a new tab) (11 December 2025) | Sets the terms and conditions under which the coordinating CSIRT receiving the notification of an actively exploited vulnerability or a severe incident may delay its dissemination to other CSIRTs, on cybersecurity grounds and for the strictly necessary time, informing ENISA immediately (Art. 14(9); Art. 16(2)); in force since 10 May 2026 |
| Commission guidance on the application of the CRA (opens in a new tab) (Communication C(2026) 7851 of 9 November 2026, OJ C/2026/6013 of 17 November 2026; content already approved on 27 July 2026 as C(2026) 5252) | The first guidance under Art. 26: scope (software, source code, complex systems, products designed before the CRA), free and open-source software, repairs, spare parts and updates as substantial modifications, support period, core functionality of important and critical products, risk assessment, remote data processing, reporting and vulnerability handling, with 67 practical examples and particular attention to microenterprises and SMEs. It is not binding; formally adopted on 9 November 2026, it is published in the Official Journal in all EU languages |
| ENISA, SME Cyber Resilience Maturity Assessment Model (opens in a new tab) (13 July 2026) | A model, with a spreadsheet tool, that lets micro, small and medium-sized enterprises manufacturing products with digital elements assess how ready they are for the CRA requirements |
| ENISA, Secure by Design and Default Playbook (opens in a new tab) (30 July 2026) | 22 practical secure-by-design and secure-by-default principles for SMEs, with the evidence to collect and the checks to run before release; an annex maps them to the essential requirements of Annex I |
| ENISA Technical Advisory for Software Bill of Materials (opens in a new tab) (22 October 2026) | How to produce, manage and share the software bill of materials (SBOM): life cycle, threats and security measures. It takes the CRA’s SBOM obligations into account but describes good practices that go beyond them, and it is not a legal interpretation of the Regulation |
| ENISA Technical Advisory on Secure Update Mechanisms (opens in a new tab) (4 November 2026) | Threats and controls across the update life cycle (integrity, secure distribution, separating security from functional updates, automatic updates and user notification), linked to the requirements of Parts I and II of Annex I; it does not confer a presumption of conformity |
| ENISA, CRA-Module B and H: CABs accreditation for notification (opens in a new tab) (16 November 2026) | A non-binding technical reference for notifying authorities and national accreditation bodies: it compares the requirements for CRA notified bodies (Modules B and H) with those under the RED and the EUCC scheme and sets out the additional competences to be demonstrated. An existing accreditation or notification does not confer automatic eligibility for CRA notification |
As of 17 November 2026, no CRA harmonised standard has yet been cited in the Official Journal.
Official sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Official Journal of the EU (opens in a new tab)
- Implementing Regulation (EU) 2025/2392 on the technical descriptions of important and critical products (opens in a new tab)
- Delegated Regulation (EU) 2025/1535 on L-category vehicles (opens in a new tab)
- Delegated Regulation (EU) 2026/881 on delaying the dissemination of notifications (opens in a new tab)
- Commission guidance on the application of the CRA, OJ C/2026/6013 (opens in a new tab)
- Implementing Decision C(2026) 7861 amending standardisation request M/606 (opens in a new tab)
- ENISA, CRA single reporting platform (opens in a new tab)
- Regulation (EU) 2024/1689 (AI Act) (opens in a new tab)
This page summarises the text of the act for information only and is not legal advice. Only the text published in the Official Journal of the European Union is authentic.