Skip to content
Web Development15 min read

Post-Quantum Cryptography Readiness: What Software Businesses Should Do Now

How software teams can prepare for post-quantum cryptography: NIST standards, government deadlines, cryptographic inventory, crypto agility and migration.

01

The short answer

Quantum computers can't break today's public-key cryptography yet, but governments have set migration deadlines in the early to mid 2030s, and data encrypted today could be stored and decrypted later. Software businesses should start now with three things: an inventory of where and how they use cryptography, a priority list based on how long data must stay confidential and how long systems will live, and crypto agility, so algorithms can be swapped through configuration and library upgrades rather than rewrites. Much of the first wave of protection arrives through updated TLS libraries, browsers and cloud services; the harder work is signatures, certificates, embedded devices and your own code.

This guide is for CTOs, security leads and engineering teams at SaaS, fintech, healthcare and enterprise software businesses. It summarises the standards and deadlines, then sets out a practical plan.

02

Why act before quantum computers exist

Two reasons. First, harvest now, decrypt later: an adversary can record encrypted traffic or steal encrypted archives today and wait until a capable quantum computer exists. If your data must stay confidential for ten years or more (health records, financial data, intellectual property, government contracts), the risk window has already started. Second, migration takes years. Cryptography is buried in libraries, protocols, certificates, hardware, partner integrations and contracts, and changing it safely is slow.

Worth noting

Timelines for a cryptographically relevant quantum computer are uncertain, and forecasts vary widely. Plans should be driven by the official deadlines and by how long your data and systems need protection, not by predictions of a specific year.

03

The standards

StandardAlgorithmPurposeStatus (Nov 2026)
FIPS 203ML-KEM (from CRYSTALS-Kyber)Key establishmentFinal, August 2024
FIPS 204ML-DSA (from CRYSTALS-Dilithium)Digital signaturesFinal, August 2024
FIPS 205SLH-DSA (from SPHINCS+)Hash-based digital signaturesFinal, August 2024
FIPS 206FN-DSA (from Falcon)Compact digital signaturesIn development
HQCCode-based key establishmentBackup to ML-KEM using different mathematicsSelected March 2025; final standard expected around 2027
04

Government timelines

Deadlines differ by country and mostly apply directly to government and critical infrastructure, but they shape what enterprise customers and regulators will ask of suppliers. Checked in November 2026:

JurisdictionGuidance
United StatesNIST's transition report (IR 8547, finalised October 2026) deprecates quantum-vulnerable public-key algorithms after 2030 and disallows them by 2035. A June 2026 executive order requires high-value federal systems to use post-quantum key establishment by the end of 2030 and signatures by the end of 2031, with requirements expected to flow to federal contractors.
United KingdomThe NCSC's timeline (March 2025): complete discovery and an initial plan by 2028, migrate the highest-priority systems by 2031, and complete migration by 2035.
European UnionA coordinated roadmap (June 2025): member states start the transition by the end of 2026, migrate high-risk use cases by the end of 2030, and the rest by 2035.
AustraliaThe Australian Signals Directorate's guidance recommends ceasing use of traditional asymmetric cryptography by the end of 2030.
SingaporeThe Monetary Authority of Singapore issued an advisory on quantum-related cybersecurity risks in 2024, focused on inventory and crypto agility, and the Cyber Security Agency has published a quantum-safe handbook.
IndiaA national task force report on a quantum-safe ecosystem was published in 2026 under the National Quantum Mission; check sector regulators for specific requirements.
05

What is already happening without you

A lot of protection is arriving through updates you may already be receiving. Chrome and Firefox enable hybrid post-quantum key exchange (X25519 combined with ML-KEM) in TLS by default, OpenSSL 3.5 includes post-quantum algorithms and hybrid key shares by default, Cloudflare reports that most browser traffic through its network is now post-quantum encrypted, and messaging apps such as iMessage and Signal have added post-quantum protection. Cloud key management services are adding post-quantum signature keys; AWS KMS, for example, supports ML-DSA.

That covers much of the risk to data in transit over the public web, provided your servers, load balancers and CDNs are updated. It doesn't cover internal service-to-service traffic on old libraries, mobile apps pinned to old crypto, VPNs, partner integrations, signed software and documents, certificates, hardware security modules, IoT devices, or anything your own code implements directly.

06

Step 1: build a cryptographic inventory

You can't migrate what you can't find. Build an inventory, sometimes called a cryptographic bill of materials, that records:

  • Where cryptography is used: TLS endpoints, VPNs, SSH, databases, file and backup encryption, message signing, JWTs and tokens, code signing, document signatures, payment integrations, HSMs and key management
  • Which algorithms and key sizes, and which library or service provides them
  • Certificates: issuers, algorithms, expiry and where they are pinned
  • Third parties: vendors, SaaS tools, payment providers and partners whose crypto you depend on
  • Data lifetime: how long the protected data must remain confidential or signatures must remain trustworthy
  • System lifetime: how long the system or device will remain in service
07

Step 2: prioritise

A useful rule of thumb: if the time your data must stay secret, plus the time migration will take, is longer than the time until a quantum threat might arrive, you should act now. In practice, prioritise:

PriorityExamples
FirstLong-lived confidential data in transit or archived (health, financial, legal, IP); key exchange on external connections; systems or devices that will stay in service for 10+ years
NextSignatures that must stay trustworthy for years (software updates, firmware, contracts, certificates with long chains); partner and payment integrations
LaterShort-lived data and systems due for replacement anyway
08

Step 3: build crypto agility into your software

  • Use well-maintained, current cryptographic libraries rather than custom implementations
  • Keep cryptography behind a small number of internal interfaces, not scattered across the codebase
  • Choose algorithms and key sizes through configuration, so they can change without code changes
  • Avoid hard-coding certificate algorithms or pinning in mobile apps without an update path
  • Record algorithm identifiers alongside encrypted data and signatures, so old and new formats can coexist during migration
  • Add cryptographic checks to CI, for example flagging deprecated algorithms or outdated libraries
  • Plan for larger keys and signatures: post-quantum signatures and keys are bigger, which affects certificate sizes, handshake sizes, database fields and constrained devices

Planning for post-quantum migration?

ZSpace Labs helps teams build secure, crypto-agile applications: cryptographic inventories, library upgrades, key management integration and testing for larger post-quantum keys and signatures.

Start a Project
09

Step 4: migrate and test

AreaTypical action
Public TLSUpgrade servers, load balancers and CDNs to versions supporting hybrid ML-KEM key exchange; test older clients
Internal servicesUpgrade TLS libraries and service meshes; enable hybrid key exchange
Mobile appsUpdate networking libraries and any certificate pinning, with an app update path
Signatures and certificatesFollow your certificate authorities' and platforms' post-quantum roadmaps; test larger certificates and signatures
Stored dataRe-encrypt long-lived archives where key exchange or key wrapping relied on vulnerable algorithms
VendorsAsk suppliers for their post-quantum roadmap and add it to procurement and security questionnaires
10

Common mistakes

  • Waiting for a quantum computer announcement before starting the inventory
  • Assuming browser support means the whole system is protected
  • Implementing post-quantum algorithms yourself instead of using vetted libraries
  • Forgetting signatures, certificates and firmware, which often have the longest lifetimes
  • Ignoring the size and performance impact of larger keys on constrained devices and protocols
  • Treating this as a one-off migration instead of building crypto agility
11

Conclusion

Post-quantum readiness is a planning and engineering exercise, not a panic. Inventory your cryptography, prioritise by data and system lifetime, keep libraries current, build crypto agility, and work through signatures, certificates and integrations ahead of the 2030 to 2035 deadlines. For protecting keys and secrets more generally, see secrets management, and for protecting data while it is processed, confidential computing.

Need a cryptographic inventory?

Tell us about your applications, integrations and data retention needs. ZSpace Labs will help you scope a practical post-quantum readiness plan. Discuss your security roadmap.

Start a Project
FAQ

Common questions.

Not today. Security agencies including the UK NCSC and the US CISA state that a cryptographically relevant quantum computer, one able to break today's public-key cryptography, does not yet exist. The concern is the future: data intercepted now could be decrypted later if such a machine is built, which is why long-lived sensitive data and long-lived systems need attention first.

NIST published three standards in August 2024: FIPS 203 (ML-KEM) for key establishment, FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) for digital signatures. A further signature standard (FN-DSA, FIPS 206) is in development, and NIST selected HQC in March 2025 as a backup key-establishment algorithm, with a final standard expected around 2027.

The ability to change cryptographic algorithms, key sizes and libraries without redesigning applications: algorithms chosen by configuration, cryptography behind well-defined interfaces, and an inventory of where cryptography is used. NIST has published guidance on achieving it. It matters because post-quantum migration will not be the last algorithm change.

The main risk is to public-key cryptography (RSA, Diffie-Hellman and elliptic-curve algorithms) used for key exchange and signatures. Symmetric algorithms such as AES with adequate key lengths are much less affected; follow your national guidance on recommended key sizes.

Combining a classical algorithm (such as X25519) with a post-quantum one (such as ML-KEM) so a connection stays secure if either holds. Major browsers and libraries now support hybrid TLS key exchange; Chrome and Firefox enable it by default, and OpenSSL 3.5 includes it in its default key shares. Some national agencies prefer pure post-quantum schemes in the long term, so check your regulator's position.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.