Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Short answer: post-quantum cryptography (PQC) is conventional cryptography designed to resist future cryptographically relevant quantum computers. NIST finalized three PQC standards on August 13, 2024, but organizations should not wait for a universal deadline: begin by inventorying cryptographic use, ranking long-lived sensitive data, testing interoperability, and requiring migration plans from suppliers. NIST’s 2035 horizon and the NSA’s 2027/2030 dates apply to different scopes and are not one compliance schedule for every business.
What is post-quantum cryptography?
Post-quantum cryptography uses algorithms intended to withstand attacks from future quantum computers while running on ordinary computers, networks and products. It is not quantum cryptography or quantum key distribution; no quantum communication channel is required. The standards now being deployed address public-key functions that organizations use to establish shared secrets and authenticate software, devices, messages and transactions.
As an Amazon Associate I earn from qualifying purchases.
The immediate planning issue is exposure over time. Public-key systems such as RSA, ECDH and ECDSA appear throughout products, protocols and cloud services. Replacing them can affect certificates, key lifecycles, hardware, applications, network protocols and supplier integrations. A PQC program is therefore an engineering and procurement effort, not a one-line algorithm change.
Which PQC standards has NIST finalized?
The U.S. Secretary of Commerce approved three Federal Information Processing Standards (FIPS) published by NIST on August 13, 2024. Two cover different signature constructions; one covers key establishment.
#1 Best Overall
| Standard | Algorithm | Primary function | Cryptographic lineage | Maturity |
|---|---|---|---|---|
| FIPS 203 | ML-KEM | Establishing a shared secret over a public channel | Derived from CRYSTALS-KYBER | Final FIPS standard, approved August 13, 2024 |
| FIPS 204 | ML-DSA | Digital signatures for authentication and detecting unauthorized modification | Derived from CRYSTALS-Dilithium | Final FIPS standard, approved August 13, 2024 |
| FIPS 205 | SLH-DSA | Stateless hash-based digital signatures | Derived from SPHINCS+ | Final FIPS standard, approved August 13, 2024 |
“Final” means the specification has completed NIST’s standards approval process. It does not mean every operating system, appliance, protocol or supplier already supports it, nor that a company can deploy it without testing certificate sizes, performance, trust stores and interoperability.
Where does HQC fit?
NIST selected HQC for standardization on March 11, 2025 as a backup key-establishment algorithm. HQC is not one of the three finalized FIPS standards listed above. Treat a selection-for-standardization announcement as a signal to watch future standards work, not as authorization to claim that an additional final FIPS standard is available.
When should organizations start migrating to post-quantum cryptography?
Start now with preparation and controlled pilots. CISA, NSA and NIST state that “A successful post-quantum cryptography migration will take time to plan and conduct.” Their guidance recommends building a roadmap, discovering where cryptography is used, assessing risk and engaging vendors before final deployment decisions.
Preparation can begin even while products and protocols are adding support. Early work gives security and procurement teams time to find systems that cannot be upgraded, contracts that lack roadmap commitments, certificates with long renewal cycles and data whose confidentiality must last for decades.
Rank #2
- Assign ownership. Name an executive sponsor and a technical program lead spanning security, infrastructure, application engineering, architecture, legal, procurement and operational technology (OT) where applicable.
- Set a migration policy. Define which systems must support approved PQC standards, how hybrid deployments will be handled during transition, evidence suppliers must provide and the risk-acceptance process for exceptions.
- Build the inventory. Record cryptographic algorithms, protocols, certificates, key lifecycles, dependent components, data flows and supplier dependencies. Record metadata about keys and their use, not secret key material.
- Rank exposure. Prioritize systems by business criticality, exploitability, replacement lead time and the length of time protected data must remain confidential.
- Test representative paths. Exercise identity, transport security, application programming interfaces, backup, signing and device-update workflows with the PQC capabilities offered by your platforms.
- Make suppliers accountable. Require product support dates, upgrade paths, interoperability evidence and a process for handling algorithms that are deprecated or revised.
What is the NIST PQC migration timeline?
NIST’s current project guidance describes an end-state in which quantum-vulnerable algorithms are deprecated and ultimately removed from NIST standards by 2035, with higher-risk systems transitioning earlier. NIST IR 8547 is identified as an initial public draft, published November 12, 2024. A draft transition plan is guidance for standards evolution, not a statute that automatically imposes a deadline on every private company.
The 2035 horizon should therefore be used for planning backwards: systems with long procurement, certification or field-replacement cycles need work well before that point. Organizations should verify the current status of IR 8547 and related NIST publications when setting formal policy because draft documents and implementation schedules can change.
| Date | Authority and document context | What it means | Who it applies to |
|---|---|---|---|
| August 13, 2024 | NIST and the U.S. Secretary of Commerce | Publication and approval of FIPS 203, FIPS 204 and FIPS 205 | Organizations choosing NIST-approved PQC standards; adoption still depends on product and protocol support |
| November 12, 2024 | NIST IR 8547 publication record | Initial public draft of a transition plan | Readers and stakeholders evaluating proposed NIST standards transition guidance |
| 2035 | NIST PQC project horizon | Target horizon to deprecate and remove quantum-vulnerable algorithms from NIST standards, with higher-risk systems earlier | NIST standards transition planning; not a universal private-sector compliance deadline |
| 2027 | NSA CNSA 2.0 guidance | New commercial national security systems must support specified quantum-resistant algorithms | National security systems (NSS) under the CNSA 2.0 scope |
| 2030 | NSA CNSA 2.0 guidance | Legacy national security systems are scheduled for phaseout | Legacy NSS under CNSA 2.0; not ordinary commercial or consumer systems |
What do the 2035, 2030 and 2027 dates apply to?
2035: a NIST standards horizon
2035 describes NIST’s stated direction for removing quantum-vulnerable algorithms from its standards. It is not, by itself, a federal filing date or a blanket requirement that every company complete migration by December 31, 2035. A regulated organization may have a separate rule, contract or sector timetable that is earlier or more specific.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
2027: new commercial NSS support
NSA’s 2027 milestone applies to new commercial national security systems covered by CNSA 2.0. It is a procurement and deployment requirement for that mission scope, not a general deadline for banks, manufacturers, software companies, schools or consumers.
2030: legacy NSS phaseout
The 2030 milestone concerns phasing out legacy national security systems under CNSA 2.0. A company supplying or operating such systems may have obligations through its government contract, while an otherwise unrelated commercial environment should not claim that 2030 is its deadline solely because the date appears in NSA guidance.
What is a harvest-now-decrypt-later attack?
In a harvest-now-decrypt-later scenario, an adversary captures encrypted traffic or data today and stores it for a future period when a cryptographically relevant quantum computer could decrypt vulnerable public-key protections. The danger is greatest when information must remain secret for a long time: strategic plans, personal records, intellectual property, diplomatic material, credentials, source code or long-lived device secrets.
This is a confidentiality-lifetime problem, not proof that current quantum computers can break widely deployed public-key systems. No reliable date is established for a cryptographically relevant quantum computer; estimates vary. The prudent question is how long each category of data must remain protected and how long replacing the systems that protect it will take.
For each major data flow, document the classification, required confidentiality lifetime, encryption and key-establishment methods, storage locations, recipients and replacement lead time. Move the highest-lifetime, highest-impact flows into testing first.
Rank #4
How do I create a cryptographic inventory?
NIST describes an inventory as a record of cryptography across systems, applications, services, devices, data flows and their dependencies. Begin with discovery rather than assuming that a central certificate database shows the whole environment.
Capture the technical facts
- Algorithms and modes used for key establishment, signatures and other public-key operations.
- Protocols and libraries that invoke those algorithms, including externally exposed interfaces.
- Certificates, trust stores, signing authorities, expiration dates and renewal ownership.
- Key lifecycle metadata: creation, rotation, archival, revocation, destruction and responsible team. Do not place secret key material in the inventory.
- Applications, appliances, devices, firmware, cloud services and suppliers that depend on each cryptographic component.
- Data flows showing where protected information originates, travels, is stored and is disclosed.
Add business-risk context
- Business criticality and consequences of loss of confidentiality, integrity or authenticity.
- How long the information must remain confidential.
- Upgrade, replacement, certification and procurement lead times.
- Interoperability constraints, including counterparties that cannot be changed unilaterally.
- Evidence of current PQC support, planned releases, testing status and contractual commitments from each vendor.
Validate the record
Compare automated discovery with architecture diagrams, certificate authorities, software bills of materials, network telemetry, endpoint configurations and supplier questionnaires. Have application and OT owners confirm whether a listed dependency is production-critical. Mark confidence and the date of the last validation so stale entries do not look authoritative.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should I ask vendors about quantum readiness?
Use procurement and security reviews to obtain specific, testable answers rather than a claim that a product is “quantum safe.” Ask:
Recommended Free Tools
- Which of FIPS 203 ML-KEM, FIPS 204 ML-DSA and FIPS 205 SLH-DSA are supported, in which product versions and deployment modes?
- Is support final, experimental, restricted to a laboratory build or dependent on a third-party library?
- Which protocols, certificate formats, hardware modules, operating systems and cloud regions interoperate with the implementation?
- Can the product run a documented transition or hybrid configuration, and how are negotiation, downgrade resistance and policy enforcement handled?
- What are the effects on key and certificate sizes, handshake behavior, storage, bandwidth, latency and hardware capacity in the vendor’s published tests?
- How are keys generated, rotated, revoked, archived and destroyed across the migration?
- What dependencies must customers, partners or managed-service providers upgrade first?
- What is the support and patch policy if NIST changes guidance, deprecates an algorithm or publishes an additional standard such as HQC?
- Can the vendor provide a dated roadmap, interoperability test results, benchmarking methods and a process for reporting implementation defects?
- Which data, logs and telemetry are collected to prove that vulnerable algorithms have been removed from active paths?
Require answers to identify product editions and release numbers. A roadmap without a supported version, test method or contractual commitment is a planning statement, not evidence of readiness.
What should organizations compare when selecting migration support?
Whether the support is an internal platform, consulting engagement or software service, compare capabilities that reduce uncertainty:
| Evaluation area | Evidence to request |
|---|---|
| Cryptographic discovery | Systems, applications, devices, services, protocols and algorithms the process can identify, including undocumented dependencies |
| Inventory and dependency management | Records for certificates, key lifecycle metadata, data flows, owners, suppliers and relationships between components |
| Risk prioritization | Methods for combining asset criticality, confidentiality lifetime, exposure and replacement lead time |
| Interoperability | Supported protocols and products, test environments, counterparties and handling of transition or hybrid configurations |
| Benchmarking | Reproducible measurements, test conditions, hardware details and results for performance and capacity impacts |
NIST’s National Cybersecurity Center of Excellence work explicitly includes visibility and risk management, along with interoperability and benchmarking. Those workstreams are useful selection criteria; they are not a product endorsement or a substitute for testing your own environment.
What are the most common migration mistakes?
- Treating 2035 as a single deadline. Use the NIST horizon for standards planning and check the laws, contracts and sector rules that actually govern your systems.
- Applying NSA dates to every business. The 2027 and 2030 milestones are for CNSA 2.0 national security systems.
- Assuming a drop-in replacement. Protocol negotiation, certificate chains, hardware limits, application dependencies and counterparties can all change.
- Inventorying only certificates. Cryptography also lives in firmware, libraries, APIs, signing pipelines, backups, devices and supplier services.
- Ignoring long-lived data. Harvest-now-decrypt-later risk makes confidentiality lifetime a central prioritization measure.
- Confusing algorithm status. Final FIPS standards, a selected-for-standardization algorithm such as HQC and a draft transition document have different levels of authority.
- Accepting unsupported marketing language. Request versions, test evidence, interoperability results and lifecycle commitments.
Where can you start your migration to PQC?
Start with one high-value, long-lived data flow and one representative public-key dependency. Document its current algorithms, certificates, owners, suppliers and confidentiality lifetime; identify the first upgradeable component; then run an interoperability and performance pilot using the finalized NIST standards where your platforms support them. Feed the results into a roadmap with owners, funding, dates, acceptance tests and exception handling.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRepeat that cycle across the inventory. The objective is not to claim that every system is already quantum-resistant. It is to know where vulnerable cryptography exists, which systems matter most, what each supplier must change and how much time remains before the organization’s own risk threshold or applicable policy requires action.
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.
