Skip to main content
Hero background

Post-Quantum Migration

Post-quantum migration is the process of transitioning systems, applications, and infrastructure from traditional public-key cryptography to post-quantum cryptography (PQC). The objective is to protect sensitive information and trusted communications before quantum computing advances to the point where current encryption no longer holds. 

For government agencies, defense organizations, and critical infrastructure operators, this is not simply an algorithmic upgrade. Teams must first map where cryptography supports communications, authentication, certificates, software updates, devices, and operational systems. Only then can migration be properly sequenced and prioritized against real operational constraints. 

The harvest-now, decrypt-later threat adds a dimension of urgency that does not depend on quantum computing, reaching operational maturity. Adversaries can capture and retain encrypted information today with the intent to decrypt it once sufficient quantum capability becomes available. Any information that must remain confidential for years or decades is exposed to that risk under current conditions. Migration timelines should reflect that reality. 

In 2024, NIST finalized three primary PQC standards: 

Starting early gives organizations the time needed to map cryptographic dependencies, assess risk, evaluate vendor readiness, test PQC technologies, and plan upgrades without disrupting essential operations. Migration priorities will vary, shaped by the sensitivity and lifespan of protected information, existing infrastructure, technology lifecycles, and operational requirements. 

Latest Post-Quantum Migration News

Why It’s Important to Prepare for Post-Quantum Now

Long-Term Security and Operational Risk 

RSA and elliptic-curve cryptography, two of the most widely deployed public-key algorithms, rely on mathematical problems that a sufficiently capable quantum computer could solve efficiently using Shor's algorithm. That creates a verifiable long-term security risk for any information that must remain protected for years or decades. 

The threat does not require quantum computing to be operational today. Adversaries can capture encrypted data now and retain it for future decryption, even when current systems are not yet capable of breaking widely used public-key encryption. Collection may already be underway. The risk is present, not projected. 

Sensitive information may include: 

  • Government communications and records 

  • Healthcare and financial information 

  • Intellectual property 

  • Operational and infrastructure data 

  • Communications between agencies, contractors, and partners 

  • Software and firmware signing information 

Regulatory Direction and Technology Readiness 

Post-quantum readiness is now a stated priority across government agencies and cybersecurity authorities. Guidance from NIST, CISA, and NSA identifies cryptographic discovery, risk assessment, vendor coordination, and structured migration planning as foundational requirements, not aspirational targets. For U.S. federal agencies, recent policies have increased the focus on post-quantum protection for sensitive systems and high-value assets. Organizations in other sectors face comparable pressure to assess their cryptographic exposure and prepare requirements that continue to evolve. 

Preparation can include: 

  • Building a cryptographic inventory 

  • Identifying systems that require long-term protection 

  • Prioritizing high-risk and hard-to-replace technologies 

  • Evaluating vendor and product readiness 

  • Establishing migration timelines 

  • Building cryptographic agility into new systems 

  • Testing PQC implementations before production deployment

Post-Quantum Migration Key Elements

Cryptographic Discovery and Inventory 

Migration cannot be responsibly planned against what teams cannot see. Modern environments embed cryptographic algorithms, certificates, keys, and libraries across applications, devices, networks, databases, operational technology, cloud services, and third-party products. Without an accurate inventory, there is no reliable basis for assessing quantum-related exposure or setting up migration priorities. 

A cryptographic inventory should capture: 

  • Algorithms, certificates, keys, and cryptographic libraries 

  • Dependencies across applications and infrastructure 

  • Embedded or hard-coded cryptography 

  • Operational technology and connected devices 

  • Third-party and vendor dependencies 

  • Product support and upgrade timelines 

That inventory is the foundation for every subsequent migration decision. Teams that attempt risk assessment without it are working from assumptions rather than evidence. 

Risk Assessment and Prioritization 

A risk-based approach helps organizations determine where to focus migration efforts first. Systems that protect highly sensitive information, support essential operations, or remain in service for decades may require earlier attention than lower-risk environments. 

Teams can assess systems based on: 

  • Sensitivity and lifespan of protected information 

  • Mission or business importance 

  • External exposure and attack surface 

  • Technical and cryptographic dependencies 

  • Difficulty of replacing or updating systems 

  • Potential impact of a future cryptographic failure 

Systems protecting highly sensitive information, sustaining essential operations, or remaining in service for decades are the priority. Lower-risk environments follow. Establishing that order early prevents migration programs from being sequenced around technical convenience rather than operational necessity. 

Hybrid Architecture and Cryptographic Agility 

Post-quantum migration does not require immediate departure from classical cryptography. Hybrid architectures combine classical and post-quantum mechanisms, allowing teams to validate interoperability, measure performance, and confirm operational readiness incrementally before committing a full transition. 

Hybrid key establishment illustrates the approach. Combining ML-KEM with an established classical mechanism introduces post-quantum protection while preserving compatibility with existing infrastructure. The same logic applies across the broader environment. 

Key considerations include: 

  • Supporting hybrid protocols across applications and networks 

  • Maintaining compatibility with existing systems 

  • Updating certificate and trust-management processes 

  • Removing hard-coded cryptographic dependencies 

  • Building algorithm flexibility into new technology deployments 

Cryptographic agility serves a longer-term purpose as well. NIST standards and approved algorithms will continue to develop after initial migrations are complete. Organizations that have built agility into their environments can absorb those changes through configuration updates rather than full-scale redesigns. 

Governance and Migration Planning 

Post-quantum migration cuts across security, infrastructure, applications, procurement, compliance, engineering, and operations. Without defined ownership and coordinated priorities, migration efforts fragment across teams and stall against competing demands. A clear governance framework establishes accountability, aligns priorities, and ensures progress is tracked and reported. 

A structured program should establish: 

  • Ownership of cryptographic assets 

  • Migration priorities and timelines 

  • PQC requirements for procurement 

  • Vendor capabilities and technology roadmaps 

  • Progress measures across systems and environments 

  • Processes for managing exceptions and operational risks 

For critical infrastructure, migration planning should also account for availability, safety, maintenance of windows, and long technology replacement cycles. 

Post-Quantum Migration Use Cases

Web, APIs, and Public Services 

Public-facing applications depend on TLS and digital certificates to protect communications between users, services, and infrastructure. Hybrid TLS provides a practical path toward post-quantum protection while organizations continue to support existing technologies through the transition. 

Migration considerations include: 

  • Enabling hybrid TLS across edge infrastructure 

  • Updating load balancers, gateways, proxies, and service meshes 

  • Testing browser, mobile, and client compatibility 

  • Monitoring connection performance and reliability 

  • Updating certificate and trust-management processes 

Identity, Access, and PKI 

Cryptographic trust underpins every identity function. PKI, certificates, secure email, SSH, VPNs, and related authentication infrastructure all carry dependencies that post-quantum migration must address directly. Deferring to this category carries compounding risk, because identity infrastructure failures affect access across the entire environment. 

Organizations can prepare by: 

  • Introducing PQC-ready certificate infrastructure 

  • Testing authentication workflows across platforms 

  • Aligning certificate lifecycles with migration plans 

  • Preparing systems for larger cryptographic artifacts 

  • Evaluating hybrid approaches where appropriate 

NIST is developing updates to PIV standards that address ML-KEM and ML-DSA, supporting planning for incremental PQC adoption in identity infrastructure. 

Software Supply Chain and Updates 

Digital signatures give organizations the means to verify the integrity and authenticity of software and firmware. Protecting those signing and verification processes is a core post-quantum readiness requirement, not a secondary one. A compromised signing infrastructure affects every system that depends on it. Migration scope should extend across software signing, build pipelines, verification tools, and distribution systems. 

Key activities include: 

  • Testing PQC signature mechanisms for software and firmware 

  • Updating build and signing pipelines 

  • Updating verification tools 

  • Testing signature size and performance 

  • Validating signing and verification workflows 

Data at Rest and Archival Protection 

Information that must remain confidential for years or decades represents direct harvest-now, decrypt-later exposure. Archival systems, long-retention records, and encrypted backups fall into this category and require specific attention in post-quantum planning. 

Organizations should evaluate: 

  • Which information requires long-term confidentiality 

  • How encryption keys are generated, stored, and backed up 

  • Whether future re-encryption may be necessary 

  • Storage requirements for larger cryptographic artifacts 

  • Retention periods and archival systems 

Prioritizing information with long confidentiality requirements addresses harvest-now, decrypt-later risk before the most sensitive holdings become harder to protect. 

IoT, OT, and Field-Deployable Systems 

Connected devices and operational technology often remain in service for years or decades. Many also have limited processing power, storage, update capabilities, or maintenance windows. 

Post-quantum planning should account for: 

  • Firmware signing and update mechanisms 

  • Device performance and storage limitations 

  • Hardware replacement cycles 

  • Secure update capabilities 

  • Gateways connecting modern and legacy environments 

Where devices cannot be updated directly, gateways connecting those environments to modern infrastructure become part of the migration scope. Hybrid approaches can introduce PQC protection while preserving compatibility with systems that cannot be immediately replaced. 

Roadmap for Post-Quantum Migration

Discover

Build a clear view of cryptography across applications, infrastructure, devices, networks, certificates, vendors, and operational environments.

Assess

Evaluate systems based on information sensitivity, protection lifespan, mission or business impact, technical dependencies, and migration complexity. Prioritize systems that face the greatest long-term risk.

Define the Migration Strategy

Select appropriate PQC standards and determine where hybrid approaches make sense. Establish migration priorities, technical requirements, ownership, and timelines.

Modernize Architecture

Remove hard-coded cryptographic dependencies, update PKI and certificate infrastructure, modernize key management, and prepare applications and protocols for cryptographic agility.

Test and Validate

Pilot PQC and hybrid implementations in controlled environments. Test interoperability, performance, certificate handling, device compatibility, and operational behavior before production deployment.

Deploy in Phases

Expand migration based on risk and readiness. Use controlled rollouts, maintenance windows, rollback procedures, and operational safeguards to minimize disruption.

Monitor and Adapt

Track compatibility, performance, vendor readiness, cryptographic configurations, and changes to standards and guidance. Use these insights to adjust migration priorities as technology and requirements evolve.

BlackBerry for Secure Communications

For Environments Where Failure Isn’t an Option

BlackBerry Secure Communications is the leading solution that delivers unmatched expertise to protect the world’s most critical communications.

Explore BlackBerry Secure Communications solutions

FAQ

Frequently asked questions about Post-Quantum Migration answered

Q: What is post-quantum migration?

A: Post-quantum migration is the process of moving systems, applications, and infrastructure from cryptography that may be vulnerable to quantum computers to post-quantum cryptography. It includes identifying where cryptography is used, assessing risk, prioritizing systems, testing new standards, and planning phased updates across the organization.

Q: Why should organizations start post-quantum migration now?

A: Organizations should start now because migration can take years, especially in environments with legacy systems, third-party dependencies, certificates, connected devices, and critical infrastructure. The harvest-now, decrypt-later threat also means sensitive data collected today could be decrypted in the future once quantum computing becomes capable enough.

Q: What systems should be prioritized during post-quantum migration?

A: Organizations should prioritize systems that protect sensitive or long-lived information, support essential operations, rely heavily on public-key cryptography, or are difficult to update. This may include identity systems, PKI, secure communications, software signing, archival data, connected devices, and operational technology.

Q: What does cryptographic agility mean in post-quantum migration?

A: Cryptographic agility is the ability to update or replace cryptographic algorithms without rebuilding the systems that depend on them. It matters because standards, algorithms, vendor support, and compliance requirements will continue to evolve, so organizations need systems that can adapt without requiring full redesigns.