top of page

What the Cyber Resilience Act expects of your device

Secure by design is now a condition for CE marking​

​

Three engineering practices carry most of the technical weight of the CRA: secure boot, signed updates and device identity. All three rest on keys that are generated, used and governed properly for the whole life of the product.

Three dates have passed. One is left.

10 Dec 2024 · In force

The Cyber Resilience Act (EU 2024/2847) enters into force. Manufacturers have three years to bring products with digital elements into line.

2026 · Applies now

Since 11 June 2026, the rules for notified bodies and conformity assessment apply. Since 11 September 2026, Article 14 reporting obligations apply, including for products already on the EU market.

11 Dec 2027 · Next

Full application: the Annex I essential requirements, CE marking and market surveillance. Devices you design now will ship into this date.

Where Annex I meets your firmware

Secure boot

Annex I asks that integrity is protected against unauthorised modification. On a device, only authentic firmware runs, from the first boot stage on. LAAVAT signs for NXP, AMD/Xilinx and TI targets and MCUboot-based MCUs.

Secure firmware updates

Annex I asks that vulnerabilities can be fixed through secure updates. The device needs an update path it can trust. LAAVAT signs, and can encrypt, RAUC, Mender and SWUpdate bundles with keys held in an HSM.

Strong device identity

Annex I asks that the product is protected from unauthorised access. Devices and services authenticate each other without shared secrets. LAAVAT issues IDevID and LDevID certificates for each device over REST or EST.

What LAAVAT covers, and what it does not

Evidence for your technical file​

Every signing action is approved, logged and exportable, so you can show who signed what, when, and who approved it.

What LAAVAT does not do​

Using LAAVAT does not make a product CRA compliant by itself. Product design, vulnerability handling and Article 14 reporting stay with you.

Confidentiality of firmware and keys​

AES-GCM-256 image encryption with a product key or a key per device. Keys are generated in the HSM and never leave it in the clear.

What non-compliance can cost​

Up to €15 million or 2.5% of worldwide annual turnover, whichever is higher, for breaching the essential requirements.

The CRA guide in our docs

01

Overview

The regulation in brief, and the dates that matter.

04

Article 14 reporting

What has to be reported, to whom, and how fast.

02

Scope, classification and penalties

Which products are in scope, the risk classes, and the penalties.

05

Secure boot and the CRA

Why secure boot is what makes updatability meaningful.

03

Annex I mapping

The essential requirements, mapped to platform capabilities.

06

Boot manager standard (ETSI EN 304 623)

The draft harmonised standard for boot managers.

See how Vaisala, a global leader in weather, environmental and industrial measurement, uses LAAVAT to secure its connected products.

See it in practice

​

Pick your hardware or update tool and watch a team go from first login to a signed release, in about 90 seconds.

Devices designed now ship into 2027

bottom of page