Free tools Windows power users keep installed
One-click scans. No signup required.
Crypto-agility is now a federal implementation requirement, not an optional modernization project. Agencies and covered suppliers must identify vulnerable public-key cryptography, move systems toward approved post-quantum cryptography (PQC), and keep the ability to change algorithms without taking services offline. Civilian-agency milestones require PQC key establishment for high-value and high-impact systems by December 31, 2030, and PQC digital signatures by December 31, 2031. National Security Systems (NSS) follow the faster CNSA 2.0 path: new commercial NSS must support quantum-resistant algorithms by 2027, while legacy systems that cannot support them are targeted for phase-out by 2030.
This guide explains what those dates cover, which standards are ready, how to build a migration program, and what crypto-agility must look like in architecture, testing, procurement, and operations.
As an Amazon Associate I earn from qualifying purchases.
What the federal migration requires
The federal requirement has three connected parts:
- Know where vulnerable cryptography is used. Agencies need an inventory of public-key algorithms, certificates, protocols, software libraries, firmware, hardware security modules (HSMs), appliances, cloud services, and supplier components.
- Replace vulnerable mechanisms with approved PQC. NIST has finalized standards for quantum-resistant key establishment and digital signatures, but agencies still have to select the right profiles, validate implementations, and fit them to each system.
- Remain able to change cryptography safely. Systems must support algorithm and parameter updates through controlled changes rather than hard-coded, disruptive rewrites.
Quantum computers capable of breaking widely deployed RSA and elliptic-curve public-key systems are not established as an operational capability today. The migration is nevertheless urgent because encrypted data can be collected now and decrypted later, and because federal systems often have long procurement, accreditation, and refresh cycles.
Deadlines by federal mission
| Scope | Requirement or target | Date | What it means in practice |
|---|---|---|---|
| All civilian agencies | Identify a PQC migration lead under Executive Order 14412 | Within 30 days of June 22, 2026 | Assign accountable ownership, governance, and reporting rather than treating migration as an informal IT project. |
| High-value and high-impact civilian systems | PQC key establishment required through OMB guidance | December 31, 2030 | Transport and stored-key-establishment designs must use approved quantum-resistant mechanisms by the milestone. |
| High-value and high-impact civilian systems | PQC digital signatures required through OMB guidance | December 31, 2031 | Signing, authentication, code-signing, and certificate profiles must support approved PQC signatures. |
| Covered federal contractors | Proposed FAR requirement to comply with applicable PQC FIPS | December 31, 2030 target in the order | Contractors should expect solicitations and contract terms to require standards support and evidence of implementation. |
| New commercial NSS | Support CNSA 2.0 quantum-resistant algorithms | 2027 | New procurements and major designs need a CNSA 2.0-compatible path before deployment. |
| Legacy NSS | Systems unable to support quantum-resilient algorithms phased out | 2030 | Unsupported systems cannot simply remain in service because replacement has not been scheduled. |
| Federal long-range goal | Mitigate as much quantum risk as feasible | 2035 goal described by NIST | Agencies need a sustained program beyond the first compliance dates. |
The civilian dates and NSS dates are not interchangeable. NSS programs follow National Security Memorandum 8 and CNSA 2.0 guidance, while non-NSS federal systems are governed principally by National Security Memorandum 10, OMB inventory direction, and subsequent executive-branch requirements.
#1 Best Overall
The policy stack behind the deadlines
Federal quantum policy was built in layers. National Security Memorandum 8, issued in January 2022, addresses National Security Systems. National Security Memorandum 10, issued in May 2022, addresses non-NSS federal systems. NSA’s CNSA 2.0 guidance, published in September 2022, identifies the algorithm transition for NSS. OMB Memorandum M-23-02, issued in November 2022, directed agencies to inventory cryptographic use. The Quantum Computer Cybersecurity Preparedness Act of December 2022 codified inventory, migration, and reporting duties.
Executive Order 14412, dated June 22, 2026, adds immediate agency leadership, system milestones, procurement direction, and work on cryptographic bills of materials. It requires each agency head to identify a PQC migration lead within 30 days. It also directs OMB guidance for the 2030 and 2031 system dates, a NIST pilot, and a proposed Federal Acquisition Regulation (FAR) rule for covered contractors.
What crypto-agility means
NIST defines crypto-agility as the capability to replace and adapt cryptographic algorithms in protocols, applications, software, hardware, and infrastructure without interrupting the flow of a running system to achieve resiliency. In other words, crypto-agility is an architectural property, not a product label.
An agile design isolates cryptographic choices from business logic and makes those choices configurable, testable, observable, and replaceable. A service should be able to move from one approved algorithm profile to another through a controlled release, certificate rotation, firmware update, or policy change. It should not require every application team to rewrite custom cryptographic code.
Architecture characteristics to require
- Configurable algorithm selection: Keep key-establishment groups, signature schemes, parameters, certificate profiles, and protocol versions in managed configuration or policy rather than scattering them through source code.
- Stable cryptographic interfaces: Expose a narrow service or library interface so applications request operations without depending on one algorithm’s implementation details.
- Replaceable providers: Permit approved software, hardware, or HSM providers to be updated without changing application behavior.
- Versioned policy: Record which algorithms and parameters are allowed, preferred, transitional, or prohibited, with an emergency rollback process.
- Operational visibility: Log algorithm negotiation, certificate use, key identifiers, failures, and fallback events without exposing private key material.
- Capacity for larger objects: PQC keys, ciphertexts, signatures, and certificates can change message sizes and memory requirements, so interfaces and network paths must not assume today’s dimensions.
NIST’s CSWP 39 discusses mechanisms, trade-offs, challenges, and metrics for implementing this capability during PQC migration. Crypto-agility should therefore be measured through such evidence as replacement time, protocol interoperability, rollback time, inventory coverage, and the percentage of systems that can accept an approved algorithm update without redesign.
The standards to map into your plan
NIST finalized three relevant Federal Information Processing Standards on August 13, 2024:
Rank #2
- Ultra-Compact FIDO2 Security Key - Plug-and-stay or carry on a keychain. This USB-A hardware security key offers portable, always-on protection for desktop and mobile use. (Item Size: 0.75 X 0.74 IN x 0.25 IN)
- USB-A Hardware Key for All Devices - Works with USB-A ports on PC, Mac, Android, and other laptop/notebook device. Enables secure, cross-platform login with FIDO2.0 passkey support.
- FIDO Certified Security Key - Meets FIDO and FIDO2 standards. Works with Google, Microsoft, GitHub, Dropbox, and more. Please check service compatibility before purchase.
- Passwordless Login with Passkey - Supports passkey login via WebAuthn and CTAP2. Enjoy password-free sign-ins where supported. Not all websites or services currently support passkeys.
- Advanced Multi-Factor Authentication - Offers 200 FIDO2 passkey slots and 50 OATH-TOTP slots. Strong, flexible 2FA/MFA support across various apps and authentication platforms.
| Standard | Algorithm | Primary function | Migration use |
|---|---|---|---|
| FIPS 203 | ML-KEM | Key establishment | Protects the process used to establish shared encryption keys for protocols and applications. |
| FIPS 204 | ML-DSA | Digital signatures | Supports signing and verification for identities, software, documents, and transactions. |
| FIPS 205 | SLH-DSA | Digital signatures | Provides a hash-based signature option for use cases requiring that alternative security design. |
“Approved” does not mean that any implementation is automatically acceptable. Agencies must check applicable cryptographic-module requirements, including FIPS 140 validation, configuration profiles, certificate rules, and mission-specific guidance. A standards map should identify the exact algorithm, parameter set, module boundary, validation evidence, protocol version, and system owner for each deployment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Build the migration program in six steps
1. Appoint accountable ownership
Name the PQC migration lead required by Executive Order 14412 and establish a CIO, CISO, engineering, procurement, legal, and mission-owner working group. Set a reporting cadence and an escalation path for systems that cannot meet a milestone. Ownership should cover suppliers and inherited services, not only infrastructure operated directly by the agency.
2. Discover and classify cryptography
Create a machine-readable inventory before deciding what to replace. At minimum, record:
- RSA, Diffie-Hellman, elliptic-curve key exchange, and elliptic-curve signature use;
- certificates, certificate authorities, trust stores, and key-rotation schedules;
- protocols such as TLS, VPN, email, directory, API, and device-management channels;
- source-code libraries, compiled binaries, containers, mobile or embedded software, and firmware;
- HSMs, smart cards, appliances, accelerators, and other hardware dependencies;
- cloud services, managed identity systems, SaaS integrations, and external APIs;
- third-party and supplier components whose cryptographic behavior is not visible from application source.
Classify each dependency by data lifetime, exposure, mission impact, replacement lead time, and whether secrets could be collected now for later decryption. Prioritize high-value and high-impact systems, long-lived confidential information, externally reachable services, and components that are difficult to update.
3. Create a standards and dependency map
For every inventory item, map the current mechanism to a target profile using ML-KEM for key establishment and ML-DSA or SLH-DSA for signatures where applicable. Record whether the required module validation exists, whether a protocol peer supports the profile, and whether certificate or hardware changes are needed. This map turns a broad mandate into a sequence of engineering work packages.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →4. Test coexistence before production change
NSA states that CNSA 1.0 and CNSA 2.0 will coexist during the transition. Test hybrid or staged operation where mission guidance permits it, including negotiation behavior with older peers. Test certificate chains, signature verification, bandwidth, latency, memory, CPU use, hardware acceleration, logging, monitoring, backup and restore, incident response, and rollback. Include negative tests for an unsupported algorithm, malformed larger key objects, expired certificates, and a failed update.
Rank #4
5. Migrate according to risk and deadline
Use the inventory to sequence systems rather than attempting a single organization-wide cutover. Move systems with long confidentiality lifetimes and high external exposure first, then address dependencies with long procurement or accreditation cycles. Civilian plans should show how high-value and high-impact systems will meet the December 31, 2030 key-establishment date and the December 31, 2031 signature date. NSS plans must account for the 2027 requirement for new commercial systems and the 2030 legacy phase-out target.
6. Make procurement enforceable
Write requirements into solicitations, statements of work, contracts, and acceptance tests. Ask suppliers to provide:
- support for applicable FIPS 203, FIPS 204, and FIPS 205 profiles;
- FIPS 140 validation evidence where required;
- documented algorithm and parameter update procedures;
- cryptographic inventory and export interfaces;
- software bills of materials and cryptographic bills of materials or equivalent dependency data;
- support lifetimes, security-update commitments, and emergency replacement procedures;
- interoperability and performance test results for the agency’s protocols and hardware.
Do not accept a statement that a product is “quantum safe” without the algorithm, parameter set, module boundary, validation status, supported protocol, and update path being specified.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCryptographic bills of materials and evidence
Executive Order 14412 directs CISA and NIST to describe minimum elements for a cryptographic bill of materials (CBOM). A useful CBOM links each cryptographic component to its owner, location, algorithm, parameter set, certificate or key identifier, protocol, module, supplier, version, data classification, and replacement status. It should be exportable for audits and comparable across software releases.
Keep evidence with the inventory: discovery method, scan date, manual confirmation, test results, approval decision, exception owner, expiration date, and remediation ticket. An inventory that cannot show freshness and ownership will not reliably support a deadline decision.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to compare migration options
Whether evaluating an internal platform, a consultant, a discovery service, an HSM, or a network-security product, use the same decision axes:
Best Value
- ADD WI-FI TO YOUR YALE ASSURE LOCK OR LEVER: No hub or Connect needed. Note: This product only works on 2.4 GHz Wi-Fi in the U.S. and Canada.
- SIMPLE TO ADD: Simply insert the Yale Wi-Fi Smart Module in the slot above the batteries. Add the module as an accessory in the Yale Access app.
- UPGRADE YALE ASSURE LOCKS: Add Wi-Fi to your Yale Assure Lock or Lever with no hub or Connect needed.
- ACCESS FROM ANYWHERE: Lock, unlock, share access and see who comes and goes from anywhere using the Yale Access app.
- AUTO-UNLOCK: Your Assure Lock/Lever will automatically unlock as you get home and relock for you.
| Axis | Questions to ask |
|---|---|
| Standards alignment | Which FIPS 203, 204, and 205 algorithms and parameter sets are implemented? What FIPS 140 validation applies to the exact version and configuration? |
| Agility | Can algorithms, certificates, and policy be changed through updateable interfaces without application rewrites or service interruption? |
| Discovery depth | Does coverage include source, binaries, certificates, firmware, HSMs, cloud services, protocols, and third-party dependencies? |
| Interoperability and performance | What measured effects occur in latency, bandwidth, memory, CPU, handshake size, storage, and hardware acceleration? Which peers and protocol versions were tested? |
| Lifecycle and evidence | How long is support provided? How are updates delivered? Can the system export CBOM or equivalent records and produce audit evidence? |
| Federal readiness | Can the supplier document procurement eligibility, validation status, incident support, and a path for future approved algorithms? |
Common failure modes and fixes
“We scanned the source code, so we are done.”
Cryptography is often hidden in binaries, firmware, HSM policies, certificates, appliances, cloud services, and supplier libraries. Combine automated discovery with architecture review, certificate analysis, configuration inspection, and supplier attestations.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →“PQC support is a checkbox.”
A nominal algorithm option may not work with your certificate authority, protocol peers, hardware, logging, or performance envelope. Require end-to-end interoperability and rollback tests before acceptance.
“We will replace everything in one cutover.”
Federal systems have different owners, accreditation boundaries, refresh cycles, and external dependencies. A staged plan with coexistence, feature flags, and tested rollback reduces operational risk while preserving progress toward the deadline.
“A vendor controls the algorithm forever.”
That creates lock-in and undermines the mandate. Contracts should require exportable inventory, documented interfaces, update rights, and a replacement path for both algorithms and hardware.
“Legacy exceptions can remain undocumented.”
Every exception needs a system owner, reason, compensating control, risk acceptance, target date, and review interval. An exception without an expiration becomes an unplanned permanent dependency.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat a defensible 2026 migration plan contains
- A named migration lead and cross-functional governance charter.
- A dated inventory baseline with coverage and confidence measurements.
- Risk tiers based on data lifetime, mission impact, exposure, and replacement difficulty.
- A standards map for ML-KEM, ML-DSA, and SLH-DSA, including validation requirements.
- Interoperability, performance, monitoring, rollback, and incident-response test plans.
- Milestones tied to the 2027 NSS procurement gate, 2030 key-establishment and NSS legacy targets, and 2031 signature target.
- Contract language for PQC support, updateability, CBOM export, supplier disclosure, and evidence.
- An exception register with accountable owners and expiration dates.
The central decision is not merely which post-quantum algorithm to deploy. It is whether the organization can discover cryptography, change it under pressure, prove that the change works, and continue operating while old and new profiles coexist. That capability is what turns federal dates into an achievable migration rather than a last-minute replacement exercise.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
