“Quantum-safe” can describe technologies with very different architectures, constraints, and deployment models. In an October 1 resource, the National Security Agency explains why quantum key distribution and quantum cryptography remain limited compared with post-quantum algorithms. NSA states that, as of June 2026, it does not recommend QKD or quantum cryptography for protecting National Security Systems unless specified technical limitations are overcome.
The scope matters. This is an NSA position for National Security Systems, not a universal prohibition on quantum communications research or every commercial use. It is also not a claim that software-based PQC solves every migration problem. The operational lesson is that QKD, quantum cryptography, and post-quantum cryptography are not interchangeable line items.
Different technologies create different dependencies
PQC uses mathematical algorithms that can run on conventional computing platforms. QKD uses quantum-mechanical properties and specialized communications arrangements to establish keying material. That difference affects topology, equipment, operations, procurement, and failure modes.
A technology decision record should identify:
- the security objective—confidentiality, authentication, integrity, or key distribution;
- the protected data, service, endpoints, and accountable owner;
- required hardware, links, trusted nodes, and physical constraints;
- classical authentication and key-management dependencies;
- availability, denial-of-service, monitoring, and recovery requirements;
- supplier, interoperability, validation, and lifecycle status;
- the alternative conventional or PQC design evaluated; and
- test scope, limitations, residual risks, and approval evidence.
This prevents a broad label from hiding the architecture actually being approved.
Key distribution does not replace authentication
Secure key establishment still requires confidence in the identities and integrity of the participating systems. A specialized key-distribution link can depend on classical cryptography, trusted hardware, management systems, and operational procedures outside the quantum channel.
Inventory should connect those dependencies rather than treating the quantum component as a self-contained control. If an authentication certificate, device identity, software-update signature, or management session remains classically protected, that state should be explicit.
The same principle applies to PQC deployments: hybrid key establishment does not automatically migrate signatures or certificate hierarchies. Accurate reporting separates cryptographic roles.
Availability belongs in cryptographic evaluation
A security design can protect confidentiality while introducing fragile operational dependencies. Dedicated links, distance constraints, specialized components, environmental effects, or limited supplier options may affect availability and recoverability. Those characteristics must be evaluated alongside the cryptographic claim.
Teams should test failure behavior, monitoring, failover, maintenance, and incident response. If a system falls back to another key-establishment method when the preferred path fails, the fallback must be inventoried and governed. A diagram showing the ideal path is not proof of the degraded state.
Procurement language must name the boundary
Requests for “quantum-safe encryption” invite incomparable responses. Procurement should state the use case, required cryptographic role, approved standards, deployment environment, interoperability population, evidence requirements, and lifecycle expectations.
Suppliers should identify which part of the system their claim covers, which algorithms or physical mechanisms are used, which external components remain necessary, and which validations or tests support the claim. Roadmap features should remain labeled as future work rather than current capability.
PQC still requires engineering and proof
NSA’s preference for quantum-resistant algorithms does not reduce PQC migration to a software toggle. Organizations still need to discover cryptography, map dependencies, test protocols and implementations, coordinate relying parties, change keys and certificates, observe production behavior, and retain evidence.
Some systems may not support suitable algorithms within their resource or lifecycle constraints. Others may require hybrid operation during transition. The appropriate design depends on the system, policy, data lifetime, and supported ecosystem.
What organizations should do next
First, remove “quantum safe” as an unqualified inventory value. Record the exact technology, cryptographic role, implementation, and boundary.
Second, compare proposed QKD or quantum-cryptography deployments with standards-based PQC alternatives using the same security, availability, lifecycle, and evidence criteria.
Third, map classical authentication, management, and fallback dependencies. Do not claim end-to-end readiness from one protected link.
Fourth, require realistic failure and recovery testing, including degraded paths and supplier support.
Finally, retain the decision rationale and re-evaluate it as standards, implementations, and operational evidence mature.
How Vista Platform helps
Vista Platform is a self-hosted cryptographic system of record. Its operating loop—discovery, canonical inventory, evaluation, action, and proof—helps teams connect cryptographic technologies to assets, relationships, owners, decisions, exceptions, remediation, and evidence.
Vista Platform Core is free of charge and includes discovery, inventory, compliance and PQC assessment, and CBOM generation without asset, sensor, seat, or time caps. Vista tracks and governs post-quantum migration; it does not generate PQC keys or perform every migration. Selected-asset Active Scan is targeted, not indiscriminate network scanning. Vista is not a vulnerability scanner, and incomplete observation is not proof of absence.
Learn more about Vista’s post-quantum migration and cryptographic inventory approach.
Where uncertainty remains
NSA’s resource reflects its mission, risk tolerance, and National Security Systems scope. Other organizations may evaluate specialized deployments differently, and future research may address current limitations. The lasting governance point is that technology labels do not establish suitability. Architecture, dependencies, operations, and proof do.
Source
- Quantum Cryptographic Solutions Are Limited Compared to Post-Quantum Algorithms, National Security Agency, October 1, 2026.