The EU Cyber Resilience Act (CRA) is the first horizontal cyber-security law for products in the EU. It covers hardware and software “products with digital elements” — and it applies to UK companies too, if they place those products on the EU market. Brexit doesn’t change that.
The timeline
| Date | What happens |
|---|---|
| 10 Dec 2024 | The CRA (Regulation (EU) 2024/2847) entered into force. |
| 11 Sep 2026 | Reporting obligations apply: actively exploited vulnerabilities and severe incidents must be reported — including for products already on the market. |
| 11 Dec 2027 | The main obligations apply: essential security requirements, conformity assessment, CE marking and documentation. |
Reporting: already in force
Since 11 September 2026, manufacturers must notify actively exploited vulnerabilities and severe incidents affecting their products through the single reporting platform operated by ENISA. The structure is staged:
- Early warning within 24 hours of becoming aware.
- Notification with more detail within 72 hours.
- Final report within 14 days of a corrective measure being available for a vulnerability, or within one month for an incident.
If you don’t yet have a way to receive vulnerability reports, triage them quickly and know who makes the call to notify, that is the first gap to close.
What December 2027 brings
- Security by design and by default — products must meet essential requirements, ship without known exploitable vulnerabilities and with secure default configurations.
- Vulnerability handling for the support period, including security updates and a coordinated disclosure policy.
- A software bill of materials (SBOM) in a machine-readable format, covering at least top-level dependencies.
- Technical documentation and conformity assessment — self-assessment for most products, stricter routes for “important” and “critical” categories.
- CE marking for compliant products.
Penalties for breaching the essential requirements can reach €15 million or 2.5% of worldwide annual turnover, whichever is higher.
Is my product in scope?
Broadly: if you sell software or connected hardware to EU customers commercially, assume yes until you have checked. Some sectors with their own regimes (such as medical devices and vehicles) are excluded. Pure software-as-a-service is generally covered by other EU rules rather than the CRA, but remote data processing that a product needs in order to function can bring backend services into scope. Non-commercial open source is outside the regime, with a lighter set of duties for open-source stewards.
And in the UK?
UK firms face parallel developments: the Product Security and Telecommunications Infrastructure (PSTI) regime already applies to consumer connectable products, and the Cyber Security and Resilience Bill is extending incident-reporting duties for operators and key suppliers. If you sell into both markets, design one secure-development and vulnerability-handling process that satisfies both.
A practical checklist
- List every product and version you place on the EU market.
- Stand up a vulnerability intake (a
security.txtfile and a monitored mailbox are a good start) and a 24-hour triage path. - Generate SBOMs in your build pipeline.
- Threat-model your main products and record the decisions.
- Define a support period and an update process for each product.
- Run a gap analysis against the essential requirements and plan the work to December 2027.
This article is general guidance, not legal advice. Check the regulation and take legal advice for your specific products.