A Binding Regulatory Architecture
The United States federal government has constructed a layered, binding framework for post-quantum cryptographic migration over the past four years. This framework is not advisory guidance. It carries the authority of Presidential directives, OMB mandates, and NSA technical requirements. Understanding each layer, what it requires, who it applies to, and when, is essential for any organization operating in or adjacent to regulated industries.
The framework rests on three pillars: National Security Memorandum 10 (NSM-10), published May 4, 2022; OMB Memorandum M-23-02, published December 2022; and the NSA's Commercial National Security Algorithm Suite 2.0 (CNSA 2.0), published September 2022. Each plays a distinct role in the compliance architecture.
NSM-10: The Presidential Mandate
NSM-10, formally titled "Promoting United States Leadership in Quantum Computing While Mitigating Risks to Vulnerable Cryptographic Systems," established quantum computing as both a national security priority and a national security threat. The memo directed the National Security Council, NIST, NSA, CISA, and OMB to coordinate a whole-of-government response to quantum risk in cryptographic systems.
NSM-10 required federal agencies to complete cryptographic inventories of all NSS and non-NSS systems, prioritize systems that protect high-value data or long-lived sensitive information, develop migration roadmaps with specific milestones, and report progress to the National Cyber Director. The memo also introduced the concept of a "Y2Q" date, the point at which a cryptographically relevant quantum computer (CRQC) could break current public-key algorithms. NSM-10 explicitly stated that the U.S. government must migrate before that date, not after.
The significance of NSM-10 for the private sector is that it established the federal government's posture: migration is mandatory, timelines are fixed, and agencies have no discretion to delay. Private firms that contract with the federal government, process federal data, or operate critical infrastructure designated under Presidential Policy Directive 21 are within the scope of these requirements through contract clauses and regulatory extensions.
OMB M-23-02: The Implementation Mandate
OMB Memorandum M-23-02, "Migrating to Post-Quantum Cryptography," translated NSM-10's strategic direction into operational requirements for agency Chief Information Officers. M-23-02 required agencies to designate a senior official responsible for PQC migration, complete cryptographic inventories by specific dates, identify systems most exposed to harvest-now/decrypt-later attacks, and submit annual progress reports to OMB and CISA.
M-23-02 also established "cryptographic agility" as a minimum architectural requirement. Agencies must ensure that cryptographic algorithms in their systems can be replaced through configuration or software updates without requiring full system replacements. This requirement flows directly to federal contractors and vendors: any software or system sold to the federal government after M-23-02's publication must support cryptographic agility or include a documented migration path to achieve it.
For financial technology companies and blockchain developers, the cryptographic agility requirement is particularly relevant. Protocol designs that hardcode specific elliptic curves, signature schemes, or key sizes are architecturally non-compliant with M-23-02 requirements. This creates procurement barriers for federally adjacent use cases and should be treated as a design defect, not a future enhancement.
CNSA 2.0: The Algorithm Specifications
The NSA's CNSA 2.0 provides the technical content that M-23-02 and NSM-10 require agencies to implement. CNSA 2.0 specifies exact algorithms and parameter sets for National Security Systems. These are not minimum recommendations; they are mandatory specifications for NSS operators and the benchmark that commercial systems interfacing with NSS should target.
The CNSA 2.0 algorithm list is as follows. For key encapsulation: ML-KEM-1024, corresponding to FIPS 203 at the largest parameter set. For digital signatures: ML-DSA-87, corresponding to FIPS 204 at the 256-bit security level. For hash-based signatures in specific long-term use cases: SLH-DSA-SHA2-256s, which provides signature integrity without reliance on lattice hardness assumptions. For symmetric encryption: AES-256, unchanged from prior guidance. For hashing: SHA-384 or SHA-512. RSA and elliptic curve algorithms are explicitly not approved for new NSS deployments.
The NSA's choice of parameter sets is deliberately conservative. ML-KEM has three parameter sets: 512, 768, and 1024. NIST's minimum recommendation for most uses is ML-KEM-768. NSA requires ML-KEM-1024 for NSS. Similarly, ML-DSA has parameter sets 44, 65, and 87; NSA requires ML-DSA-87. This conservatism reflects the intelligence community's view that the cost of underestimating quantum threat timelines is unacceptable.
CISA's Role: The Operational Enforcement Arm
The Cybersecurity and Infrastructure Security Agency (CISA) published its Post-Quantum Cryptography Initiative roadmap in 2022 and has been the primary operational coordinator for federal migration. CISA operates the Joint Cyber Defense Collaborative (JCDC), which includes major financial institutions, critical infrastructure operators, and technology firms. CISA's PQC guidance flows through JCDC to private sector participants, making it a de facto requirement for critical infrastructure operators even without direct federal mandate.
CISA's roadmap emphasizes four priorities: cryptographic discovery and inventory, algorithm agility, hybrid deployment during transition, and supply chain awareness. The supply chain element is particularly relevant for blockchain and fintech companies: if your hardware, firmware, or third-party libraries do not support CNSA 2.0 algorithms, your migration cannot complete regardless of your own development progress. Vendor assessment is a first-order migration task.
The Timeline for NSS vs Non-NSS Systems
CNSA 2.0 distinguishes between National Security Systems and commercial systems. NSS timelines are more aggressive. Software and firmware on NSS must complete CNSA 2.0 migration by 2030. Networking equipment on NSS must complete migration by 2033. For non-NSS federal systems, the timelines align with NIST's general guidance, with mandatory migration for high-priority systems by 2030 and full deprecation of legacy algorithms planned for the 2030-2035 timeframe.
Commercial systems are not formally within NSS requirements, but the practical effect of CNSA 2.0 is that it sets the standard for regulated industries. When the OCC, SEC, or FINRA develop quantum cryptography guidance, they will reference NIST standards and likely align with CNSA 2.0 parameter choices. Building to CNSA 2.0 specifications now avoids the risk of having to re-engineer to higher parameter sets later.
How Trump's 2025 Executive Orders Build on NSM-10
The Trump administration's 2025 executive orders on quantum computing built directly on NSM-10's foundation rather than replacing it. The 2025 orders accelerated procurement timelines, added requirements for domestic quantum-resistant hardware production, and extended migration requirements more explicitly to critical infrastructure operators in the financial sector. The EU's parallel post-quantum infrastructure plan reflects similar urgency from European regulators. The continuity between administrations on quantum migration requirements reflects the bipartisan consensus that CRQC development by adversary states is a genuine near-term threat, not a distant theoretical risk.
Implications for Financial Regulators and Crypto Companies
The SEC, FINRA, and OCC have not yet published formal post-quantum cryptography requirements. However, each of these agencies has referenced quantum computing risk in recent guidance documents, examination procedures, and risk management frameworks. The OCC's guidance on technology risk management and the SEC's cybersecurity disclosure rules both create frameworks under which failure to address quantum cryptographic risk could constitute a material deficiency.
For crypto companies and blockchain developers that interface with regulated entities, the relevant question is not whether post-quantum requirements will exist but when. Financial institutions completing their own migrations in 2028-2030 will require compliant cryptographic interfaces from their blockchain counterparties. Starting migration planning in 2026 allows for the multi-year vendor coordination, protocol design, and hybrid deployment phases that a credible migration requires. Starting in 2029 does not.
