Requirements
What the regulation expects

Secure by design, for every product
The CRA applies to hardware and software products with digital elements placed on the EU market, with CE marking tied to cybersecurity.
Authenticated devices and updates
Integrity and authenticity of firmware and updates need signing keys that cannot be copied off a build server.
Long support periods
Devices sold in 2027 may still need patches, renewed certificates and new algorithms in the 2030s.
Solutions
How DuoKey supports the framework
Factory device certificate provisioning
A unique X.509 certificate per device over EST or CMP on the production line, with OCSP and CRL revocation.
Learn moreCode signing with non-exportable keys
Firmware, software and container signatures made in a vault or HSM, under approval and with a complete journal.
Learn moreCryptographic inventory
Discovery and a cryptographic bill of materials (CBOM) next to the SBOM the CRA asks for.
Learn moreKey themes
Where independent key control fits
DuoKey supports manufacturers with building blocks for Annex I. The CRA does not certify key managers or PKIs: conformity is assessed on your product, and the mapping below shows where DuoKey contributes evidence.
Protection from unauthorised access (Annex I, Part I)
Unique device identities and mutual authentication instead of shared credentials, with per-device revocation through OCSP and CRL.
Confidentiality of stored and transmitted data (Annex I, Part I)
State-of-the-art encryption with keys held in an HSM, a cloud KMS or an MPC vault, outside the systems that store the data.
Integrity of data, commands and software (Annex I, Part I)
Signed firmware, software and container images, with signing keys that never leave the vault and an approval policy on each signature.
Security updates over the support period (Annex I, Part II)
Authenticated over-the-air updates and renewable device certificates, so devices can still be patched and re-keyed years after shipment.
Vulnerability handling and SBOM (Annex I, Part II)
A cryptographic inventory of algorithms, keys and certificates per product, to find what a new cryptographic weakness affects.
Discuss the decisions that matter most to your security programme.
Tell us where control is difficult today. We will help you identify a practical next step.
