Short answer
The CRA is Regulation (EU) 2024/2847. It says that a product with digital elements may be placed on the EU market only if it is secure by design and the manufacturer takes care of its security throughout the support period: fixing vulnerabilities, releasing updates and reporting serious issues. Compliance is demonstrated as with other rules: technical documentation, an EU declaration of conformity and the CE marking.
Which products it covers
All products with digital elements, i.e. hardware and software that can be connected to another device or a network, whether by cable, radio or even USB. Typically:
- control units, industrial and embedded computers, terminals,
- smart devices, sensors and IoT gateways,
- routers, modems, switches,
- firmware and software sold separately.
It does not cover products with their own cybersecurity rules, such as medical devices, motor vehicles or aviation equipment, or products developed exclusively for defense and national security. Open source software not supplied in the course of a commercial activity is also out of scope.
What applies when
- 10 December 2024: the regulation entered into force.
- 11 June 2026: rules for the conformity assessment bodies that will assess products.
- 11 September 2026 (already applies): the obligation to report actively exploited vulnerabilities and severe security incidents. This also covers products already on the market.
- 11 December 2027: full application. New products that do not meet the CRA may no longer be placed on the market.
What manufacturers must do
During design and before placing on the market:
- Assess the product’s cybersecurity risks and design it accordingly.
- Not sell the product with known exploitable vulnerabilities.
- Ship with a secure default configuration, for example no shared default password, and allow a reset to factory state.
- Protect data and access: encryption, authentication, protection against unauthorized firmware modification.
- Minimize the attack surface, i.e. disable unnecessary interfaces and services.
- Compile a software bill of materials (SBOM) as part of the technical documentation.
Throughout the support period:
- Define the support period, usually at least 5 years (shorter only for products with a shorter expected lifetime). Customers must know it at the time of purchase.
- Fix vulnerabilities and release security updates, automatically and free of charge where possible.
- Provide a contact for reporting vulnerabilities and a procedure for handling them.
- Report an actively exploited vulnerability or a severe incident: early warning within 24 hours, notification within 72 hours and a final report (for a vulnerability within 14 days of the fix, for an incident within one month).
Breaching the essential requirements can result in a fine of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher. The market surveillance authority can also order the product to be withdrawn from the market.
Who assesses the product
- Default products (the majority): the manufacturer assesses conformity alone, just as for EMC.
- Important products, class I, such as routers, modems, switches or microcontrollers with security functions: self-assessment only when harmonized standards are applied, otherwise a notified body.
- Important products, class II, such as firewalls: always a third party.
- Critical products, such as smart cards or hardware security modules: a third party or European certification.
The exact classification is set out in Annexes III and IV of the regulation. If you are not sure, we are happy to go through it with you.
The CRA and radio equipment
For internet-connected devices with Wi-Fi, Bluetooth or LTE, the cybersecurity requirements of the RED have applied since 1 August 2025 (Regulation (EU) 2022/30, EN 18031 standards). From 11 December 2027 they will be replaced by the CRA. If you meet EN 18031 today, you are well on your way to the CRA, but the CRA asks for more, mainly vulnerability handling and updates throughout the support period.
How to get started
- Check whether the CRA applies to you. Does the product have firmware and some data interface? Then almost certainly yes.
- Do a risk assessment. What can be done to the product, what would it cause and how do you prevent it.
- Review the design: secure boot, signed updates, default passwords, unnecessary interfaces and debug ports.
- Set up a process: who monitors vulnerabilities in the libraries you use, how updates are released and who reports an incident within 24 hours.
- Plan the support period and factor it into the product price.
We have been designing embedded hardware and firmware for over 25 years, so we know how to build security into the design from the start. We also pre-test radio equipment to EN 18031. An overview of the other rules is in Directives made simple.
The complete CE guide as a PDF
All 11 guides in one document: CE, CRA, directives, EMC and safety testing, technical documentation, manual and rating label. For printing and for your team.
Does the CRA apply to your product?
Our EMC and CE calculator also asks about cybersecurity and shows which rules and tests your product faces. Or just write to us.