Why it exists
Vehicle security must outlast the algorithms selected at production. For a platform planned around a 15–20 year vehicle lifetime, consider both the information that must remain confidential and the software signatures that must remain trustworthy. This is a planning horizon, not a prediction of when quantum attacks will become practical.
A sufficiently capable quantum computer could break today’s widely used public-key cryptography. An attacker could then recover secrets from recorded communications or forge signatures accepted by a vehicle.
The confidentiality problem starts before such a computer exists. An attacker can collect encrypted traffic now and attempt to decrypt it later: harvest-now-decrypt-later. This matters when captured engineering data, credentials or personal information must remain secret for a long time. It particularly affects sessions whose recorded key exchange can later be broken.
Firmware has a different exposure. An attacker does not need to decrypt an old image. They need to forge a signature that a future bootloader or update client will accept. Preparing the verification path early is therefore part of keeping vehicles updateable.
These alternative sessions assume sound authentication, key derivation and symmetric encryption; post-quantum key establishment is designed to prevent later recovery of session secrets from recordings.
What it is
Post-quantum cryptography uses algorithms designed to resist attacks from both classical and quantum computers. It runs on conventional processors; the vehicle does not need quantum hardware.
Crypto agility is the ability to replace algorithms, parameter sets, keys and implementations without redesigning the whole system. It includes formats, memory budgets, security policy and update procedures.
The National Institute of Standards and Technology (NIST) published its first three post-quantum Federal Information Processing Standards (FIPS) in August 2024: FIPS 203, FIPS 204 and FIPS 205. Their roles differ:
| Algorithm | Purpose | Vehicle relevance |
|---|---|---|
| ML-KEM: Module-Lattice-Based Key-Encapsulation Mechanism | Establish a shared secret | Vehicle-to-backend session establishment |
| ML-DSA: Module-Lattice-Based Digital Signature Algorithm | Sign and verify data | Update metadata, software and certificates |
| SLH-DSA: Stateless Hash-Based Digital Signature Algorithm | Sign and verify using hash-based constructions | An alternative signature family with different implementation and size tradeoffs |
| LMS: Leighton-Micali Signature; XMSS: eXtended Merkle Signature Scheme | Stateful hash-based signatures, profiled in NIST SP 800-208 | Firmware signing with tightly controlled backend signing state |
A key-encapsulation mechanism establishes a secret for symmetric encryption. It does not itself encrypt a firmware image or authenticate the communicating parties.
How it works
Quantum attacks affect algorithm families differently
Shor’s algorithm solves the factoring and discrete-logarithm problems underlying RSA, named after Rivest, Shamir and Adleman, and elliptic-curve cryptography (ECC). On a sufficiently capable quantum computer, this defeats their security assumptions. Increasing their key sizes is not a durable migration strategy.
Grover’s algorithm gives a generic speedup for exhaustive search. Symmetric encryption and hashes therefore lose security margin rather than suffering the same structural break. Hash collision resistance is a separate property; do not apply a blanket “halve every hash strength” rule.
For long-lived assets, prefer Advanced Encryption Standard with 256-bit keys (AES-256) and Secure Hash Algorithm with a 384-bit output (SHA-384) where the protocol permits. NIST’s Post-Quantum Cryptography Standardization — Security Evaluation Criteria discusses these security benchmarks and quantum attack costs. Larger symmetric keys do not repair a vulnerable public-key exchange that exposes those keys.
Signing and key establishment need separate migrations
For a backend connection, a protocol can incorporate ML-KEM to establish session secrets. It still needs authentication, a key-derivation procedure and symmetric authenticated encryption.
For secure boot, the device needs a trusted public key and a verifier for the selected signature scheme. The backend signs the image or its authenticated manifest; the device verifies it before execution.
LMS and XMSS are attractive for firmware signing because signing can be centralized while many vehicles perform verification. Their critical constraint is persistent signing state: a one-time signing key must never be reused. Backups, failover and restored snapshots must preserve that rule. Vehicles verifying signatures do not maintain this signing state.
Agility must reach the root of trust
Algorithm identifiers and parameter identifiers let a verifier interpret a package unambiguously. They must be authenticated and checked against an allowed policy.
A hybrid scheme combines classical and post-quantum protection during migration. For key establishment, use a reviewed protocol and combiner. For signatures, specify whether both signatures must verify. Accepting either signature leaves an attacker free to target the weaker permitted option.
When to use it — and when not
Prioritize long-lived confidential communications, firmware-signing infrastructure and trust anchors that are difficult to replace. Evaluate backend services, central computers and constrained electronic control units (ECUs) separately.
Begin with inventory and migration capability even when immediate algorithm replacement is impractical. A brake ECU may need more preparation in its bootloader than in its real-time control messages.
Do not replace every symmetric message authenticator with a post-quantum signature. These mechanisms serve different purposes and have different resource costs. Do not deploy an improvised hybrid format simply because its component algorithms are standardized.
Best practices
- Inventory dependencies. Record algorithm, parameter set, key location, library, hardware dependency and replacement path for each security function.
- Budget for larger objects. Check public keys, signatures, certificate chains, update manifests, flash slots and communication buffers. Measure verification time and working memory on the target.
- Prepare bootloaders early. An immutable verifier that understands only a vulnerable signature scheme can block migration. Design a trusted transition path before production.
- Make libraries updateable. Keep clear interfaces between applications, crypto implementations and hardware services. Authenticate library updates and prevent rollback.
- Stage transitions. Install new verification support before sending packages that require it. Test recovery images and interrupted updates throughout the transition.
- Protect signing operations. For LMS or XMSS, enforce state advancement across failures and backend replicas; use implementations and operational controls consistent with SP 800-208.
Common pitfalls
- Treating an algorithm identifier as permission to accept any algorithm, enabling downgrade attacks.
- Reserving room for a larger signature while forgetting certificate chains, temporary buffers or recovery partitions.
- Assuming a library update can change algorithms locked into immutable boot code or fixed-function security hardware.
- Restoring an LMS or XMSS signing backup and accidentally reusing signing state.
- Calling a connection quantum-resistant while its authentication still accepts forgeable classical signatures.
- Confusing signature validity with freshness: post-quantum signatures still need version checks and rollback protection.