The European Commission has published feedback on the EU coordinated roadmap for transition to post-quantum cryptography. The results show broad support for the roadmap’s timelines, risk-based approach, actionable steps, hybrid schemes, and emphasis on crypto agility. They also expose something just as important: many organizations still need clearer answers about quantum-risk estimation, milestones, prioritization, hybrid approaches, the EU’s role, and national roadmaps.
The consultation received 97 submissions. Of those, 73 respondents provided an overall rating or feedback on the roadmap, while 63 asked for clarification in one or more areas. The NIS Cooperation Group responded with a frequently asked questions document covering several of the recurring topics.
This is not evidence that the roadmap failed. It is evidence that moving from policy to operations requires a shared language and a defensible data model. A deadline can establish urgency, but it cannot tell an organization which cryptographic dependency to migrate first or prove that a milestone has been reached.
Risk-based migration requires comparable records
“Prioritize by risk” sounds straightforward until different teams describe cryptographic risk differently. An application team may focus on algorithm use. A data owner may focus on confidentiality lifetime. An identity team may focus on certificate chains and trust anchors. A procurement team may focus on supplier upgrade commitments. A regulator may need evidence that all of those views were considered.
A useful cryptographic record therefore needs more than an algorithm name. It should connect the observation to an asset or service, the security function it performs, the affected data or process, the protocol and implementation, the owner, the supplier, the expected support path, and the evidence’s source and age. That context makes prioritization explainable and repeatable.
Without it, risk classification becomes a workshop artifact that is difficult to update. With it, teams can distinguish high-value public-key exposure from quantum-safe symmetric use, identify long-lived data, expose shared dependencies, and document why one migration is sequenced ahead of another.
Milestones need testable completion criteria
The consultation’s request for clarity on milestones points to a common governance problem. Terms such as “inventory complete,” “migration plan established,” or “high-risk systems transitioned” can mean different things across organizations and countries.
Teams should translate each milestone into evidence questions. What scope was assessed? Which discovery methods were used? When were observations collected? What remains outside coverage? Which systems still depend on quantum-vulnerable public-key cryptography? Who owns each dependency? Which supplier assertions have been verified? What artifact records the decision?
A milestone should not imply certainty beyond the evidence. If discovery covered cloud APIs and network traffic but not embedded-device configuration, the record should preserve that limitation. If a vendor has announced PQC support but the deployed version has not been observed or tested, the inventory should distinguish the product claim from the operating state.
Hybrid schemes must be observed, not merely permitted
Respondents also valued hybrid approaches and crypto agility while seeking more clarification. That combination is understandable. Hybrid cryptography can support a staged transition, but it creates operational questions about negotiation, interoperability, performance, fallback, certificate formats, termination points, and eventual retirement of the classical component.
Policy language that allows or encourages hybrid schemes is only a starting point. Organizations need to record where hybrid operation is intended, where it has been enabled, what was actually negotiated, what dependencies remain, and how configuration can change without rebuilding entire applications. Crypto agility should be demonstrable as controlled replaceability—not treated as a product label.
Prepare for national variation without fragmenting the program
The questions about EU and national roles also have an operational consequence. Organizations working across jurisdictions may face different implementation guidance, sector priorities, assurance expectations, and reporting dates even when the overall 2030–2035 direction is aligned.
The answer is not a separate inventory for every framework. Maintain one canonical cryptographic record, then evaluate it through the relevant policy lenses. Requirements, risk rules, and reporting views can vary while the underlying evidence remains consistent. This reduces duplicated data collection and makes differences between jurisdictions visible instead of burying them in separate spreadsheets.
How Vista Platform can help
Vista Platform is a self-hosted cryptographic system of record. Its operating loop—discovery, canonical inventory, evaluation, action, and proof—supports the kind of evidence discipline the EU feedback makes necessary. Teams can preserve where cryptographic observations came from, evaluate them against PQC and compliance controls, assign remediation, and generate repeatable CBOM evidence for defined scopes.
Vista Platform Core is free of charge and includes discovery, inventory, compliance and PQC assessment, and CBOM generation without asset, sensor, seat, or time caps. Vista tracks and governs post-quantum migration; it does not generate PQC keys or perform every migration. Selected-asset Active Scan is not indiscriminate network scanning, Vista is not a vulnerability scanner, and missing observations are not proof of absence. Learn more about operating a PQC program with Vista or try Vista Core.
What remains uncertain
The published summary reports the consultation counts and major themes, but it does not turn every question into a binding requirement. National roadmaps and sector-specific guidance will continue to shape implementation. Organizations should use the feedback to improve evidence and decision criteria while monitoring authoritative EU and national publications for requirements that apply to their systems.
Sources
- EU Roadmap on Post-Quantum Cryptography — Survey feedback, European Commission, September 2, 2026.
- A Coordinated Implementation Roadmap for the Transition to Post-Quantum Cryptography, European Commission and NIS Cooperation Group, June 23, 2025.