1. Why the migration starts now
Most public-key cryptography in use today, which protects TLS certificates, VPN authentication and code signing, relies on mathematical problems that a sufficiently large quantum computer could solve. No such machine is available today to break ordinary keys in real time. The concern is about data that must stay confidential for years. An attacker can record encrypted traffic now and decrypt it later, once the capability exists. That is why organizations begin the transition before the threat becomes practical.
The work is slow because cryptography is embedded almost everywhere: certificate authorities, devices, VPN gateways, applications, libraries, hardware security modules and third-party services. The first task is an inventory, not a product purchase. Without knowing where keys and certificates live, who owns them and when they expire, you cannot replace them in an orderly way, and the migration becomes a set of emergency changes.
2. What changes in PKI and TLS
Public key infrastructure (PKI) issues and manages certificates that bind keys to identities. Transport Layer Security (TLS) uses those certificates and key exchanges to protect connections. Post-quantum algorithms are designed to resist quantum attacks, and they are generally larger in key and signature size than the classical algorithms they replace. That increases the size of handshakes and certificate chains, raises storage needs and can cause compatibility problems with older devices or with network equipment that inspects traffic.
A practical transition pattern is hybrid key exchange, which combines a classical algorithm with a post-quantum one, so that the connection stays protected if either algorithm turns out to be weak. Signatures and certificate chains are harder. A root certificate authority with a long lifetime needs careful planning, because replacing a root that is trusted across a whole fleet is a major operation. Confirm with each supplier which algorithms and hybrid modes they support, and in which product versions.
3. Comparing migration approaches
The approaches differ in their immediate benefit and in the effort they require. An inventory and crypto agility work are the foundation for everything else, and they pay off whatever the timeline turns out to be. Hybrid key exchange on externally facing services and remote access addresses the recorded-traffic risk early. Post-quantum certificates for internal services make sense where you control both endpoints. Replacing the root certificate authority is the last step, once the earlier stages have been proven in practice.
The table summarizes the approaches. Start with the first row for every organization, and move to the others as the inventory shows where the risk and the control are. Treat each stage as a pilot with a rollback path, because interoperability problems are much easier to fix when they affect a small group of endpoints. Record the result of each stage before moving on.
| Approach | Benefit | Constraint | Suitable for |
|---|---|---|---|
| Inventory and crypto agility first | Shows exposure and makes future change cheaper | Takes time and needs cooperation across teams | Every organization, as the starting point |
| Hybrid key exchange for TLS and VPN | Protects sessions against recorded-traffic attacks while keeping classical security | Larger handshakes, and support is needed on both ends | Externally facing services and remote access |
| Post-quantum certificates for internal services | Modernizes identity for internal systems | Requires client, library and device support | Services where you control both endpoints |
| Replacing the root certificate authority | A long-term reset of trust | A major operation with wide impact and a long lead time | Only after the earlier stages are proven |
4. Building a cryptographic inventory
A cryptographic inventory lists every place where keys, certificates and algorithms are used. That includes web servers, load balancers, VPN gateways, code signing, email, storage encryption, backup tools and third-party integrations. For each item, record the algorithm, the key size, the expiry date and the owner. Many organizations discover certificates that nobody remembers issuing, and those are the ones that cause outages when they expire unexpectedly.
Crypto agility is the ability to change algorithms without redesigning the system around them. It means that configuration is centralized, that libraries can be updated without rewriting applications and that protocols can negotiate the algorithm in use. Without agility, each migration becomes a separate project. Start by removing hard-coded algorithm choices in the code you control, and by moving certificate settings into a managed location that the team can change safely.
5. Checklist for a post-quantum readiness plan
A readiness plan should be concrete enough to schedule. The checklist below moves from the inventory to the priorities, then to compatibility testing and finally to the rollback plan. Each item should name an owner and produce evidence, such as an inventory export, a test report or a configuration change record. Assign each owner a due date for that evidence, and review progress every month.
Review the plan with the teams that operate the systems, not only with the security function. The people who renew certificates and maintain VPN gateways know where the surprises are, and their input determines whether the schedule is realistic. Ask them which systems they expect to be hardest to change, and why, and write down their answers before the schedule is fixed.
- Inventory certificates, keys and algorithms across all systems and suppliers.
- Classify data by how long it must remain confidential.
- Prioritize externally facing services and remote access for the first hybrid deployments.
- Confirm that libraries, operating systems and devices support the chosen algorithms.
- Test handshake size and connection performance on representative devices and networks.
- Plan certificate lifetimes so that replacements are routine rather than emergencies.
- Keep the classical fallback and a rollback path until interoperability has been proven.
6. Common mistakes and what to ask suppliers
A common mistake is treating post-quantum readiness as a single upgrade that is switched on at a fixed date. Another is enabling a new algorithm on the server while clients or network devices silently fail to negotiate it, which produces connection problems that are hard to diagnose. Test with real clients, including older ones and those behind inspection devices, and monitor failure rates after every change.
Ask suppliers which post-quantum algorithms they support, whether those are offered in hybrid or pure modes, which product versions include them and what their timeline for updates is. Ask how key material is protected in their hardware and whether the migration path requires new hardware. Ask for test evidence from a comparable deployment, not only for a roadmap, because roadmaps change more often than configurations do.
7. How to start with a cryptographic inventory
Pick one domain, such as external web services or VPN access, and inventory it completely. Include the certificate authority that issues each certificate, the lifetime of each certificate and the systems that depend on it. The result shows which systems can be upgraded with existing tools and which will need a new plan, and it gives you the first realistic estimate of the effort.
Then set up a small pilot: enable a hybrid option on one non-critical external endpoint, measure connection success across the client types you actually have, and document the results. The first concrete step is to ask your team for a list of every certificate issued by your internal PKI, with its owner and expiry date, and to identify the systems that still depend on the oldest algorithms.
Frequently Asked Questions
Do we need to replace everything now?
No. Start with an inventory, then prioritize the data and systems with long confidentiality requirements and external exposure. A phased approach lets you learn from pilots and avoids a rushed change to root trust, which is the most disruptive part of the work.
What does harvest now, decrypt later mean?
An attacker records encrypted traffic today and stores it until a capable quantum computer is available to decrypt it. This matters most for data that must stay confidential for many years. It is one of the main reasons to prioritize key exchange for sensitive connections, even before certificates are changed.
Are post-quantum certificates already widely supported?
Support is growing, but it is uneven across clients, libraries and devices. Verify support for each system you rely on, including internal devices and older operating systems, before you change certificate policy. A certificate that a key client cannot validate is an outage, not an upgrade.
Does hybrid mode double the work?
It adds complexity and larger handshakes, but it keeps classical protection in place during the transition. Plan the testing and monitoring effort accordingly, and confirm with each supplier how hybrid modes are configured and whether they are enabled by default.
Are there regulatory requirements for this?
Requirements vary. Frameworks such as ISO/IEC 27001 expect you to manage cryptographic controls in a risk-based way, and sector rules may add specific obligations. Confirm with your compliance advisor which requirements apply to your organization and when they take effect.