CRYPTAGION — Post-Quantum Security
Roadmap · Method

How to prepare your post-quantum roadmap: a 7-step method and a template

· 10 min read · By Ali Korsi A post-quantum roadmap is the document your board approves and your supervisor reads. How to build one that holds up: who owns it, what goes in it, how to order the work and how to show progress.

Lire en français

Most regulated organisations now accept that they will have to move away from RSA and elliptic-curve cryptography. Far fewer have a document that says how. The EU’s Coordinated Implementation Roadmap expects the transition to have started by the end of 2026 and high-risk use cases to be migrated by the end of 2030 (what each milestone asks for). This guide covers the work in between: turning a policy deadline into a plan your own teams can carry out.

A good post-quantum roadmap is not a list of RSA findings, and it is not a copy of the EU calendar. It answers five questions:

  1. What cryptography do we have, and where is it?
  2. Which of it is at risk, and by when must it be fixed?
  3. What do we do first, next and last?
  4. Who owns each part, and who pays for it?
  5. How do we show, every quarter, that our exposure is going down?

The seven steps below produce those answers in order. Each step ends with a deliverable that goes into the roadmap document described at the end of this guide.

Step 1: Get a mandate and name an owner

A post-quantum migration touches applications, infrastructure, PKI, suppliers and budgets over almost a decade. Without an executive sponsor, it stalls at the first contract that has to be renegotiated.

Anchor the mandate in obligations the board already recognises. NIS2 Article 21(2)(h) requires policies on the use of cryptography. Under DORA, Article 6 of the ICT risk management RTS (Delegated Regulation (EU) 2024/1774) requires the encryption policy to provide for updating cryptographic technology as cryptanalysis develops. The EU roadmap supplies the dates against which those policies will be read.

Deliverable: a one-page mandate signed by the sponsor, naming the owner, the steering body and the review cadence.

Step 2: Scope from business services, not systems

Starting from a list of servers produces an inventory nobody can prioritise. Start instead from the services the organisation must keep running and protected: the critical or important functions you already report under DORA, or the services in scope of NIS2. Then list the cryptographic use cases behind each one.

Use caseTypical cryptographyWhy it matters
External TLS (websites, APIs)ECDHE key exchange, RSA or ECDSA certificatesTraffic can be recorded today and decrypted later
Internal TLS, mTLS, service meshThe same, often with private CAsHigh volume and rarely inventoried
VPNs and site-to-site linksIKEv2 with (EC)DH, RSA or ECDSA authenticationLong-lived links carrying sensitive data
SSH and administrationRSA or ECDSA keys, ECDHPrivileged access paths
PKI, code and firmware signingRSA or ECDSA signatures, long-lived rootsHardest to change; signatures must outlive the device
Data at rest and archivesSymmetric encryption, keys wrapped with RSALong confidentiality requirements
Email and document signingS/MIME, CMS, RSA or ECDSALegal value that lasts for years
HSM, KMS and cloud key managementDepends on the vendorLimited by the supplier’s own roadmap
OT and embedded devicesFixed in firmwareLifecycles of 15 years or more
Deliverable: a scoped list of services and cryptographic use cases, each with a business owner.

Step 3: Build an inventory you can trust

The roadmap is only as good as the inventory beneath it. For each use case, find where the cryptography really is: in source code (library calls, algorithms, key sizes), in certificates, in live TLS and SSH configurations, in keystores and cloud KMS, and in the products you buy. Three rules keep the inventory usable:

Our guides on what a CBOM looks like and how to estimate the blast radius of a migration cover this step in detail.

Deliverable: a versioned inventory (CBOM) per service, with its coverage and known gaps stated.

Step 4: Classify risk by use case

Not everything has to move by 2030. The EU roadmap separates high-, medium- and low-risk use cases, and your own classification decides which group each one falls into. Three questions drive it:

  1. How long must the data stay confidential? If the answer is ten years or more, traffic recorded today is already exposed. This is the harvest-now-decrypt-later risk.
  2. How long will the migration take? Large estates, embedded systems and supplier dependencies can take years.
  3. How long must a signature be trusted? Root certificates, firmware signatures and signed archives must remain verifiable for their whole life, so they need a post-quantum path well before the device or document is retired.
Mosca’s inequality: if the time the data must stay secret (X) plus the time needed to migrate (Y) is longer than the time until a cryptographically relevant quantum computer exists (Z), the asset is already at risk. Test your own figures with the HNDL calculator.

A practical rule set, aligned with the EU milestones:

ClassTypical profileEU target
HighData that must stay confidential for 10+ years, long migrations, long-lived roots of trust, internet-facing key exchangeMigrated by the end of 2030
MediumInternal services, shorter-lived data, moderate migration effortMigrated by the end of 2035
LowShort-lived data, little exposure, systems due for retirementAs far as feasible by 2035, or retired

Write the criteria down. A supervisor will want to know why a use case is classed as medium rather than high, and written criteria are what make the answers consistent.

Deliverable: a risk register per use case, with its class, the reasoning and a target date.

Step 5: Define the target state

The roadmap has to say what “migrated” means. For most EU organisations, the answer follows the national agencies:

Record these choices in the cryptography policy itself, so the policy and the roadmap say the same thing. See crypto-agility explained and our comparison of BSI, ENISA, NCSC and ANSSI guidance.

Deliverable: an updated cryptography policy and a short target architecture for each use case.

Step 6: Sequence the work in dated waves

Order the work by risk class, then by effort and dependencies: a use case that relies on a PKI change cannot move before the PKI does. Tie each wave to the external milestones, so the plan can be read against them.

PeriodFocusExample deliverables
Now to end-2026Evidence and pilotsScoped inventory, risk register, signed roadmap, one or two pilots on high-risk use cases, such as hybrid TLS on an external service
2027–2028High risk, quick to moveHybrid key exchange on external TLS and VPNs, post-quantum requirements in every new purchase, a PKI and HSM upgrade plan
2029–2030High risk, hard to moveRemaining high-risk use cases migrated, post-quantum or hybrid signatures for code signing and new roots
2031–2035Medium and low riskInternal services, OT and embedded systems at their refresh, retirement of legacy cryptography

Then check the plan against the national dates that apply to you:

Use natural refresh cycles. Hardware renewals, certificate rotations and contract renewals are the cheapest moments to migrate, so map them onto the waves instead of funding a separate project for each change.

Deliverable: a wave plan with dates, dependencies and an owner for each wave.

Step 7: Bring in suppliers and the budget

Much of your cryptography sits in products you buy: HSMs, VPN appliances, load balancers, PKI software, SaaS and OT equipment. Their roadmaps set the limits of yours. Ask each critical supplier, in writing:

Add the same points to contract templates and renewals, so that every new purchase reduces your exposure instead of extending it.

For the budget, estimate effort wave by wave rather than for the whole programme at once. The inventory gives the number of affected components, and the classification and blast-radius analysis give the effort for each. Keep the one-off project costs (inventory, pilots, PKI changes) separate from running costs (continuous discovery, supplier follow-up, policy reviews).

Deliverable: a supplier register with post-quantum status and committed dates, and a budget for each wave.

Measure progress every quarter

A roadmap that is never measured turns into a slide. Choose a few indicators that come straight from the inventory, so they can be recomputed after each scan:

Review the roadmap with the steering body every quarter and reissue it once a year, or sooner if a standard, a national guideline or a supplier date changes. Our PQC standards tracker lists the sources to watch.

The roadmap document: a template

Bring the seven deliverables together in one document. This structure works for a board and for a supervisor:

  1. Executive summary: today’s exposure, the targets, the budget and the decisions needed.
  2. Mandate and governance: sponsor, owner, steering body, review cadence.
  3. Scope: services and cryptographic use cases, with their business owners.
  4. Inventory summary: coverage, method, known gaps, and a link to the CBOM.
  5. Risk classification: the criteria, results by class, and the reasoning for borderline cases.
  6. Target state: cryptography policy, hybrid choices, crypto-agility requirements.
  7. Migration waves: dates, dependencies, owners and pilots.
  8. Suppliers: status and committed dates for critical products.
  9. Budget and resources: per wave, split between project and running costs.
  10. Indicators and reporting: KPIs, baseline and targets.
  11. Exceptions: risk acceptances, each with an owner and an expiry date.

Keep the document short and link to the detail. The inventory and the risk register will change every quarter; the roadmap should not need rewriting each time they do.

Five mistakes to avoid

A post-quantum roadmap is a management document built on technical evidence. Without the evidence it is a wish list; without the management, it is a scan report.

How CRYPTAGION fits

CRYPTAGION produces the inputs for steps 3, 4 and 6, and the indicators that follow them. It discovers cryptography across code, Git repositories, certificates, TLS endpoints, keystores and cloud KMS on a schedule, scores each finding from 0 to 100 including its harvest-now-decrypt-later exposure, and exports a CycloneDX 1.6 CBOM, a four-wave migration roadmap and a CISO report. It runs on-premises or air-gapped. The fixed-scope readiness pilot covers one critical domain and produces the end-2026 evidence for it.

The takeaway

Get a mandate, scope from services, inventory what is really deployed, classify by data lifetime and migration time, fix the target state, sequence the work in waves tied to 2026, 2030 and 2035, and bring suppliers in early. With two months left in 2026, the first three steps and a signed roadmap are a realistic goal for this year. The CISO readiness checklist is a quick way to see where you stand before you start.

Sources

Start with the inventory

Every step of the roadmap depends on knowing where your cryptography is. CRYPTAGION builds that inventory inside your perimeter, with the risk scores and CBOM the roadmap needs.

Book a live scan → Or take the 2-minute readiness assessment

← All resources · Home