The National Security Agency has put two near-term markers on the post-quantum transition for National Security Systems. In its October 1 announcement, NSA says that starting in 2027, all new commercial NSS must be capable of supporting quantum-resistant algorithms, while legacy systems that cannot support them are to be phased out by 2030.
The announcement applies to a specialized national-security context, not every commercial system. It also points to further resources rather than spelling out a complete acceptance test. Yet the word “capable” creates an immediate operational question for government buyers, the Defense Industrial Base, and suppliers: what evidence proves a product can support approved PQC in the environment where it will actually operate?
Installed code is not deployable capability
A product may contain an ML-KEM or ML-DSA implementation and still be unready for use. The capability may be disabled, available only in a future firmware branch, incompatible with required peers, excluded from the validated configuration, or too resource-intensive for the target hardware. Key management, certificates, protocol negotiation, logging, recovery, and upgrade procedures may remain classical.
Procurement therefore needs a stronger test than a “PQC supported” checkbox. Evidence should identify the exact product and version, standardized algorithm and parameter set, protocol profile, hardware and software prerequisites, supported operating mode, validation status, and interoperable peers. It should distinguish a shipping capability from an experimental build, preview, or roadmap promise.
The distinction is especially important for National Security Systems, where lifecycle and integration lead times are long. Buying a nominally capable component that cannot participate in the required end-to-end path simply moves the migration problem into the installed base.
Capability belongs to a system relationship
Cryptography does not operate in isolation. A VPN gateway needs compatible peers and policy. A signing service needs verifiers that understand its signatures. A device needs a secure way to receive trust anchors and updates. A cryptographic module needs applications that invoke it correctly.
For each proposed acquisition, teams should map:
- the security purpose: confidentiality, authentication, signing, key establishment, or another function;
- the quantum-vulnerable mechanism being replaced or supplemented;
- the PQC or hybrid mechanism, specification, and implementation version;
- the peers, roots of trust, libraries, modules, and management systems required;
- performance, message-size, storage, and availability constraints;
- the approved fallback and rollback behavior;
- evidence from interoperability and operational testing; and
- the accountable owner and date by which the capability will be enabled.
This relationship model prevents a component claim from being mistaken for system readiness. It also makes exceptions visible when one dependency prevents an otherwise capable product from using PQC.
The 2030 phase-out needs a retirement inventory now
NSA’s second marker concerns legacy systems that cannot support quantum-resilient algorithms. Phase-out planning cannot begin in 2029. Organizations need to identify those systems, determine why they are incapable, and decide whether to upgrade, isolate, replace, or retire them.
That inventory should include embedded equipment, appliances, operational technology, hard-coded certificate formats, unsupported operating systems, fixed cryptographic accelerators, and vendor services with no customer-controlled crypto policy. It should also capture mission dependencies and replacement lead time. An obscure device can become the critical path if it anchors identity, controls access, or signs firmware for a larger fleet.
Discovery results must be treated as evidence with coverage boundaries. A scanner that finds no vulnerable algorithm on an inaccessible device has not proved absence. Procurement records, architecture diagrams, firmware analysis, supplier attestations, and observed protocol data may all contribute different parts of the picture.
What organizations should do next
First, translate “PQC capable” into testable acceptance criteria for each acquisition class. Require suppliers to name current versions and dependencies and to mark roadmap items explicitly. Tie payment or acceptance to reproducible evidence where appropriate.
Second, create a 2027 procurement gate. Security, architecture, acquisition, and mission owners should review whether a new system can support the required quantum-resistant mechanisms without an unplanned redesign. Preserve the decision and supporting evidence.
Third, establish a legacy exception register linked to a retirement plan. Record technical blockers, compensating controls, vendor commitments, funding, milestones, and the operational owner. Reassess exceptions when standards, products, or mission needs change.
Finally, keep confidentiality and authentication workstreams separate. NSA highlights both harvest-now, decrypt-later and “trust now, exploit later.” A system may protect key establishment with PQC while signatures, identities, or update chains remain quantum-vulnerable.
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 observed cryptography to systems, suppliers, owners, policies, exceptions, and remediation 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 rather than indiscriminate network scanning. Vista is not a vulnerability scanner, and discovery gaps are not proof that vulnerable cryptography is absent.
Vista’s post-quantum guidance provides additional migration context.
Where uncertainty remains
NSA’s announcement does not define every product-level test, exception, or implementation profile, and additional resources are expected. Organizations should confirm the controlling policies for their systems rather than treating this article as compliance advice. The durable takeaway is that acquisition claims must become verifiable system evidence—and incapable legacy systems need owned retirement plans well before 2030.
Source
- NSA Announces Post-Quantum Cryptography Measures to Safeguard National Security Systems Against Quantum Computing Threats, National Security Agency, October 1, 2026.