Is your product in scope?
The CRA covers products with digital elements: hardware and software that connect, directly or indirectly, to a device or a network, placed on the EU market. That includes connected devices, their firmware, the companion apps and the remote data processing the product needs to work. A few groups are covered by their own rules instead: medical devices, vehicles and their components, aviation and marine equipment, and products built only for national security or defence. Open-source software made without a commercial activity is outside; companies that steward open source for commercial use have lighter duties.
Which class is your product in?
| Class | Examples | Conformity assessment |
|---|---|---|
| Default | Sensors, appliances, machine controllers, most fitness devices and other connected products not listed in the higher classes | Self-assessment by the manufacturer |
| Important, class I | Smart home products with a security function (door locks, cameras, alarms, baby monitors), routers, modems, network interfaces, microcontrollers with security functions, smart home virtual assistants, internet-connected toys with location tracking or social features, wearables for health monitoring or for children, password managers, operating systems | Self-assessment only with harmonised standards applied in full; otherwise a notified body |
| Important, class II | Firewalls, intrusion detection and prevention, hypervisors, tamper-resistant microprocessors and microcontrollers | A notified body |
| Critical | Hardware devices with security boxes, smart meter gateways, smartcards and secure elements | A notified body, and a European cybersecurity certificate where the Commission requires one |
Our free device CRA check places your product in a class in about three minutes and lists what is still missing.
The firmware checklist
These are the product requirements most connected devices fall short on. Each maps to the CRA's essential requirements in Annex I:
- Secure by default. No default passwords shared between units; unique credentials per device; unused interfaces and debug ports closed in production.
- Secure boot. A chain of trust from ROM or a hardware root of trust that checks the signature of the bootloader and the firmware before they run.
- Signed updates with rollback protection. Updates signed by keys kept off the build server, verified on the device, with anti-rollback counters and a safe recovery if an update fails.
- Automatic security updates. On by default where the product allows it, with a way for the user to turn them off, and notification of available updates.
- Protected keys and data. Device keys in a secure element, TPM or TrustZone where the hardware has one; data encrypted at rest and in transit with current algorithms.
- Minimal attack surface. Only the services the product needs; least privilege between components; memory-safe code where you can. Rust removes whole classes of memory bugs from new firmware.
- Resilience and logging. The device keeps its essential functions under attack or loss of network, and records security events the user or you can read.
- Data minimisation and deletion. Collect only what the function needs; let the user delete their data and settings securely.
The process checklist
Annex I also sets vulnerability handling duties. These are about your company, not the device, and they usually take longer than the firmware work:
- SBOM. A software bill of materials covering at least the top-level dependencies, generated for every release in a standard format such as SPDX or CycloneDX, and kept in the technical documentation.
- Vulnerability handling. A process to find, track and fix vulnerabilities in your code and dependencies, with regular testing and security updates shipped free of charge, separately from feature updates where that is possible.
- Coordinated disclosure. A published policy and a security contact where anyone can report a vulnerability, and a commitment to tell users once a fix ships.
- Reporting. Someone who can file an early warning through the EU single reporting platform within 24 hours of learning of an actively exploited vulnerability or a severe incident, a notification within 72 hours, and a final report later. Rehearse it.
- Support period. A declared end date for security support, shown at the point of sale, of at least five years unless the product's expected use is shorter.
- Risk assessment and documentation. A written cybersecurity risk assessment, the technical documentation and the EU declaration of conformity, kept for ten years after the product is placed on the market or for the support period, whichever is longer.
How does it relate to EN 18031?
Wireless devices sold in the EU have had to meet the Radio Equipment Directive's cybersecurity requirements since 1 August 2025, usually by applying the EN 18031 standards. That work carries over: secure updates, authentication, secure storage and communication are all CRA requirements too. What EN 18031 does not cover is the process side: SBOM, vulnerability handling, reporting and the support period. Our EN 18031 guide explains the standard and its restrictions.
A 12-month plan to December 2027
| Quarter | Firmware | Process |
|---|---|---|
| Q4 2026 | Gap assessment against Annex I; threat model per product | Name the owner of reporting; publish a disclosure policy; rehearse a 24-hour early warning |
| Q1 2027 | Secure boot and signed update path; remove shared credentials | SBOM generated in CI for every release; dependency monitoring |
| Q2 2027 | Key storage, encryption, interface hardening; fix the findings from testing | Risk assessment written; support period decided and priced |
| Q3 2027 | Penetration test and fixes; update rollout tested in the field | Technical documentation complete; notified body booked if your class needs one |
| Q4 2027 | Release candidate frozen against the requirements | Declaration of conformity; CE marking from 11 December 2027 |
If your product needs a notified body, book one early: capacity is expected to be tight through 2027.
What usually slips?
- Signing keys for firmware kept on a build server or a developer laptop.
- Legacy product lines with no update path, still on sale after December 2027.
- Third-party modules and SDKs with no SBOM and no security support from the supplier.
- A support period promised by sales that engineering cannot staff.
- Reporting owned by nobody until the first exploited vulnerability arrives.
How we work with this
We are firmware and systems engineers. We do gap assessments against Annex I, implement secure boot, signed over-the-air updates, key storage and SBOM generation, and write the Rust firmware that removes memory bugs from new code. Our engineers can also join your team to carry the work through to December 2027: see engineers in your team and our delivered device work.
FAQ
Q01Does the CRA apply to products we already sell?
The product requirements apply to products placed on the EU market from 11 December 2027; each unit you sell after that date must comply, even if the model launched earlier. The reporting duty for actively exploited vulnerabilities and severe incidents has applied since 11 September 2026 to products already on the market.
Q02How long must we provide security updates?
For the support period you declare, which must reflect how long the product is expected to be used and is at least five years unless the product's expected use is shorter. Each security update must stay available for at least ten years after release, or for the rest of the support period if that is longer.
Q03Do we need a notified body?
Default-class products can be self-assessed. Important class I products can be self-assessed only if you apply harmonised standards in full; otherwise, and for class II, a notified body takes part. Critical products may need a European cybersecurity certificate.
Q04What are the penalties?
For breaching the essential requirements or the reporting duties, fines up to 15 million euros or 2.5% of worldwide annual turnover, whichever is higher. Market surveillance authorities can also order a product off the market.
Q05We already meet EN 18031 for the Radio Equipment Directive. Are we done?
No, but you are ahead. EN 18031 covers part of the CRA's product requirements for wireless devices. The CRA adds the vulnerability handling process, the SBOM, the support period, reporting and the technical documentation.
Sources
This guide is a summary for engineering teams, not legal advice. Check your product's class and conformity route with your compliance team or a notified body.
