Post-quantum cryptography: what organizations should do now

Public-key cryptography underpins everything from secure web browsing to code signing and secure email. Cryptographic algorithms like RSA and ECDSA rely on mathematical problems that are hard for classical computers, but advancing quantum technologies threaten to make those problems tractable.

That doesn’t mean immediate panic, but it does mean proactive planning is essential to protect long-lived data and critical systems.

Why this matters today
Many sensitive records—backups, archived emails, intellectual property, and long-term contracts—must remain confidential for years. If an attacker records encrypted traffic today and later obtains a quantum-capable machine, those archives could be decrypted. High-value targets and regulated industries are especially exposed. The good news: standards bodies and vendors are rolling out quantum-resistant algorithms and best practices, and there are pragmatic steps organizations can take now.

Key concepts to understand
– Post-quantum algorithms: A new family of public-key algorithms designed to resist quantum attacks.

Some are already standardized and available in libraries and cloud services.

– Hybrid cryptography: Combining classical and post-quantum algorithms in parallel so that security doesn’t hinge on a single primitive during transition.
– Crypto agility: The capacity to swap cryptographic algorithms, parameters, and keys quickly across systems without major rewrites.
– Long-lived data risk: Data encrypted today with vulnerable algorithms can be exposed later, so prioritize assets based on retention time and sensitivity.

Practical migration checklist
1.

Inventory cryptographic use: Identify where public-key cryptography is used—TLS, VPNs, code signing, PKI, SSH, email encryption, and hardware devices.

Note key lifetimes and data retention windows.
2. Classify risk: Prioritize systems that protect highly sensitive or long-lived data, or those with regulatory implications.
3.

Embrace crypto agility: Design or refactor systems to support multiple algorithms and update configurations without deep code changes. Use libraries and protocols that make algorithm swaps straightforward.
4.

Adopt hybrid modes where available: Implement hybrid key exchanges and signatures that pair classical algorithms with post-quantum candidates to balance immediate compatibility and future resilience.

5. Update certificates and PKI practices: Work with certificate authorities and vendors to obtain certificates that support new algorithms and plan for certificate lifecycle changes.
6. Strengthen key management: Review key generation, storage, rotation, and destruction policies. Hardware security modules (HSMs) and secure elements should be assessed for post-quantum support.
7. Test thoroughly: Validate interoperability across clients, servers, devices, and third-party integrations. Performance and resource impact testing is crucial—some post-quantum algorithms have different key and signature sizes.

8. Monitor standards and vendor guidance: Follow ongoing standardization and vendor roadmaps to avoid lock-in and to adopt proven implementations.

Performance and compatibility considerations
Post-quantum schemes vary in computational cost and ciphertext/signature size.

This can affect latency, bandwidth, and constrained devices. Hybrid deployments help maintain compatibility with legacy systems while enabling gradual upgrades.

Expect iterative tuning: select algorithms appropriate to each use case rather than a one-size-fits-all approach.

Governance and procurement tips
Include post-quantum requirements in procurement contracts, ask vendors about roadmap and testing for quantum-resistant algorithms, and require cryptographic agility.

Create an internal governance group to track progress, update policies, and run tabletop exercises simulating migration scenarios.

Final note
Preparing for quantum-capable threats is a risk-management exercise. Organizations that inventory cryptographic assets, prioritize high-risk data, and build agility into systems will navigate the transition with less disruption and stronger long-term security. Start with an inventory and a pilot hybrid deployment to build experience before broader rollouts.