Which products are in scope
The Regulation refers to "products with digital elements": any software or hardware product whose intended use includes a direct or indirect data connection to a device or to a network. This covers connected objects, communicating industrial equipment, routers, software and applications, but also components sold separately, such as a microcontroller or a software library.
Products already covered by equivalent sector-specific legislation are excluded:
- medical devices;
- motor vehicles;
- civil aviation equipment;
- marine equipment;
- products designed exclusively for defence or national security;
- free and open-source software developed outside a commercial activity.
An online service is not, in itself, a product within the meaning of the Regulation. It becomes one if it provides remote data processing without which the product cannot perform one of its functions: the mobile application and the remote service of a smart lock are part of the product.
Manufacturer, importer, distributor
The manufacturer bears most of the obligations: design, documentation, vulnerability handling, reporting. The importer must ensure, before placing the product on the market, that the manufacturer has done what is required. The distributor verifies that the CE marking and the documents are present.
Anyone who sells a product under their own brand, or who modifies it substantially, becomes a manufacturer within the meaning of the Regulation, with all the obligations that this entails.
- Manufacturer Designs, documents, fixes, reports
- Importer Verifies before placing on the market
- Distributor Verifies the CE marking
- User Receives updates and information
The timeline
- 10 December 2024 Entry into force (past step)
- 11 June 2026 Conformity assessment bodies (past step)
- 11 September 2026 Mandatory reporting (past step)
- 11 December 2027 Full application (next step)
| Date | What applies |
|---|---|
| 10 December 2024 | Entry into force of the Regulation |
| 11 June 2026 | Rules on conformity assessment bodies |
| 11 September 2026 | Mandatory reporting of actively exploited vulnerabilities and severe incidents |
| 11 December 2027 | Full application: security requirements, documentation, CE marking |
A unit placed on the market before 11 December 2027 is not subject to the design requirements, unless it subsequently undergoes a substantial modification. The reporting obligation, however, already applies to it.
Note: it is each individual unit that is placed on the market, not the model. A model designed in 2024 and still sold in 2028 will have to be compliant for the units delivered after the deadline.
The security requirements
Everything starts from a cybersecurity risk assessment, which the manufacturer must carry out, document and keep up to date. It is what justifies which requirements apply to the product, and how. On that basis, Annex I requires in particular that the product:
- is placed on the market without any known exploitable vulnerability;
- is delivered with a secure-by-default configuration;
- can receive security updates, automatic by default where applicable;
- is protected against unauthorised access, through appropriate authentication and access management;
- protects the confidentiality and integrity of the data it stores, processes or transmits;
- limits its attack surface, including its external interfaces;
- records the relevant security events;
- allows the user to erase their data and settings.
Vulnerability handling and the support period
The second part of Annex I deals with the life of the product after it is sold. The manufacturer must:
- identify and document the product’s components, in a machine-readable software bill of materials (SBOM) covering at least the top-level dependencies;
- remediate vulnerabilities without delay, through security updates;
- regularly test and review the security of the product;
- publish a coordinated vulnerability disclosure policy and a contact point for reporting a vulnerability;
- distribute security updates free of charge, and without delay.
These obligations last throughout the support period. The manufacturer sets it according to the length of time the product is expected to be in use; it is at least five years, unless the product is made to be used for a shorter time. Its end date must be indicated to the purchaser.
Reporting, in force since 11 September 2026
An actively exploited vulnerability, or a severe incident affecting the security of the product, is reported in three stages:
- 24 hours Early warning
- 72 hours Notification
- 14 days or 1 month Final report
- within 24 hours: an early warning;
- within 72 hours: a notification, with the information available and the measures taken;
- a final report: no later than 14 days after a fix becomes available for a vulnerability, and within one month for a severe incident.
Reports are made on the single reporting platform operated by ENISA, addressed to the national computer security incident response team (CSIRT) designated as coordinator and to ENISA. The users affected must also be informed.
This obligation applies to all products in scope, including those sold before that date. If you are a manufacturer and have no contact point, no procedure and no bill of materials, this is the first job to tackle.
Conformity assessment and CE marking
By default, the manufacturer assesses the conformity of its product itself. The Regulation identifies two categories for which the process is more demanding:
- "important" products (Annex III) — password managers, virtual private networks, routers, operating systems, firewalls and microcontrollers with security-related functionalities, among others: application of harmonised standards or use of a third-party body, depending on the class;
- "critical" products (Annex IV) — smart cards and smart meter gateways, for example: reinforced requirements, which may go as far as European certification.
In all cases, the manufacturer compiles the technical documentation (risk assessment, software bill of materials, test reports), draws up an EU declaration of conformity, provides the user with the required information and instructions, and then affixes the CE marking. The documentation is kept for ten years, or for the support period if that is longer.
Penalties
The Regulation provides for fines of up to €15 million or 2.5% of worldwide annual turnover for non-compliance with the essential requirements or with the manufacturer’s obligations, including reporting. Other obligations carry fines of up to €10 million or 2%, and the supply of incorrect information up to €5 million or 1%.
Market surveillance authorities may also require a product to be brought into conformity, withdrawn or recalled. For a manufacturer, that is often the heaviest penalty.
Where to start
- Determine, product by product, whether it is in scope and in which category.
- Set up reporting: contact point, procedure, designated people. It is already due.
- Draw up the software bill of materials for each product.
- Carry out the risk assessment for each product.
- Measure the gaps against Annex I, starting with updates and the default configuration.
- Set the support period and what it commits you to.
- Build the technical documentation as the work progresses, not at the end.
Frequently asked questions
My product is already on the market: am I affected?
By reporting, yes, since 11 September 2026. Units already placed on the market before 11 December 2027 are not subject to the design requirements, unless they are substantially modified. But every unit placed on the market after that date will have to be compliant, even if the model existed before.
Does the Regulation apply to standalone software?
Yes. Software sold or supplied in the course of a commercial activity is a product with digital elements, even without associated hardware.
Is a third-party body required?
Not in the general case: the manufacturer assesses conformity itself. A third party is involved for certain products in the "important" and "critical" categories, depending on their class and on whether harmonised standards have been applied.
What is the difference between the Cyber Resilience Act and NIS2?
NIS2 covers organisations, for the security of their own systems. The Cyber Resilience Act covers products, for the security of what is placed on the market. An industrial company may fall under both.
Sources
This guide provides general information, up to date on the date shown at the top of the page. It replaces neither the official texts nor advice tailored to your situation.

