Get your product ready for the CRA
Key dates
The first obligations already apply. The rest follow in December 2027.
10 December 2024
Regulation (EU) 2024/2847, the Cyber Resilience Act, entered into force.
11 September 2026
Reporting obligations apply: manufacturers must report actively exploited vulnerabilities and severe incidents, with an early warning within 24 hours.
11 December 2027
All requirements apply. Products placed on the EU market must meet the essential cybersecurity requirements and carry the CE marking under the CRA.
What the CRA requires
For a typical embedded device, the CRA’s essential requirements come down to a few concrete obligations:
- Secure by design and by default, without known exploitable vulnerabilities when the product is placed on the market.
- Security updates for the whole support period, normally at least five years, distributed securely.
- A software bill of materials (SBOM) and a documented process for handling vulnerabilities.
- Reporting of actively exploited vulnerabilities and severe incidents to the authorities, starting within 24 hours.
- Technical documentation and a conformity assessment for the CE marking.
Non-compliance can be fined with up to €15 million or 2.5% of the worldwide annual turnover.
How we help
Most CRA requirements are engineering tasks. They are what we do every day.
Gap analysis
We review your product, from bootloader and kernel to root file system, update path and development process, and show where it falls short of the CRA’s essential requirements.
Secure Boot and hardening
Only authenticated software runs on your device. We implement Secure Boot for your SoC, reduce the attack surface and verify the result with penetration tests.
Secure updates with SWUpdate
Signed update packages, A/B updates with fallback and fleet rollouts with hawkBit, from the team that created SWUpdate. Five years of security updates become manageable.
SBOM and CVE monitoring
We set up your Yocto Project build to generate SBOMs for every release and monitor CVEs against them, so you know which vulnerabilities affect which product.
Maintained BSP
Staying close to maintained upstream versions is the basis for fixing vulnerabilities quickly. Upstream first means fewer private patches to carry for years.
Vulnerability handling
We help you set up the process behind the 24-hour reporting obligation: from triage of a new vulnerability to the fixed update installed in the field.
Engineering, together with your advisers
We are engineers, not lawyers. For the legal side, such as the classification of your product or the conformity assessment procedure, we work together with your legal and compliance advisers, and deliver the technical measures and documentation they need.