Post-Quantum Cryptography in 2026: Why Businesses Should Start Migrating Now
Many organizations depend on public-key cryptography to establish secure connections, authenticate systems, protect digital signatures, and manage digital identities. These mechanisms work against today's known computing threats, but sufficiently capable quantum computers could undermine some of the mathematical assumptions behind widely used public-key algorithms.
The practical response is called post-quantum cryptography, or PQC. Rather than waiting for a future quantum computer to arrive, standards bodies and technology providers are developing and deploying cryptographic algorithms designed to resist attacks from both classical and quantum computers.
The issue is not that every encrypted message is suddenly unsafe. The challenge is that cryptographic migration can take years, involves products from many vendors, and may affect systems that organizations cannot easily update. Data collected today may also remain sensitive long enough to create a future risk if an adversary can store it and decrypt it later.
What Is Post-Quantum Cryptography?
Post-quantum cryptography uses algorithms intended to remain secure against attacks from conventional computers and sufficiently capable quantum computers. The algorithms are designed to run on ordinary computing infrastructure; organizations do not need a quantum computer to implement them.
This is different from quantum cryptography, which uses quantum-mechanical phenomena as part of a communication or security technique. PQC is primarily a change to the mathematical algorithms used in existing digital systems.
The distinction matters because most organizations will approach PQC as a software, protocol, hardware, and vendor-migration project. It is not simply a matter of buying a quantum device or switching on a new security feature.
Why Quantum Computing Changes the Security Equation
Modern public-key cryptography relies on mathematical problems that are difficult for classical computers to solve at the sizes used by secure systems. Algorithms such as RSA and elliptic-curve cryptography are used in different ways across authentication, digital signatures, key establishment, and secure communications.
A sufficiently capable cryptographically relevant quantum computer could use quantum algorithms to attack the mathematical problems that protect some of these public-key systems. That possibility creates a long-term concern for data and infrastructure that must remain secure for many years.
It is important to distinguish the potential threat from current capabilities. The fact that quantum computers are advancing does not mean that a practical machine capable of breaking widely deployed cryptography is already available to every attacker. The reason to plan now is that migration itself is a lengthy process, not proof that the threat has already materialized at scale.
The “Harvest Now, Decrypt Later” Risk
One concern is often described as “harvest now, decrypt later.” An adversary may collect encrypted information today and store it in the hope of decrypting it in the future when more capable technology becomes available.
This threat is especially relevant when the information has a long confidentiality lifetime. Examples could include sensitive government records, long-term commercial secrets, confidential research, or information that would still cause harm if disclosed years after collection.
Not every encrypted file has the same exposure. Risk depends on the type of cryptography used, the information's sensitivity, how long it needs protection, whether an attacker can obtain the ciphertext, and how feasible future decryption would be.
Organizations should therefore prioritize migration based on both technical vulnerability and the value of the information being protected. Waiting until a quantum computer is publicly demonstrated to break a target system could leave too little time to update complex infrastructure.
The First Three NIST Post-Quantum Standards
In August 2024, the US National Institute of Standards and Technology finalized three post-quantum cryptography standards. These standards provide an important foundation for implementation and interoperability.
ML-KEM: Establishing shared secrets
FIPS 203 specifies the Module-Lattice-Based Key-Encapsulation Mechanism, known as ML-KEM. A key-encapsulation mechanism helps two parties establish a shared secret that can then be used with symmetric cryptography to protect their communication.
ML-KEM is not simply a replacement name for a complete data-encryption system. It serves a particular role in the broader process of establishing cryptographic keys. Secure implementation still depends on the surrounding protocol, key handling, and system configuration.
ML-DSA: Digital signatures
FIPS 204 specifies the Module-Lattice-Based Digital Signature Algorithm, or ML-DSA. Digital signatures help establish that a message or software artifact was signed by the holder of a particular private key and has not been altered since signing.
Signatures are important beyond user login. They can be used for software updates, certificates, document authenticity, and other mechanisms that depend on verifying who signed something and whether it has changed.
SLH-DSA: Hash-based digital signatures
FIPS 205 specifies the Stateless Hash-Based Digital Signature Algorithm, or SLH-DSA. It provides another standardized approach to post-quantum digital signatures, based on hash functions rather than the same mathematical foundation used by ML-DSA.
The availability of multiple standards gives implementers options, but it does not mean that every system should independently select an algorithm without guidance. Organizations should follow the requirements of the relevant protocol, product, sector, and security authority.
Why Migration Is More Complicated Than Replacing One Algorithm
Cryptography is often embedded in software libraries, network protocols, operating systems, identity services, hardware, appliances, and vendor products. Some dependencies are visible to an organization's security team; others are buried inside a third-party service or a device that has not been updated for years.
For example, a company might use a secure web connection, a virtual private network, a public-key infrastructure, code-signing certificates, device authentication, and encrypted backups. These systems can rely on different algorithms and update mechanisms.
Changing one component may create compatibility problems with another. A new key-establishment method may require protocol support at both ends of a connection. A new signature algorithm may require changes to certificate formats, validation software, hardware security modules, or software distribution systems.
Cryptographic migration is therefore an ecosystem project. It requires coordination among system owners, application developers, network teams, security providers, procurement staff, and vendors.
The First Step Is a Cryptographic Inventory
Organizations cannot migrate systems they do not know they use. The first practical task is to discover where cryptography is deployed, which algorithms are involved, and which systems depend on them.
An inventory should go beyond a list of security products. It should identify the cryptographic functions used by applications and infrastructure, the business owners responsible for them, the vendors that supply them, and the systems that depend on their continued operation.
Useful areas to investigate include:
- TLS and other secure communication protocols.
- Virtual private networks and remote-access systems.
- Certificates, certificate authorities, and public-key infrastructure.
- Code signing and software or firmware update mechanisms.
- Identity systems, authentication services, and device credentials.
- Hardware security modules and cryptographic appliances.
- Cloud services and managed security products.
- Operational technology, embedded devices, and long-lived equipment.
- Third-party applications and supply-chain components.
Automated discovery tools can help identify cryptographic usage, but no single tool should be assumed to find everything. Vendor documentation, application testing, architecture reviews, and procurement records can reveal dependencies that automated scans miss.
Prioritizing Which Systems to Migrate First
A large organization may have thousands of systems that use cryptography. Replacing everything at once is usually unrealistic. Prioritization should consider the sensitivity of the protected data, the expected lifetime of that data, the exposure of the system, the availability of PQC support, and the time needed to update the relevant technology.
Prioritize long-lived sensitive information
Information that must remain confidential for many years deserves particular attention. If the data could be collected now and remain valuable after future cryptographic advances, the organization should assess whether its current protection relies on vulnerable public-key mechanisms.
Prioritize difficult-to-update systems
Embedded equipment, industrial devices, and specialized appliances may remain in service for a long time. If their firmware or cryptographic components cannot be updated easily, migration may require procurement changes, vendor cooperation, or planned replacement.
Prioritize critical dependencies
Systems that support many applications can become migration bottlenecks. Identity infrastructure, certificate services, secure communications, and shared cryptographic libraries should be assessed carefully because a change in one component may affect numerous downstream systems.
What the 2026 Policy Developments Mean
NIST continues to encourage organizations to begin migrating to its finalized PQC standards. Its post-quantum cryptography materials describe a transition away from quantum-vulnerable algorithms, with a plan to deprecate and ultimately remove such algorithms from relevant NIST standards by 2035, while high-risk systems transition earlier.
The 2035 date should not be interpreted as a universal deadline that automatically applies to every business in every country. It is part of a standards-transition framework, and different organizations may be subject to different regulatory, contractual, and sector-specific requirements.
In June 2026, the United States issued an executive order focused on accelerating the migration of federal information systems to NIST-approved post-quantum standards. The accompanying policy materials describe designated responsibilities and earlier milestones for certain high-value assets. These are US federal measures; they do not automatically establish the legal obligations of every private organization worldwide.
Nevertheless, developments in government standards and procurement can influence vendors, contractors, critical infrastructure operators, and organizations that depend on government-related services. Businesses should monitor the requirements relevant to their jurisdictions and customer contracts.
How to Build a Practical Migration Plan
1. Establish ownership
Assign responsibility for cryptographic discovery and migration. The effort may involve security, infrastructure, application development, procurement, legal, and business teams. Without a clear owner, findings can remain scattered across departments without turning into a coordinated plan.
2. Discover and document dependencies
Inventory cryptographic algorithms, protocols, libraries, certificates, hardware, and third-party products. Record which systems depend on each component and how difficult it would be to replace or update it.
3. Assess risk and prioritize
Rank systems based on data sensitivity, exposure, business importance, update difficulty, and vendor readiness. Prioritize systems that protect information with a long confidentiality lifetime or that would be difficult to replace quickly.
4. Check product and vendor roadmaps
Ask vendors whether their products support the relevant NIST standards, which versions provide that support, and whether it is available in production or only in a development release. Request migration guidance, compatibility information, and a clear statement of any remaining limitations.
Do not assume that a general claim of “quantum readiness” means that every cryptographic feature in a product has been updated. Confirm the specific algorithms and functions covered.
5. Test interoperability
Run controlled tests with the applications and services that must communicate. Check performance, certificate handling, protocol compatibility, error recovery, logging, monitoring, and the ability to roll back safely when a migration step fails.
Cryptographic changes can affect network traffic sizes, handshake behavior, storage, and processing requirements. The magnitude of these effects depends on the algorithms and protocols used, so measurements should come from the actual environment.
6. Plan for crypto agility
Crypto agility is the ability to change cryptographic algorithms and configurations without rebuilding every dependent system from scratch. It can make future transitions easier by reducing hard-coded assumptions and clarifying where cryptographic choices are managed.
Agility is not permission to create a custom cryptographic design. Organizations should use established standards and vetted implementations, with qualified review of any proposed architecture changes.
7. Update procurement and contracts
New systems should be evaluated for their ability to support relevant post-quantum standards and future updates. Contracts can require vendors to disclose cryptographic dependencies, communicate support timelines, and provide migration assistance when necessary.
Procurement is important because a company may be unable to modify the cryptographic implementation of a closed product directly. If support is absent, the available options may include a vendor upgrade, an alternative product, an architectural change, or eventual replacement.
Performance, Compatibility, and Operational Risks
Post-quantum algorithms can differ from older public-key algorithms in key sizes, signature sizes, computational requirements, and protocol behavior. The operational effect depends on the specific algorithm, implementation, and use case.
Organizations should test systems that are sensitive to network overhead, latency, memory use, storage constraints, or hardware limitations. A change that works well in a modern web service may require additional testing in a constrained embedded device or a legacy network appliance.
Compatibility must be evaluated across the entire communication path. If one endpoint supports a new mechanism but another does not, the system may need a carefully planned transition approach. Any temporary hybrid design should follow authoritative guidance rather than being assembled from improvised cryptographic components.
Logging and monitoring should also be updated so that teams can distinguish migration failures from ordinary operational problems. A rollout plan should define success criteria, test coverage, rollback conditions, and responsibility for resolving compatibility issues.
What Individuals and Small Businesses Should Do
Individuals generally do not need to choose cryptographic algorithms manually. The more useful steps are to keep operating systems, browsers, devices, and applications updated, and to choose reputable services that maintain their security infrastructure.
Small businesses can ask cloud providers, software vendors, managed service providers, and security suppliers about their PQC plans. The key questions are whether the product relies on public-key cryptography, whether the vendor supports relevant standards, and how the vendor plans to maintain compatibility during migration.
Organizations that operate their own applications or networks should begin with an inventory and risk assessment rather than purchasing a product solely because it is marketed as quantum-resistant. A solution's value depends on whether it protects the actual system and fits its technical and regulatory requirements.
Frequently Asked Questions
Does post-quantum cryptography require a quantum computer?
No. Post-quantum cryptographic algorithms are designed to run on conventional computing systems while resisting attacks from sufficiently capable classical and quantum computers.
Will quantum computers immediately break all encryption?
No. The threat differs by cryptographic algorithm and use case. The primary concern is that sufficiently capable quantum computers could undermine certain widely used public-key mechanisms. Organizations should follow current standards guidance rather than assuming every form of encryption is equally affected.
What are the three finalized NIST PQC standards?
NIST finalized FIPS 203 for ML-KEM, FIPS 204 for ML-DSA, and FIPS 205 for SLH-DSA in August 2024. They address key establishment and digital signatures in different ways.
Why should businesses start migrating before quantum computers become a practical threat?
Discovery, procurement, testing, software updates, and coordination with vendors can take years. Sensitive information collected today may also remain valuable in the future, making early risk assessment important.
Does the 2035 timeline apply to every business?
No. The timeline described by NIST is part of its standards-transition planning. Legal, contractual, and sector-specific requirements may differ, so organizations should check the rules that apply to their systems and jurisdictions.
Conclusion
Post-quantum cryptography is a long-term infrastructure transition, not a single software update. The first three NIST standards provide a foundation for implementation, but organizations still need to discover their cryptographic dependencies, prioritize vulnerable systems, work with vendors, and test compatibility.
The most useful first step is to establish an accurate inventory and a risk-based migration plan. Organizations that wait until a quantum threat becomes urgent may discover that their most difficult systems are also the least prepared to change. Starting early gives them time to test solutions, update procurement requirements, and protect sensitive information through a controlled transition.
Sources
- NIST — Post-Quantum Cryptography Standards and Migration
- NIST Computer Security Resource Center — Post-Quantum Cryptography Project
- NIST NCCoE — Migration to Post-Quantum Cryptography
- CISA — Quantum Readiness: Migration to Post-Quantum Cryptography
- The White House — 2026 Policy on Accelerating Post-Quantum Cryptography Migration
