TL;DR
Quantum-vulnerable cryptography does not carry the same level of risk across every system. Migration priority depends on factors such as the sensitivity and lifetime of protected data, system criticality, exposure, dependencies, and the time and complexity involved in migration. Understanding these factors helps organizations determine where PQC migration should begin.
What Is Cryptographic Risk in a PQC Migration?
PQC migration starts with identifying where quantum-vulnerable public-key cryptography, including RSA and elliptic-curve cryptography, is being used.
That inventory provides technical visibility, but migration planning also requires context. Organizations need to understand what the cryptography protects, the role of the affected system, and the consequences if that protection becomes vulnerable.
NIST's National Cybersecurity Center of Excellence (NCCoE) treats cryptographic discovery and inventory as inputs to risk management and PQC migration planning. Its Migration to Post-Quantum Cryptography project includes capabilities for identifying cryptographic assets and using that information to support risk assessment and prioritization.
Two systems can therefore use the same quantum-vulnerable algorithm while requiring different migration priorities. The difference comes from the environment in which that cryptography is used.
What Factors Affect PQC Migration Risk?
There is currently no single risk-scoring methodology that applies to every organization. However, government and industry migration guidance identifies several factors that can be used to evaluate risk and set migration priorities.
1. Data Sensitivity and Lifetime
The first consideration is what the cryptography protects and how long that information needs to remain secure.
Long-lived sensitive information is particularly relevant to PQC because of Harvest Now, Decrypt Later (HNDL). An adversary can collect encrypted information today and retain it for possible decryption when a cryptographically relevant quantum computer becomes available.
NIST recommends identifying sensitive and critical datasets protected by quantum-vulnerable cryptography and considering how long that information must remain protected. The PQC Coalition's migration roadmap also includes asset sensitivity and lifespan when determining migration priorities.
Data that must remain confidential for 10 or 20 years may therefore require earlier action than information with a much shorter useful life.
2. System Criticality and Business Impact
The role of the affected system also matters.
Cryptography can protect authentication systems, financial transactions, critical infrastructure, healthcare records, government information, internal applications, and many other functions. The potential impact of cryptographic compromise varies considerably between them.
Current U.S. federal policy provides a clear example of this approach. OMB Memorandum M-26-15 requires federal agencies to use risk-based prioritization for PQC migration, with particular attention to High Impact systems, High Value Assets, highly sensitive data, and systems supporting critical functions.
These requirements apply specifically to U.S. federal agencies, but they illustrate how system impact can be incorporated into PQC migration planning.
3. Exposure
Exposure adds another layer to the assessment.
A cryptographic asset used within a tightly controlled environment can have a different exposure profile from one protecting externally accessible services or information.
U.S. government quantum-readiness guidance recommends identifying outside access to datasets when evaluating quantum-vulnerable cryptography. This helps connect technical cryptographic findings with the actual environment in which the data and systems operate.
Therefore, when conducting risk assessments, enterprises need not only to know what cryptography is used, but also to understand where this cryptography is deployed and how the related systems and data are accessed.
4. System and Supplier Dependencies
PQC migration also depends on the systems surrounding the affected cryptography.
An application may rely on cryptographic libraries, PKI, hardware security modules, operating systems, cloud services, third-party software, or vendor-managed infrastructure.
Changes to one component can therefore depend on PQC support becoming available elsewhere.
NCSC migration guidance recommends identifying dependencies on suppliers and physical infrastructure during planning. It also highlights long-lived hardware and legacy systems because these dependencies can affect how and when migration is possible.
Mapping these relationships is important when setting priorities because the migration of one system may depend on several others.
5. Migration Complexity and Time
Migration priority also needs to account for how difficult a system will be to change.
Some cryptographic components may be updated through software or configuration changes. Others may depend on legacy applications, hardware refresh cycles, vendor updates, certification requirements, or infrastructure that cannot be changed quickly.
NCSC recommends considering both the impact of a potential breach and the time required to migrate when determining priorities. The PQC Coalition roadmap similarly includes migration time, urgency, asset sensitivity, and available mitigation strategies in its prioritization process.
A system that will take several years to migrate may need planning to begin earlier, even when the actual technical transition will occur later.
Why Migration Time Matters
PQC migration is expected to be a multi-year program for many organizations.
NCSC's current timeline calls for organizations to complete discovery and assessment and develop an initial migration plan by 2028. Its target for completing the highest-priority migration activities is 2031, followed by broader migration completion by 2035.
Large environments may need to coordinate software changes, hardware replacement, procurement, testing, vendors, and operational requirements. Legacy environments can introduce additional constraints.
Research published in 2026 on PQC migration in legacy systems identifies issues including hard-coded cryptographic functions, outdated programming languages, hardware limitations, vendor lock-in, interoperability constraints, and certification requirements. The paper is a research preprint rather than formal migration guidance, but it provides useful examples of why migration complexity can differ significantly between systems.
Migration planning therefore needs to consider both risk and remediation time. Systems with high impact and long migration lead times may require attention early in the program.
From Risk Assessment to Migration Priority
Cryptographic discovery establishes where cryptography is being used and identifies quantum-vulnerable algorithms, certificates, keys, protocols, applications, and dependencies.
Risk assessment adds the information required to prioritize those findings:
| Cryptographic visibility | Risk context |
| Algorithms and Key Types | Data sensitivity and lifetime |
| Certificate or cryptographic asset | System criticality |
| Application or service | Exposure |
| Host or infrastructure | Dependencies |
| Cryptographic vulnerability | Migration complexity and time |
Organizations can then group and prioritize migration activities according to their own risk-management requirements rather than treating every quantum-vulnerable asset as having the same urgency.
For CeQureX (CQX), this is where cryptographic discovery connects to migration planning. Wave-Key provides cryptographic discovery, inventory, and assessment capabilities that help organizations build the visibility required to evaluate exposure and determine migration priorities.
Discover → Assess → Prioritize → Migrate
Frequently Asked Questions (FAQ)
What is a PQC risk assessment?
A PQC risk assessment evaluates the use of quantum-vulnerable cryptography together with the business and operational context surrounding it. Depending on the organization's risk framework, this can include data sensitivity and lifetime, system impact, exposure, dependencies, and migration requirements.
How to prioritize the PQC migration?
Organizations can prioritize PQC migration by combining cryptographic inventory data with risk information. Current guidance considers factors such as sensitive or long-lived data, critical systems, dependencies, exposure, and the time required to migrate. The specific weighting of these factors depends on the organization's risk-management framework and requirements.
What systems should migrate to PQC first?
There is no universal list that applies to every organization. NCSC recommends giving priority to systems where a breach would have the greatest impact and systems that require significant time to migrate. Sector-specific or government requirements may establish additional priorities.
What is quantum cryptographic risk?
Quantum cryptographic risk is the risk created when cryptographic mechanisms used to protect data, communications, authentication, or digital signatures may become vulnerable to quantum computing. For PQC planning, the level of risk also depends on where the cryptography is used and what it protects.
Why does data lifetime matter for PQC?
Sensitive information may need to remain confidential for many years. HNDL attacks allow an adversary to collect encrypted information today for possible decryption in the future. Data with a long confidentiality requirement can therefore require action before a cryptographically relevant quantum computer exists.
What is Harvest Now, Decrypt Later?
Harvest Now, Decrypt Later is an attack strategy in which encrypted information is collected and stored even though the attacker cannot currently decrypt it. The attacker retains the information in anticipation of future capabilities, including quantum computers capable of breaking vulnerable public-key cryptography.
Is a cryptographic inventory enough for PQC migration?
A cryptographic inventory is the foundation for PQC migration because it identifies where cryptography is used. Migration planning also requires context about the affected data and systems so organizations can assess risk, establish priorities, understand dependencies, and plan remediation.
References
- Chammas, P., et al. Towards a Field-Informed Risk-Based Framework for PQC Migration in Legacy Systems. IACR Cryptology ePrint Archive, 2026/790.
https://eprint.iacr.org/2026/790.pdf - National Institute of Standards and Technology (NIST), National Cybersecurity Center of Excellence (NCCoE). Migration to Post-Quantum Cryptography. https://www.nccoe.nist.gov/applied-cryptography/migration-to-pqc
- Cybersecurity and Infrastructure Security Agency (CISA), National Security Agency (NSA), and NIST. Quantum-Readiness: Migration to Post-Quantum Cryptography. 2023. https://www.cisa.gov/sites/default/files/2023-08/Quantum-Readiness%20-%20Migration%20to%20Post-Quantum%20Cryptography_508c.pdf
- Office of Management and Budget (OMB). M-26-15: Execution of the Migration to Post-Quantum Cryptography. June 2026. https://www.whitehouse.gov/wp-content/uploads/2026/06/M-26-15-Execution-of-the-Migration-to-Post-Quantum-Cryptography.pdf
- Post-Quantum Cryptography Coalition (PQCC). PQC Migration Roadmap. 2025. https://pqcc.org/wp-content/uploads/2025/05/PQC-Migration-Roadmap-PQCC-2.pdf
- UK National Cyber Security Centre (NCSC). Timelines for Migration to Post-Quantum Cryptography. https://www.ncsc.gov.uk/guidance/pqc-migration-timelines
- UK National Cyber Security Centre (NCSC). Post-Quantum Cryptography Migration Workshop Report. https://www.ncsc.gov.uk/blogs/post-quantum-cryptography-pqc-migration-workshop-report