- The Cyber Resilience Act (Regulation (EU) 2024/2847) covers hardware and software products with digital elements made available on the EU market, plus the remote data processing they need to perform their functions
- Manufacturers carry most of the obligations. Importers and distributors have their own checking, cooperation and corrective duties, and become manufacturers if they rebrand or substantially modify a product
- Products are default, important (Class I or Class II, Annex III) or critical (Annex IV). The category decides the conformity assessment route under Article 32
- Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents through the single reporting platform, under two separate sets of deadlines
- The support period must be at least five years unless the product is expected to be in use for less time (Article 13(8))
- Most other obligations apply from 11 December 2027
What the Cyber Resilience Act covers
The Cyber Resilience Act (CRA) sets cybersecurity requirements for products with digital elements sold in the EU. It entered into force on 10 December 2024. Before it, EU product law had no general rule that connected products be designed securely or patched after sale. From 11 December 2027, a manufacturer that places such a product on the EU market without meeting the essential requirements, or without handling its vulnerabilities over the support period, can face fines, withdrawal orders and recalls.
The duties fall on the economic operators that make these products available on the EU market: manufacturers, importers and distributors. The CRA does not place obligations on an organisation simply because it uses software or connected devices in its own operations. As a buyer, you can ask suppliers for evidence of CRA conformity, but the legal duties sit with them.
A product with digital elements is any software or hardware product, including its remote data processing solutions, whose intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network. That covers smart home devices, routers, industrial controllers, operating systems, desktop and mobile apps, password managers and development tools when they are supplied in the course of a commercial activity. Products already covered by sector rules, such as medical devices, motor vehicles, civil aviation and marine equipment, are excluded or partly excluded (Article 2).
Software as a service is a common source of confusion. The CRA does not regulate SaaS as such. A cloud service that runs entirely on the provider's infrastructure and is not part of a product falls outside it, and may instead fall under NIS2. The Act does cover remote data processing solutions: processing at a distance that the manufacturer designs or controls and without which the product could not perform one of its functions (Articles 3(2) and 6). The cloud back end of a smart camera or the licence and sync service of an installed application can be in scope as part of that product.
The CRA is EU law and does not apply to products sold only in Great Britain, where the Product Security and Telecommunications Infrastructure Act 2022 sets baseline rules for consumer connectable products. If you sell software or connected hardware to customers in the EU, the CRA applies to those products wherever your business is based.
Manufacturers, importers and distributors
Manufacturers develop or manufacture a product with digital elements, or have it designed or made, and market it under their own name or trademark. They meet the essential requirements, run vulnerability handling, carry out the conformity assessment, draw up technical documentation and the EU declaration of conformity, affix the CE marking and report under Article 14.
Importers place on the EU market products from a manufacturer established outside the EU (Article 19). Before placing a product on the market, an importer checks that:
- the manufacturer has carried out the right conformity assessment and drawn up the technical documentation;
- the product carries the CE marking and comes with the EU declaration of conformity (or a simplified version) and the required user information;
- the manufacturer has identified a single point of contact for vulnerabilities and has vulnerability handling processes in place.
If an importer has reason to believe a product does not conform, it must not place it on the market until it does. If the product presents a significant cybersecurity risk, the importer informs the manufacturer and the market surveillance authorities. After placing the product, importers keep a copy of the declaration and the technical documentation available, tell the manufacturer about vulnerabilities they learn of, take corrective action when needed and cooperate with authorities.
Distributors make products available without being the manufacturer or importer (Article 20). They act with due care: they check the CE marking, the accompanying information and that the manufacturer and importer have met their identification duties. They must not supply a product they consider non-conforming. When they learn of non-conformity or a vulnerability, they inform the manufacturer, take corrective measures within their control and cooperate with market surveillance authorities.
An importer or distributor that places a product on the market under its own name or trademark, or carries out a substantial modification of a product already on the market, is treated as the manufacturer (Article 21). Any other person who substantially modifies a product becomes the manufacturer for the modified part (Article 22). This catches white-label hardware and OEM software arrangements.
The detailed obligations are on our companion page, Cyber Resilience Act requirements in practice. It covers product categories and conformity assessment, the essential requirements, SBOMs, support periods, Article 14 reporting, open source, products already on the market and the evidence authorities will ask for.
The implementation timeline
CRA, NIS2 and GDPR compared
| CRA | NIS2 | GDPR | |
|---|---|---|---|
| What it regulates | Products with digital elements | The security of an entity's own network and information systems and services | Processing of personal data |
| Who it applies to | Manufacturers, importers, distributors and open-source software stewards | Essential and important entities in listed sectors | Controllers and processors |
| What triggers reporting | Actively exploited vulnerability or severe incident affecting the product | Significant incident affecting the entity's services | Personal data breach likely to result in a risk to individuals |
| Who receives the report | Coordinating CSIRT and ENISA, through the single reporting platform | National CSIRT or competent authority | Data protection authority, and individuals if the risk is high |
| Deadlines | 24 hours, 72 hours, then 14 days after a fix or one month | 24 hours, 72 hours, then one month | 72 hours to the supervisory authority where there is a risk; individuals without undue delay if the risk is high (Article 34) |
A software company can sit under all three: the CRA for the products it sells, NIS2 for its own operations if it is in a covered sector, and GDPR wherever it processes personal data. For UK organisations, UK GDPR and the ICO apply to processing in the UK, and the NIS Regulations 2018 apply in place of NIS2.
What to do now
Reporting already applies, and the main obligations start on 11 December 2027. Technical documentation, SBOM tooling and third-party assessments all take time to set up, so plan the work now.
Step 1: Build the product inventory
List every product you develop, import or distribute in the EU, your role for each, and any remote data processing it depends on. Check each against the definition of a product with digital elements and the exclusions in Article 2.
Step 2: Classify by core functionality
Compare each product's core functionality with Annexes III and IV and the Commission's technical descriptions. If a product is Class II or critical, contact a notified body early, because capacity may be limited.
Step 3: Make reporting work
Register on the single reporting platform, name who can submit, and agree how a report of active exploitation reaches them within hours. Test the procedure against both the vulnerability and the incident timelines.
Step 4: Generate SBOMs and run vulnerability handling
Produce an SBOM for each release, connect it to vulnerability monitoring and publish a coordinated vulnerability disclosure policy with a contact address.
Step 5: Set support periods and plan documentation
Decide the support period for each product and show the end date at the point of sale. Start the technical documentation and risk assessment for products you will place on the market after 11 December 2027.
Our cybersecurity team supports manufacturers, importers and distributors with CRA readiness assessments, SBOM implementation and vulnerability handling design. Our compliance practice helps with technical documentation and conformity assessment preparation for UK businesses selling into the EU.
The fine structure
Market surveillance authorities in each member state enforce the CRA. Article 64 sets the maximum administrative fines:
- Essential requirements and the obligations in Articles 13 and 14: up to €15 million or 2.5% of total worldwide annual turnover, whichever is higher.
- Other obligations, including those of importers and distributors, conformity assessment and CE marking: up to €10 million or 2% of total worldwide annual turnover, whichever is higher.
- Incorrect, incomplete or misleading information given to notified bodies or market surveillance authorities: up to €5 million or 1% of total worldwide annual turnover, whichever is higher.
Microenterprises and small enterprises cannot be fined for missing the 24-hour early warning deadline, and open-source software stewards cannot be fined (Article 64(10)). Authorities can also order corrective action, withdraw or recall products and restrict them across the EU.