All articles

How do you start a post-quantum migration?

Start with a reliable overview and a justified order of work. Post-quantum cryptography, or PQC, aims to withstand attacks using future quantum computers. Migration involves systems, data, suppliers and operations.

Distinguish the cryptographic roles

Sufficiently powerful quantum computers would threaten widely used public-key algorithms such as RSA and elliptic-curve schemes. Key exchange and digital signatures are among the affected functions. This does not mean every kind of cryptography needs the same replacement.

You should therefore first establish what an algorithm is used for. Symmetric data encryption, hash functions and public-key algorithms have different properties. The choice of a target algorithm must suit the protocol, the implementation and the protection requirements. An algorithm name alone does not answer these questions.

Prioritise protection lifetime and migration effort

Data that must remain confidential for a long time deserves early attention. Attackers could record encrypted communication today and decrypt it later if its cryptography can then be broken. This is often called “harvest now, decrypt later”.

At the same time, consider how long the conversion will take: supplier dependencies, long-lived devices, components that are hard to replace and coordination with customers can lengthen the process. Signatures require a separate assessment of their trust chains and validity requirements. Derive priorities from these properties instead of treating all findings alike.

Turn the inventory into a work plan

Start with a clearly bounded service or software project. Inventory its cryptography and add configurations, external services and responsible teams. Clarify with suppliers which target algorithms and protocol variants are actually supported. Unknown dependencies remain in the plan as open tasks.

Define a verifiable completion point for each migration wave: Which components change? Which peers have to work together? Who approves? NIST’s migration project covers the discovery of the inventory as well as interoperability and performance. This combination is essential for a workable plan.

Give the pilot clear boundaries

First trial the selected change in a suitable test environment. Check successful connections, error handling, larger messages or signatures and interoperability with existing components. Document software versions and settings so that results can be interpreted later.

Demonstrate progress with traceable evidence

Keep the initial inventory, plan, test results, approvals and verification together. Compare the same area before and after the change and explicitly map related findings. A finding that has disappeared may also be due to changed detection or a smaller scan scope.

Identify remaining risks and justify exceptions, stating a responsible body and a review date. This makes it possible to explain progress without inferring the security of the entire organisation from a successful pilot project. Update the plan when the inventory, standards or supplier offerings change.

Brief answers

Must everything move to PQC at once?

No. Priorities depend on protection requirements, dependencies and technical readiness. Components that work together must still coordinate their transition.

Is there one binding deadline for everyone?

A general PQC roadmap does not establish a universal legal deadline. Separately check the rules, contracts and sector requirements that apply to your organisation.

Avalanche Anchor brings together Quantum reports and Transcendence migration evidence. Originals and evaluations remain traceably connected. This supports the review of the documented state; expert assessment remains with your team.

Connect migration evidence with Anchor

Sources and foundations

  1. NIST NCCoE · Migration to Post-Quantum Cryptography
  2. CISA, NSA & NIST · Quantum-Readiness: Migration to Post-Quantum Cryptography
  3. NIST CSWP 39upd1 · Considerations for Achieving Crypto Agility