Quantum risk in automotive and transport

Because of the gap between vehicle life and algorithm life. A car type-approved in 2026 will typically still be driven in the 2040s, and its secure boot, OTA updates and V2X messages all trust ECDSA or RSA signatures. NIST deprecates those algorithms after 2030 and disallows them after 2035. A cryptographically relevant quantum computer would let an attacker forge the signature on a firmware update or a V2X certificate chain for an entire fleet, so the decision has to be made at design time, years before the threat arrives.

Not by name. R155 requires a cyber security management system that identifies and manages risks across the vehicle lifecycle, and ISO/SAE 21434:2021 sets out the threat analysis and risk assessment method without naming algorithms. Neither has been amended for post-quantum cryptography. The obligation is indirect: a threat analysis that ignores quantum cryptanalysis for keys trusted past 2030 is hard to defend, and R156 expects an update process that can keep the vehicle secure for its life.

The EU roadmap targets high-risk use cases by the end of 2030 and as many systems as feasible by 2035. NIST IR 8547 deprecates 112-bit RSA and ECC after 2030 and disallows them after 2035. The UK NCSC sets milestones at 2028, 2031 and 2035. For transport the harder date is the one you set yourself: the last model year, refit or re-signalling before 2035 in which a hardware change is still possible.

An adversary records encrypted traffic or data today and stores it until a quantum computer can break the encryption. In transport that covers telematics and location data, maintenance and design data exchanged with suppliers, passenger records and anything tunnelled over TLS or a VPN between vehicles, depots and back ends. Any record that must stay confidential beyond the arrival of that computer is already at risk.

IEEE 1609.2 and ETSI ITS messages are signed with ECDSA, and the certificates come from a credential management system: the EU C-ITS CCMS in Europe and the SCMS in the United States. ML-DSA signatures are roughly 2.4 KB against 64 bytes for ECDSA, which strains the bandwidth and latency budgets of basic safety messages. Working groups are developing post-quantum options, but no ratified amendment exists yet, so the practical move today is to specify crypto-agile hardware and plan for hybrid signatures.

Only where the ECU has the flash, memory and boot-time budget to verify ML-DSA, and where the root of trust can be updated. For many ECU families it can, through a dual-signature period in which updates carry both an ECDSA and an ML-DSA signature. For others it cannot, and those units will carry the old algorithm until the vehicle is scrapped. Classifying each ECU family into one of those two groups is the first engineering deliverable of a programme.

Not to type-approved vehicles, which are covered by the General Safety Regulation and UN R155 instead. Certified aircraft products and marine equipment are excluded too. It does apply to aftermarket telematics, fleet trackers, chargers, port and rail IoT and most other connected devices placed on the EU market, with reporting obligations since 11 September 2026 and full application from 11 December 2027. Those products must protect data with state-of-the-art encryption and be supported with security updates, which is where crypto-agility becomes a product requirement.

The ETCS radio link itself relies on symmetric keys, so the exposure sits in how those keys are distributed, in the IP-based radio that CBTC and FRMCS use, and in the fact that trackside and on-board assets last 25 to 30 years. Rail cyber security standards build on IEC 62443, which gives you the zones and conduits model to sequence the work, and NIS2 puts rail infrastructure managers and operators in scope as essential entities.

Put cryptographic lifetime into the risk assessments you already owe. Part-IS has applied to aviation organisations since 22 February 2026 and asks for an information security risk assessment. IMO Resolution MSC.428(98) requires cyber risk in the ship's safety management system. In both cases the first step is the same: inventory the cryptography in airline, airport, port and shipping systems, identify what must hold past 2030, and ask suppliers for their post-quantum roadmaps.

Five numbers: the share of your fleet or assets that will still be in service after 2035 and cannot change algorithm by update, inventory coverage of in-service platforms and safety systems, how many Tier 1 suppliers and certificate providers have a post-quantum roadmap, how many ECU families and services are crypto-agile, and budget and milestones against the 2027, 2030 and 2035 deadlines.

Everything on this page. The two-minute readiness check scores your automotive and transport programme and routes you to the right next step. The free tools, including the OT Protocol Quantum Vulnerability Scanner and the HNDL Risk Calculator, run in your browser with no registration. The weekly peer call runs every Tuesday at 15:00 CET and is open to anyone. Sample lectures from the 170-plus expert library are linked above, and the page is reviewed as the mandates change; the date beside the key facts is the last check.

It depends on the role. Board and executives start with the Certified Quantum Business Professional bootcamp, about 22 hours self-paced across ten modules. Security, risk and IT teams take Introduction to Quantum Cyber Security, four to five hours online with a QSECDEF certificate. OEM product security and OTA engineers take Quantum-Safe OTA Update Security for Connected Vehicles, for OEM product security and OTA engineers. Whoever will run the migration takes CPQCPM, the Certified Post Quantum Cryptography Programme Manager course: ten hours live online over five weeks, with the next public cohort in January 2027.

Yes. QSECDEF runs private CPQCPM cohorts for a single organisation, live online or in person, and private deliveries of the sector courses listed under Equip your people for your OEM product security and OTA engineers. Board and leadership workshops are built on your own exposure and obligations and end with an agreed position on quantum risk. Use the contact button in the For your organisation section and tell us your timeline.

Through the QSECDEF Expert Members directory. Every listed member has been vetted, has signed the Members' Charter and has presented to the community. You can filter by consulting and services, technology vendor or enablement and investment, and send a request for further information from the member's own page. QSECDEF is vendor-neutral and sells training, not migration products, so the shortlist stays yours.

Two routes. QSECDEF membership gives your team the self-paced courses, the full lecture archive, the weekly call and 25 per cent off CPQCPM and partner training. Expert Membership is for the builders, consultancies and technology vendors serving automotive and transport who want to be found by the people reading this page; it includes a showcase listing with an enquiry form, the Industry Conversations and speaking slots at the annual QSECDEF symposium.

No. QSECDEF is a vendor-neutral membership network. We train people and connect them with peers and peer-reviewed experts; we do not sell migration software, hardware or services.

CPQCPM is ten hours of live instruction over five weeks, two hours a week. The Introduction to Quantum Cyber Security course is 4 to 5 hours, self-paced. The business bootcamp is self-paced. The automotive engineering courses on OTA security, V2X protocols and supply chain cryptographic risk are each a full day of six hours, in person or online.