The EU Cyber Resilience Act makes cybersecurity a condition for selling connected hardware and software in the EU.
If you sell a router or a desktop app under your own brand, you can have the duties of a manufacturer even if another company built it.
Manufacturers already have to report actively exploited vulnerabilities and severe incidents affecting product security. From 11 December 2027, they must also show that new products meet the Act’s cybersecurity requirements before placing them on the EU market.
Discuss a product or contract
Which products does the EU Cyber Resilience Act cover?
Under Regulation (EU) 2024/2847, the starting point is the product you supply. Check these three conditions.
Is it a product with digital elements? That means a software or hardware product, including its remote data processing solutions. Software or hardware components placed on the market separately count as products in their own right.
Is it made available on the EU market in the course of a commercial activity? Charging is not required. Supplying a product free of charge still counts if it is part of a commercial activity, for example where it is used to monetise other services.
Does its intended purpose or reasonably foreseeable use include a data connection? The connection can be direct or indirect, logical or physical, to a device or network.
If all three answers are yes, the product is likely in scope, subject to the exclusions below.
Cloud functions: the two-part test
The CRA covers remote data processing only where both conditions are met. First, the software for the processing is designed and developed by the manufacturer, or under its responsibility. Second, without that processing the product could not perform one of its functions. A standalone cloud service that customers use through a browser is generally outside the CRA; the recitals point to the NIS2 Directive (Directive (EU) 2022/2555) for cloud services. A cloud backend that a connected device or app needs to work can be part of the product.
| Business model | Initial view | Fact that could change it |
|---|---|---|
| Connected device with a companion app | Device and app are in scope | The device has no direct or indirect data connection; the app may still be in scope |
| Cloud dashboard that a device or app needs to work | Likely part of the product as remote data processing | A third party designs and runs the dashboard under its own responsibility |
| Standalone SaaS used through a browser | Generally outside the CRA; NIS2 may apply | You also supply a desktop client, app or device that depends on it |
| Software installed on the customer’s systems | Likely in scope | It is not supplied in the course of a commercial activity |
| Library, SDK or firmware sold separately | A product in its own right | It is free and open-source software that you do not monetise |
Open source and sector exclusions
Free and open-source software that its developer does not monetise is outside the CRA. Indicators of commercial activity include charging a price, charging for support beyond cost recovery, or using the software to monetise other services. Foundations that sustainably support open-source projects intended for commercial use may be “open-source software stewards”, with a lighter regime. A manufacturer that builds open-source components into its own product must still exercise due diligence over them.
Some products are excluded because another EU regime already governs them: medical devices and in vitro diagnostic devices, motor vehicles, certified civil aviation products and marine equipment. Identical spare parts and products developed exclusively for national security or defence are also excluded. The exclusion follows the legal regime that applies to the product, not the customer’s industry. Software used in a hospital is not excluded unless it is itself regulated as a medical device.
Consider a UK supplier that sells a connected sensor and a companion app in Poland. Both are products with digital elements. The cloud dashboard is part of the product if the UK company designs it, or has it built under its responsibility, and the sensor or app cannot perform a function without it.

Which company is responsible?
The CRA assigns duties by role in the supply chain. One business can hold different roles for different products.
| Role | Who it is | Core responsibility |
|---|---|---|
| Manufacturer | Develops or manufactures the product, or has it designed or made, and markets it under its own name or trademark | Design, risk assessment, conformity assessment, documentation, vulnerability handling, reporting |
| Importer | Established in the EU; places on the market a product bearing the name of a business established outside the EU | Checks that the manufacturer completed conformity assessment and documentation, and that the product has CE marking and the required information |
| Distributor | Any other business in the supply chain that makes the product available without changing its properties | Checks that the product carries CE marking and the required information |
| Authorised representative | Established in the EU and appointed by the manufacturer under a written mandate | Only the tasks in the mandate, such as keeping documentation available and cooperating with authorities |
Two rules change the picture. An importer or distributor that places a product on the market under its own name or trademark, or substantially modifies a product already on the market, is treated as the manufacturer. Any other business that substantially modifies a product and makes it available becomes its manufacturer too. For a business other than the manufacturer, importer or distributor, Article 22 applies to the modified part, or to the whole product if the change affects its cybersecurity as a whole.
Writing code does not, by itself, make a company the manufacturer of the final product. A Polish subsidiary that develops software for its UK parent is usually a supplier within the group. If the Polish company places the product on the EU market under its own name, its position changes.
Appointing an authorised representative is voluntary under Article 18 of the CRA. The mandate cannot cover the manufacturer’s core design and vulnerability-handling duties. Other EU product rules that may apply to the same product, such as radio equipment rules, are assessed separately and may have their own requirements.
Suppose the UK company sells the sensor under its own brand. It is the manufacturer. The Polish company is the importer and must check the manufacturer’s conformity work before placing units on the market. If the importer started selling the sensor under its own brand, it would take on the manufacturer’s duties.
If your distributor asks you to take responsibility for updates it controls, CGO Legal can review the proposed terms. See which CRA clauses to negotiate in software and distribution agreements for examples covering warranties, security updates and recall costs.

Cyber Resilience Act deadlines in 2026 and 2027
Entry into force and application are different things. The CRA entered into force on 10 December 2024, but its obligations apply in stages. This section is accurate as of 18 November 2026.
| Date | Who it affects | What it means in practice |
|---|---|---|
| 11 June 2026 | Conformity assessment bodies and the authorities that notify them | Rules on notified bodies apply, so third-party assessment capacity can be built before 2027 |
| 11 September 2026 | Manufacturers | Reporting of actively exploited vulnerabilities and severe incidents applies, including for products placed on the market before December 2027 |
| 11 December 2027 | Manufacturers, importers, distributors | Main product requirements apply. Check the placement date and any subsequent substantial modification. |
| 11 June 2028 | Holders of certain certificates under other EU product legislation | EU type-examination certificates and approval decisions covering cybersecurity remain valid until this date, unless they expire earlier |
Which release date counts?
Products placed on the EU market before 11 December 2027 are subject to the main CRA requirements only if they undergo a substantial modification from that date. Hardware and software are treated differently.
For hardware, record when each unit was first made available on the EU market in the course of commercial activity. Shipping records can help establish the facts. The model launch date alone cannot answer the question.
For standalone software, the Commission distinguishes identical copies, different variants and subsequent iterations. Copies of the same software share the date of first EU supply once development is complete. Different builds with different components, configurations or enabled features can be distinct products. A later iteration changes the placement date if it constitutes a substantial modification.
Consider three releases around the December 2027 deadline.
| What changes | How to assess it |
|---|---|
| Another sensor of the same model | Check when this unit was first made available in the EU. |
| Another download of the identical standalone app | Use the date the completed software was first supplied commercially on the EU market. |
| A release adds remote control of machinery | Assess the change to intended purpose and conformity. The version number alone does not determine the outcome. |
What manufacturers do before and after launch
The manufacturer’s obligations follow the product’s life cycle.
| Stage | What the manufacturer does |
|---|---|
| Design and development | Assesses cybersecurity risks and applies the results; designs the product to meet the essential requirements in Annex I; exercises due diligence over third-party and open-source components |
| Before placing on the market | Prepares technical documentation; completes the conformity assessment; draws up the EU declaration of conformity; affixes the CE marking |
| During the support period | Handles vulnerabilities, including a software bill of materials, a coordinated vulnerability disclosure policy and security updates provided free of charge; keeps the risk assessment up to date |
| After the support period | Retain the declaration and documentation for at least ten years from placement on the market, or the support period if longer. Keep each issued security update available for at least ten years after issue or for the remainder of the support period, whichever is longer. |
Conformity assessment: self-assessment or a third party
Most products can follow internal control, where the manufacturer assesses conformity itself. Products listed as “important” or “critical” in Annexes III and IV follow stricter routes. For important Class I products, internal control is available only where harmonised standards, common specifications or a suitable certification scheme have been applied in full; otherwise a notified body is involved. Important Class II products need third-party assessment or certification. Critical products may require European cybersecurity certification. There is no general duty to buy a certificate. Article 32(4) provides a specific route for qualifying free and open-source software in Annex III. If the technical documentation is publicly available when the product is placed on the market, the manufacturer may use one of the procedures in Article 32(1), including internal control.
Setting the support period
The manufacturer sets the support period to reflect how long the product is expected to be in use. Relevant factors include reasonable user expectations, the nature and purpose of the product, comparable products, the operating environment and the support periods of third-party components that provide core functions. The period must be at least five years, unless the product is expected to be in use for less time. The reasons for the chosen period go into the technical documentation.
Suppose the UK manufacturer plans to launch the sensor in 2028 with seven years of support. Its cellular module supplier will stop issuing security fixes in 2031. Before ordering the module, the team can negotiate longer support, select another component or establish how it will maintain or replace the module for the rest of the sensor’s support period.

When must a manufacturer report a vulnerability or incident?
The reporting duty applies to two events, not to every bug or IT incident.
An actively exploited vulnerability is one where there is reliable evidence that a malicious actor has exploited it in a system without the owner’s permission.
A severe incident affects the security of the product. It is severe if it has, or could have, a negative effect on the availability, authenticity, integrity or confidentiality of sensitive or important data or functions. It is also severe if it led, or could lead, to malicious code being introduced or executed in the product or a user’s systems.
Manufacturers report through ENISA’s Single Reporting Platform. The coordinating CSIRT and ENISA receive the notification simultaneously. The relevant EU establishment is normally where decisions on product cybersecurity are predominantly taken. If this cannot be determined, use the EU establishment with the most employees.
Without a main EU establishment, first identify the authorised representative acting for the largest number of the manufacturer’s products. Failing that, use the importer placing the largest number on the market, then the distributor making the largest number available, then the country with the most users. A Polish importer alone does not settle the question if the manufacturer also uses other importers. Inform affected users and, where appropriate, all users. Explain relevant measures they can take.
Record when the first report arrived, what it established and when further evidence became available. Early warnings and notifications are due without undue delay and within the outer limits below. Assess NIS2 and personal data breach notification duties separately.
| Stage | Actively exploited vulnerability | Severe incident |
|---|---|---|
| Early warning | Within 24 hours of becoming aware | Within 24 hours of becoming aware, stating whether unlawful or malicious acts are suspected |
| Notification | Within 72 hours of becoming aware | Within 72 hours of becoming aware |
| Final report | Within 14 days after a corrective or mitigating measure is available | Within one month after the 72-hour incident notification |
EU Cyber Resilience Act. What to check first
These facts let you answer the questions above for your own business.
| What to collect | Who has it | What it establishes |
|---|---|---|
| Device identifiers and records of first EU supply | Sales and logistics | Which units or batches cross the application date |
| App builds, release history and feature changes | Product team | Identical copies, variants and possible substantial modifications |
| Product labels, sales channels and EU volumes | Commercial team | Manufacturer and importer roles, and facts needed to select a reporting endpoint |
| Cloud architecture and development contracts | Engineering and legal | Whether the manufacturer is responsible for a necessary cloud function |
| Component end dates and maintenance rights | Procurement | Whether the planned support period is achievable |
| Report timestamps and escalation contacts | Product security | What was known, when, and who can submit the report |
The product and security teams own the technical work: architecture, component inventory, risk assessment and updates. Management decides the support period, the budget, which company markets the product and whether to appoint an authorised representative. Legal advice is worth seeking when a role is unclear and blocks a decision, a counterparty asks for guarantees or indemnities, or an authority makes a request.
When to seek legal advice on EU Cyber Resilience Act
If a customer asks for a seven-year patch commitment, send the proposed clause together with the component supplier’s support terms. CGO Legal can identify where the promises differ and draft wording covering access to fixes, notice of incidents and the cost of replacing an unsupported component. For a private-label launch, include a sample label and the distribution agreement so both parties’ statutory roles can be checked. Discuss your product or contract.
Frequently asked questions on EU Cyber Resilience Act
Do we need an EU company to sell a CRA-covered product?
Not under the CRA itself. A non-EU manufacturer can sell through an EU importer or distributor, and appointing an authorised representative is optional. Other product, tax or corporate rules may still require a local presence for other reasons.
Does every software update require a new conformity assessment?
A routine security fix will generally leave the original assessment in place. A change affecting conformity with the essential product security requirements or altering the intended purpose for which the product was assessed calls for a substantial-modification assessment. Record the reasons for the release decision.
Does the reporting duty apply to products we no longer sell?
Yes, if an in-scope product meets one of the two reporting triggers. Ending sales or reaching the end of support does not, by itself, end the manufacturer’s reporting duty.

