Making IoT devices quantum-safe: building post-quantum encryption into your own products
Devices stay in the field for 10 to 20 years. How manufacturers build in post-quantum encryption now and meet the Cyber Resilience Act.

- Devices shipped today will still be in use when powerful quantum computers could become available.
- The Cyber Resilience Act requires security over the whole life cycle, including updates.
- Crypto-agile building blocks let you switch algorithms by update instead of replacing devices.
A manufacturer of industrial robots is planning its next controller generation. It is meant to stay in the field for 15 years, allow remote maintenance and receive signed software updates. Engineering asks which encryption to build in today so the devices are still secure in ten years. Anyone who wants to make IoT devices quantum-safe has to decide today for a period they cannot know exactly.
Why device makers have to act earlier
Data intercepted today can be decrypted later once sufficiently powerful quantum computers are available. For devices there is more: whoever can forge an update signature can install malware. NIST's post-quantum standards have been published since 2024, and authorities such as the BSI recommend hybrid use, i.e. classical and post-quantum algorithms together (see NIST standards at a glance).
What the Cyber Resilience Act requires
The EU's Cyber Resilience Act sets cybersecurity requirements for products with digital elements across their whole life cycle, including security updates. Most obligations apply from December 2027; reporting obligations for actively exploited vulnerabilities already from September 2026. Cryptography that cannot be renewed in the field thus becomes a product risk.
Rule of thumb: A device is only as secure as the algorithms it can still switch by update.
Quantum-safe IoT devices: what manufacturers should watch
- Hybrid instead of either-or: classical and post-quantum algorithms together, as recommended by the BSI and other authorities.
- Signed updates: firmware and configuration are verified with post-quantum signatures.
- Crypto agility: algorithms are interchangeable without rebuilding protocols and processes.
- Keys in hardware: where available, device keys live in a secure element or TPM.
- Mind the resources: post-quantum signatures are larger; plan for memory and bandwidth.
Frequently asked questions
Do IoT devices need post-quantum cryptography today?
For devices with a long lifetime and confidential data or remote access, yes — at least for signed updates and the ability to switch algorithms later.
What does hybrid mean?
A classical and a post-quantum algorithm are used together. The connection stays secure as long as one of the two is secure.
Does post-quantum cryptography fit on small devices?
Often yes, but signatures and keys are larger. Memory, bandwidth and computing time should be planned early.
What does the Cyber Resilience Act have to do with it?
It requires security across the life cycle, including updates. Cryptography that cannot be renewed therefore becomes a compliance risk.
What you can do now
- Create an inventory of the cryptography used in your products.
- Check whether your update chain can already switch algorithms today.
- Plan post-quantum signatures for updates in the next device generation.
- Add the requirements of the Cyber Resilience Act to your specification.
With the PQVault SDK
The PQVault SDK brings post-quantum encryption and signatures into your own applications and devices, hybrid and crypto-agile, with keys in the TPM and a release service. For exchanging firmware and documentation with partners, use data rooms in Spaces. More under Robotics & automation and in the article on crypto agility.
PQVault is a product of QuantiCor Security GmbH, Darmstadt — specialists in post-quantum cryptography. More about QuantiCor Security


