EU Regulation · CRA
Cyber Resilience Act
Regulation (EU) 2024/2847
The EU Cyber Resilience Act sets mandatory cybersecurity requirements for products with digital elements across their whole lifecycle — from secure design and a Software Bill of Materials to vulnerability handling and incident reporting.
What it covers
Products with digital elements whose intended or foreseeable use includes direct/indirect data connections, subject to statutory exclusions including MDR/IVDR.
How it applies to your product
In practice the CRA means a connected product needs secure-by-default configuration, a documented vulnerability-handling process, and a Software Bill of Materials — and the manufacturer must report actively exploited vulnerabilities and severe incidents through the EU single reporting platform to the relevant national CSIRT (with ENISA notified in parallel) within tight deadlines. It applies on top of a product’s other CE-marking obligations, not instead of them.
Key dates
Applies in full from 11 December 2027; the vulnerability and incident reporting obligations apply earlier, from 11 September 2026.
Authoritative source
Always confirm against the primary text on EUR-Lex — the official EU legal database.
Read Regulation (EU) 2024/2847 on EUR-Lex ↗See also the CRA entry in the glossary.
Guides on CRA
From the Library
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
guide
CRA Scope for Connected Devices and Their Cloud Backends
Apply the CRA remote data processing tests to connected device architectures and record external cloud dependencies separately.
guide
When a Firmware Update Needs New CE Evidence or Retesting
Assess firmware changes against existing CE evidence, notified body notification duties and the CRA substantial modification rules with a change impact record.
tutorial
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example
Write a scoped CycloneDX VEX decision for embedded firmware: an unresolved in_triage record, a synthetic not_affected record with justification, and reassessment triggers.
tutorial
CRA Cybersecurity Risk Assessment for an IoT Gateway
Create an IoT gateway risk register that connects product boundaries, abuse cases, security controls and verifiable release evidence.
tutorial
Generate and Check an SPDX SBOM with Yocto
Prepare a pinned Yocto 5.0.13 workflow that emits SPDX 2.2, capture build provenance and review package coverage before using the SBOM as evidence.
Check your product