Quantum Safe Cryptography for Connected Cars: UN R155, ISO/SAE 21434, and V2X

Your Car Is a Long-Lived Computer

A vehicle sold in 2026 will still be on the road in 2040 or later. Over those fifteen years it will receive software updates, talk to roadside units, share data with insurance partners, and connect to infotainment clouds. Every one of those channels rests on cryptography that Shor's algorithm would dismantle once a large quantum computer exists. Connected vehicles are a textbook harvest-now-decrypt-later target: long service life, high-value authentication, and packets that leak identity and location whether the engineer intended it or not.

This guide explains what automotive engineers, OEM security leads, and Tier 1 suppliers need to know about Quantum Safe Cryptography in the context of UN Regulation 155, ISO/SAE 21434, and V2X standards. It does not pretend the automotive industry has solved post-quantum. It maps where the gaps sit and what to do about them.

UN R155 and R156: The Regulatory Baseline

The United Nations Economic Commission for Europe adopted UN R155 (Cybersecurity Management System) and UN R156 (Software Update Management System) in June 2020. They entered into force in January 2021 and became mandatory for all new vehicle type approvals in contracting states from July 2024. R155 requires manufacturers to operate a CSMS across the entire vehicle lifecycle, including cryptographic key management and software update integrity.

R155 is not a Post Quantum Cryptography mandate. It is a process regulation. That matters because regulators will hold OEMs accountable for failing to manage known cryptographic risk, and quantum risk is now a documented, standards-body-acknowledged concern. An OEM CSMS that ignores PQC migration planning will face questions at the next homologation cycle.

ISO/SAE 21434 and the Security Lifecycle

ISO/SAE 21434 Road vehicles Cybersecurity engineering was published on August 31, 2021, superseding SAE J3061. It defines the cybersecurity engineering process for automotive electrical and electronic systems from concept through decommissioning. Post Quantum Cryptography is not called out by name, but the standard's requirements for threat analysis and risk assessment (TARA), cryptographic agility, and lifecycle management all apply directly to quantum risk.

For OEM security teams, the path is clear: the TARA has to include a harvest-now-decrypt-later threat scenario for any long-lived secret in the vehicle or backend, and the cybersecurity concept has to describe how PQC migration will occur within the 15-year operational window.

V2X and the IEEE 1609.2 Problem

Vehicle-to-Everything (V2X) communications under IEEE 1609.2 use a public key infrastructure based on ECDSA P-256 or P-384 for signing Basic Safety Messages and other payloads. Certificates are short-lived by design (often hours or days for pseudonym certificates) to protect privacy, but the root and intermediate CAs live for many years. Shor's algorithm breaks every curve used in that hierarchy.

The IEEE 1609 working group is aware and has been studying post-quantum alternatives, but no normative profile has been issued as of April 2026. Constraints are real: signature size matters because V2X messages go into tight radio frames at 10 Hz, and ML-DSA signatures are larger than ECDSA signatures. Hash-based schemes like SLH-DSA produce even larger signatures. Hybrid approaches and stateful hash-based trees (LMS/XMSS, NIST SP 800-208) for roots are being discussed.

The CAN Bus and Internal Networks

The Controller Area Network (CAN) bus inside a vehicle is not cryptographically authenticated by default. AUTOSAR Secure Onboard Communication (SecOC) adds message authentication using AES-128-CMAC or similar symmetric primitives. Symmetric cryptography is relatively resistant to quantum attacks (Grover's algorithm halves effective key bits), so AES-256 variants remain safe. The quantum vulnerability inside the vehicle is concentrated in asymmetric operations: HSM-backed key provisioning, diagnostic authentication (ISO 14229 UDS $29), secure boot signatures, and OTA update verification.

OTA Updates and R156

R156 makes software update integrity a homologation requirement. OEMs today sign update packages with RSA-2048, RSA-3072, or ECDSA. An adversary with a cryptographically relevant quantum computer could forge updates for vehicles built with those signatures. The near-term fix is a hybrid signature: attach both an ECDSA signature and a PQC signature (ML-DSA or SLH-DSA) so that verification fails only if both are broken. NIST SP 800-208 stateful hash-based signatures (LMS/HSS) are also appropriate for firmware signing because update events are bounded and state management is tractable in the backend.

What OEMs Should Do Now

Automotive PQC migration is a multi-year program. Any OEM planning model year 2028 and later should already be doing:

1. A full cryptographic inventory across ECUs, HSMs, backend, telematics clouds, V2X stack, and OTA pipeline.
2. A harvest-now-decrypt-later threat scenario inside the ISO/SAE 21434 TARA for every long-lived secret.
3. HSM roadmap alignment: confirm HSM vendors can add ML-KEM, ML-DSA, and LMS primitives via firmware update.
4. Hybrid signature planning for OTA, V2X, and secure boot.
5. Telematics backend migration to TLS 1.3 with ML-KEM hybrid key exchange.
6. Supplier contract updates requiring crypto agility and PQC roadmaps from Tier 1s.

Satellite, 5G, and the Car as a Node

Connected vehicles increasingly use cellular and satellite links. 5G networks are moving toward 3GPP SA3 quantum-safe profiles (see our 5G and 6G post), and satellite V2X over constellations like Starlink will ride whatever the operator offers. Vehicles talking to multiple radio layers need a vehicle-side crypto-agility design, not a hard-coded per-radio choice.

QNSQY and Automotive Data

QNSQY provides a Post Quantum Cryptography data encryption platform used in engineering contexts where long-lived data has to survive the quantum transition. Automotive use cases include protecting engineering datasets (CAN logs, HIL recordings, chassis measurements, proprietary maps), protecting supplier IP during collaboration, and encrypting vehicle-to-backend data dumps that might sit on adversary storage for years.

Frequently Asked Questions

Does UN R155 require Post Quantum Cryptography?

No. UN R155 is a process regulation for the Cybersecurity Management System, not a cryptographic primitive mandate. But regulators expect the CSMS to address known cryptographic risk, which now includes quantum.

When was ISO/SAE 21434 published?

ISO/SAE 21434 Road Vehicles Cybersecurity Engineering was published on August 31, 2021, superseding SAE J3061.

Is V2X quantum-safe?

No. IEEE 1609.2 V2X certificates use ECDSA over P-256 or P-384. No post-quantum V2X profile has been standardized as of April 2026.

What should OEMs use for OTA update signing?

Hybrid signatures combining ECDSA with ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) are the safest near-term choice. NIST SP 800-208 LMS/HSS stateful hash-based signatures are also appropriate for bounded firmware signing events.

Is the CAN bus itself vulnerable to quantum attacks?

AUTOSAR SecOC symmetric message authentication (typically AES-128-CMAC) is relatively quantum-resistant. Grover's algorithm halves effective key bits, so AES-256 variants remain safe. The real quantum vulnerability is in asymmetric key provisioning and secure boot.

Sources

1. UN ECE R155 Cybersecurity Management System
2. UN ECE R156 Software Update Management System
3. ISO/SAE 21434 Road Vehicles Cybersecurity Engineering
4. NIST FIPS 204 (ML-DSA) Final
5. NIST SP 800-208 Stateful Hash-Based Signatures

Related Articles

• Harvest Now, Decrypt Later Threat
• LMS Stateful Signatures
• ML-DSA vs SLH-DSA Comparison
• Why Hybrid Encryption Matters
• PQC for 5G and 6G Telecom