Key highlights
- Quantum computers threaten public-key algorithms such as RSA and elliptic curve cryptography, while approved symmetric algorithms like AES are far less exposed.
- Harvest now, decrypt later attacks mean data with a long confidentiality life is already at risk, even though no cryptanalytically relevant quantum computer has been built.
- NIST published FIPS 203, 204 and 205 in August 2024, and its final transition report deprecates quantum-vulnerable public-key algorithms after 2030 and disallows them after 2035.
- A cryptographic inventory showing where each algorithm is used, what it protects and who owns it is the essential first step.
- Crypto agility, hybrid key exchange and vendor roadmaps let businesses migrate in phases instead of in one risky project.
Most of the encryption protecting your business today relies on public-key algorithms such as RSA and elliptic curve cryptography. They secure website connections, VPNs, software updates, digital signatures and the keys that protect stored data. A sufficiently powerful quantum computer could break them. No one has publicly demonstrated such a machine, and nobody can say with certainty when one will exist.
So why prepare now? Because data stolen today can be stored and decrypted later, and because replacing cryptography across an organization takes years. Post quantum cryptography provides replacement algorithms that run on today's computers, and NIST published the first standards in August 2024. This guide explains the threat in plain language, the standards and official timelines, which systems to prioritize, and a phased plan any business can begin this quarter.
Businesses should start preparing for post quantum cryptography now because attackers can record encrypted traffic today and decrypt it once quantum computers mature, and because past cryptographic migrations have taken 10 to 20 years. The first step is not buying new products. It is building an inventory of where you use cryptography, ranking systems by how long their data must stay secret, and making sure new systems can switch algorithms easily.
- Inventory your cryptography and assign owners
- Prioritize long-lived sensitive data and key exchange
- Adopt NIST FIPS 203, 204 and 205 and design for crypto agility
What quantum computers threaten, and what they do not
Public-key cryptography relies on math problems that are extremely hard for classical computers, such as factoring large numbers for RSA or computing discrete logarithms for Diffie-Hellman and elliptic curve cryptography. A large, fault-tolerant quantum computer running Shor's algorithm could solve these problems efficiently. NIST calls such a machine a cryptanalytically relevant quantum computer.
Two jobs are affected. Key establishment, where two parties agree on a shared secret key, protects confidentiality in protocols such as TLS. Digital signatures protect authenticity in certificates, code signing and signed documents. Both currently depend on quantum-vulnerable algorithms.
Symmetric cryptography is in a much stronger position. NIST's final transition report states that its approved symmetric algorithms, including AES and the SHA-2 and SHA-3 hash families, are significantly less vulnerable to known quantum attacks than public-key standards. The urgent work is replacing public-key algorithms, not rewriting every piece of encryption you own.
No one knows when a cryptanalytically relevant quantum computer will exist, and expert estimates vary widely. This article does not predict a date. The case for acting now rests on facts that can be checked: data captured today stays captured, the standards are already published, and migrations take years.
Harvest now, decrypt later: why the risk already exists
NIST describes the threat directly in its transition report: adversaries collect encrypted data now with the goal of decrypting it once quantum technology matures. Because sensitive data often keeps its value for many years, NIST calls this threat model one of the main reasons the transition is urgent.
A simple way to judge your exposure is Mosca's theorem, which the same report explains. Let X be the number of years your data must stay confidential, Y the years you need to complete migration, and Z the years until a capable quantum computer exists. If X plus Y is greater than Z, data you send today will still be valuable when it can be decrypted.
Consider a health insurer that must keep member records confidential for decades, or a law firm handling merger documents. Their encrypted traffic recorded this year could still be damaging long after it is decrypted. A marketing team's campaign data, by contrast, may lose its value within months.
Signatures face a different risk. A forged signature only matters once quantum computers exist, but devices and certificates built today may still verify signatures far into the future. A medical device or industrial controller shipped in 2027 with a long service life needs a way to trust post-quantum signed updates later.
If your data must stay secret longer than the time left to migrate before quantum attacks arrive, the clock has already run out for that data.
The NIST post-quantum standards you should know
On August 13, 2024, NIST released its first three finalized post-quantum standards and said they were ready for immediate use. NIST mathematician Dustin Moody encouraged system administrators to start integrating them immediately, "because full integration will take time."
| Standard | Algorithm | Derived from | Used for |
|---|---|---|---|
| FIPS 203 | ML-KEM | CRYSTALS-Kyber | Key encapsulation for general encryption, the primary choice |
| FIPS 204 | ML-DSA | CRYSTALS-Dilithium | Digital signatures, the primary choice |
| FIPS 205 | SLH-DSA | SPHINCS+ | Hash-based digital signatures, a backup built on different math |
| In development | FN-DSA | FALCON | An additional digital signature standard |
| In development | HQC-KEM | HQC | A backup key encapsulation method based on error-correcting codes |
In March 2025, NIST selected HQC as a backup to ML-KEM, chosen because it relies on different mathematics. NIST said ML-KEM remains the recommended choice for general encryption and that it planned to finalize the HQC standard in 2027.
Support is reaching mainstream software. The OpenSSL 3.5 release notes list support for ML-KEM, ML-DSA and SLH-DSA, and state that the default TLS key shares now offer the hybrid group X25519MLKEM768 alongside classical X25519.
Official timelines businesses should know
NIST's final report, published in October 2026, says it will deprecate quantum-vulnerable public-key cryptography after 2030 and disallow its use under NIST standards and guidelines after 2035. That covers RSA, ECDSA, EdDSA and the Diffie-Hellman family of key-establishment schemes. Other governments are setting similar dates.
- August 2024 (NIST): FIPS 203, 204 and 205 published and ready for use.
- 2028 (UK NCSC): migration goals defined, discovery completed and an initial plan in place, according to the NCSC migration timelines.
- January 2, 2030 (US federal): agencies must support TLS 1.3, which NIST calls a practical path to hybrid post-quantum key exchange.
- December 31, 2030 (US federal): high value assets and high impact systems must use post-quantum key establishment.
- 2031 (UK NCSC and US federal): the NCSC expects highest-priority migrations to be complete, and US high impact systems must adopt post-quantum signatures by December 31, 2031.
- 2035 (NIST and UK NCSC): quantum-vulnerable algorithms disallowed under NIST standards, and the NCSC target for completing migration.
Even if you never sell to a government, these dates shape vendor roadmaps, procurement questionnaires and customer expectations everywhere. NIST also notes that moving from a standardized algorithm to full integration has historically taken 10 to 20 years, which is why the early milestones focus on discovery and planning.
Which data and systems to prioritize
You cannot migrate everything at once, so rank systems by how long their data must stay confidential and how exposed they are.
- Long-lived confidential data: health records, legal files, intellectual property, identity data and financial records with long retention requirements.
- Data in transit over public networks: TLS for websites and APIs, VPNs and links between offices or data centers, because this is the traffic attackers can record today.
- Long-lived devices: IoT sensors, industrial controllers, vehicles, medical devices and payment terminals that may stay in service for a decade or more.
- Trust anchors: root certificates, code and firmware signing keys, and the PKI that issues identities to users and devices.
- Backups and archives: stored data whose keys were exchanged or wrapped with RSA or elliptic curve algorithms.
Short-lived data, such as session caches or analytics that lose value within days, can usually wait for routine upgrades.
Building a cryptographic inventory
You cannot migrate what you cannot see. A cryptographic inventory records where cryptography is used, which algorithms protect what, and who owns each system. The UK NCSC advises covering servers, workstations, network hardware, mobile devices, IoT and industrial systems, and asking managed service providers to carry out the same assessment for the services they run for you.
- System and owner: the application, service or device, and the person accountable for it.
- Where cryptography is used: TLS, VPN, disk or database encryption, signing, authentication tokens.
- Algorithm and key size: for example RSA-2048, ECDSA P-256 or X25519.
- Implementation: library or product and version, such as OpenSSL, a cloud key management service or a hardware security module.
- Data and lifetime: what the cryptography protects and how long it must stay confidential.
- Upgrade path: whether the component changes through configuration, a patch or only by replacement.
Start with automated discovery. Scan public endpoints for TLS versions and key exchange groups, search code repositories and dependency lists for cryptographic libraries, and export key and certificate reports from your cloud providers. Then fill the gaps by interviewing system owners and vendors. A quick first check of a public endpoint looks like this:
# Requires OpenSSL 3.5 or later. Checks whether a server accepts
# the hybrid post-quantum key exchange group X25519MLKEM768.
openssl s_client -connect example.com:443 -groups X25519MLKEM768 -brief </dev/null
# A server that supports it reports a line such as:
# Negotiated TLS1.3 group: X25519MLKEM768The same inventory that drives post-quantum migration is likely to surface expired certificates, outdated TLS settings and unsupported libraries that are risks today. Fixing those early gives the project value long before any new algorithm is deployed.
Crypto agility: designing systems that can change algorithms
Crypto agility is the ability to switch algorithms without rewriting your applications. It matters because the post-quantum transition will not be the last one, and because standards and best practices are still evolving. These practices help, and they complement the controls in our guide to web application security best practices.
- Centralize cryptography: route all cryptographic operations through a small set of internal libraries or services instead of scattering them across the codebase.
- Make algorithms configuration: treat algorithm choices and key sizes as settings, not hard-coded constants.
- Plan for larger sizes: FIPS 203 lists a 1,184 byte encapsulation key and 1,088 byte ciphertext for ML-KEM-768, and FIPS 204 lists 3,309 byte signatures for ML-DSA-65, which can affect packet sizes, certificate chains, database columns and small devices.
- Use hybrid modes during the transition: combine a classical and a post-quantum algorithm so security holds if either survives. NIST describes hybrids as typically temporary steps toward a full post-quantum setup.
- Ask vendors for roadmaps: get written plans and dates from your cloud, CDN, VPN, identity, hardware security module and SaaS providers.
A phased preparation plan for businesses
The timeframes below are a sensible starting rhythm for a mid-sized organization, not a formal standard. Larger estates will need longer.
- 1
Assign ownership (month 1)
Name an accountable owner and a small working group across security, engineering, infrastructure and procurement.
- 2
Build the inventory (months 1 to 6)
Combine automated scans with owner interviews until every system that uses public-key cryptography is listed.
- 3
Rank by risk
Score each system by data lifetime, exposure to public networks and how hard it is to upgrade, then agree priorities with leadership.
- 4
Take the quick wins
Move to TLS 1.3, update cryptographic libraries, and enable hybrid key exchange where your platforms support it, testing performance as you go.
- 5
Update procurement and contracts
Add post-quantum support and crypto agility requirements to RFPs, renewals and vendor security questionnaires.
- 6
Migrate in waves
Start with external traffic and the highest-priority data, then internal systems, then signatures, certificates and PKI.
- 7
Retire and track
Replace systems that cannot be upgraded, and measure progress against NIST and NCSC milestones each quarter.
Costs and common obstacles
Most of the cost is people and time rather than licenses. NIST attributes long transitions to the complexity of building algorithms into products, procuring those products and integrating them into existing infrastructure. Expect effort in a few areas.
- Discovery: finding cryptography hidden in legacy code, appliances and third-party components.
- Legacy hardware: devices, smart cards and security modules that cannot be updated and must be replaced.
- Vendor dependency: waiting on suppliers whose products sit in your critical paths.
- Performance testing: checking that larger keys and signatures do not break protocols or slow constrained devices.
- Skills: training engineers in new algorithms, hybrid modes and safe library choices.
We have not given price ranges because migration cost depends almost entirely on how many systems you run, how old they are and how much of the work your vendors handle. The inventory phase is what turns this into a real budget, so treat any figure quoted before that point as a rough guess.
Post-quantum readiness also belongs in your wider security roadmap. Our overview of cybersecurity trends for 2027 shows how it fits alongside identity, supply chain and AI-related risks.
Preparing for the quantum transition, one step at a time
Post quantum cryptography is not a crisis to solve overnight, but it is no longer a topic to postpone. The standards exist, official deadlines are set, and data with a long confidentiality life is already exposed to harvest now, decrypt later collection. Start with ownership and an inventory, prioritize long-lived data and public traffic, take the quick wins in TLS and libraries, and build crypto agility into every new system. If you need help reviewing your applications, updating backends or designing software that can change algorithms without a rewrite, Brahmabyte Lab's engineers can help. Book a free consultation and we will help you plan a practical first phase.
Frequently asked questions
Post quantum cryptography is a set of public-key algorithms designed to resist attacks from both classical and future quantum computers. They run on today's ordinary hardware and software. NIST has standardized the first of them as FIPS 203, 204 and 205.
No publicly known quantum computer can break today's encryption yet. The current risk comes from attackers recording encrypted data now and decrypting it later, which matters if your data must stay confidential for many years. Long migration times are the other reason to start early.
Generally no. NIST states that its approved symmetric algorithms are significantly less vulnerable to known quantum attacks than public-key algorithms, and those with at least 128 bits of classical security are believed to meet its post-quantum requirements. The priority is replacing RSA and elliptic curve algorithms used for key exchange and signatures.
Hybrid key exchange combines a classical algorithm, such as X25519, with a post-quantum one, such as ML-KEM, so the connection stays secure as long as either algorithm holds. It is a common transition approach, and OpenSSL 3.5 offers the X25519MLKEM768 hybrid group by default.
It depends on the size and age of your systems. NIST notes that past moves from standardizing an algorithm to full integration have taken 10 to 20 years, and the UK NCSC sets 2035 as the target for completing migration. Most organizations will migrate in phases over several years.
Start by listing the systems that use encryption, the data they protect and the vendors behind them. Ask your cloud, VPN and software vendors for their post-quantum roadmaps, keep libraries updated, and make sure any custom software you build can change algorithms through configuration.
Sources and references
- NIST Releases First 3 Finalized Post-Quantum Encryption Standards, NIST
- NIST IR 8547: Transition to Post-Quantum Cryptography Standards (final), NIST
- Timelines for migration to post-quantum cryptography, UK National Cyber Security Centre
- NIST Selects HQC as Fifth Algorithm for Post-Quantum Encryption, NIST
Cover photo by Sasun Bughdaryan
Stay in the loop
Get our latest guides on software, SaaS and growth delivered to your inbox.
By subscribing, you agree to get updates from Brahmabyte Lab. You can unsubscribe any time.


