Quick answer: NIST finalized ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) on August 13, 2024, giving organizations approved, production-ready algorithms to replace RSA and ECC. It matters because a fourth signature algorithm, FN-DSA (FIPS 206), remains in draft, and a June 2026 executive order now requires U.S. federal agencies to complete post-quantum key establishment by December 31, 2030, and digital signatures by December 31, 2031. The recommended action is to build a cryptographic inventory now and begin migrating to the finalized standards rather than waiting for FN-DSA or later deadlines to force the issue.
Key Takeaways
- NIST finalized three post-quantum standards on August 13, 2024: ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205).
- FN-DSA (FIPS 206, formerly FALCON) remains in draft, with final publication expected in late 2026 or early 2027; HQC was selected in March 2025 as a backup KEM.
- A June 2026 executive order set binding federal deadlines: post-quantum key establishment by December 31, 2030, and digital signatures by December 31, 2031, for high-value and high-impact systems.
- A successful migration starts with a cryptographic inventory (CBOM), followed by identifying legacy systems that cannot support PQC, prioritizing critical systems, and testing before deployment.
- Crypto-agility, the ability to swap algorithms without major rework, is the key capability that makes ongoing PQC transitions manageable.
The New PQC Standards
The National Institute of Standards and Technology (NIST) finalized its first three post-quantum cryptographic algorithms on August 13, 2024. The three algorithms are ML-KEM, ML-DSA, and SLH-DSA. Earlier, these algorithms were known as CRYSTALS-Kyber, CRYSTALS-Dilithium, and SPHINCS+. A fourth signature algorithm, FN-DSA (formerly known as FALCON), remains in draft as FIPS 206, with final publication expected in late 2026 or early 2027. NIST also selected a fifth algorithm, HQC, in March 2025 as a backup key-encapsulation mechanism alongside ML-KEM.
We have recently received a lot of queries, including can an organization start implementing these PQC-safe algorithms? Are these the finalized algorithms? Are these the ultimate cryptographic algorithms that will secure our systems from a quantum attack?
The finalization of these algorithms means that organizations can now start implementing PQC-safe algorithms into their Public Key Infrastructure (PKI) to help ensure that systems that rely on secure digital identities and the exchange of encrypted data are safe from being broken by quantum computers.
Many organizations have already started developing strategies and roadmaps to migrate to PQC algorithms, and these PQC algorithm releases effectively create a starting point toward PQC readiness. But the truth is that organizations that are only just starting to think about migrating to the new standards are getting a late start in the race to secure the infrastructure that underpins their cryptographic assets.
Now, let’s talk a little more about the PQC Algorithms:
1. ML-KEM: FIPS 203 (Module-Lattice-based Key-Encapsulation Mechanism Standard)
ML-KEM provides a Key-Encapsulation Mechanism for sharing symmetric keys for general encryption. FIPS 203 states that it establishes a shared secret key (Symmetric key) between two users who communicate over a public network.
For more information, read In-Depth Overview of FIPS 203
2. ML-DSA: FIPS 204 (Module-Lattice-Based Digital Signature Standard)
ML-DSA is used to secure digital signatures. This standard outline specific details of algorithms used to generate and verify digital signatures, and “ML-DSA is considered secure, even against adversaries in possession of a large-scale quantum computer.”
The digital signature and the signed data are provided to the intended verifier. The verifying entity verifies the signature using the claimed signatory’s public key. Similar methods may be used to generate and verify signatures for stored and transmitted data.
For more information, read Understanding FIPS 204
3. SLH-DSA: FIPS 205  (Stateless Hash-Based Digital Signature Standard)
A stateless hash-based digital signature algorithm that is also used for data authentication and verification is described in FIPS 205.
For more information, read In-Depth Analysis of FIPS 205
| Type | FIPS Name | Current Specification Name | Initial Specification Name |
| KEM | FIPS-203 | ML-KEM | CRYSTALS-Kyber |
| Signature | FIPS-204 | ML-DSA | CRYSTALS-Dilithium |
| Signature | FIPS-205 | SLH-DSA | Sphincs+ |
| Signature | FIPS-206 (draft) | FN-DSA | FALCON |
It’s Time to Prepare for a Post-Quantum World
Those who haven’t started preparing for PQC readiness must understand the recommended next steps for PQC readiness.
Strategy for Migration to PQC
The migration strategy depends on many factors, such as compliance requirements, business requirements, the need to be aligned with industry best practices, and more. However, let’s talk about the key points that will help an organization for a successful migration to PQC
- Build a comprehensive and ongoing cryptographic inventory or a Cryptographic Bill of Materials (CBOM) and scope the impact of PQC on existing identified systems.
- Examine the organization’s application ecosystem and identify the legacy systems that cannot support PQC algorithms.
- Replace or upgrade the identified legacy systems that cannot support PQC algorithms.
- Prioritize crown jewels systems and data for PQC migration.
- Select appropriate PQC algorithms for your environment’s needs.
- Set up a lab environment to test the PQC algorithms.
- Deploy and monitor
- The best strategy to direct these phases with minimal trouble and maximum security can be achieved by becoming crypto-agile.
Know the PQC Timeline to Date
How Can Encryption Consulting Help You Prepare for a PQC World?
1. Quantum Threat Assessment
Our detailed Quantum Threat Assessment service utilizes advanced cryptographic discovery to analyze and secure your cryptographic infrastructure.
- Evaluate the state of the cryptographic environment as it is, identify any gaps in the current standards and controls that are in place for cryptography (such as key lifecycle management and encryption methods), and do a thorough analysis of any possible threats to the cryptographic ecosystem.
- We assess the effectiveness of existing governance protocols and frameworks and provide recommendations for optimizing operational processes related to cryptographic practices.
- Identify and prioritize the crypto assets and data based on their sensitivity and criticality for the PQC migration.
2. Quantum Readiness Strategy and Roadmap
- Identify PQC use cases that can be implemented within the organization’s network to protect sensitive information
- Define and develop a strategy and implementation plan for PQC process and technology challenges.
3. Build Crypto-Agility
- We assist in determining the cryptographic challenges, compromises, and threats for your organizations.
- We support seamless migration to new CAs, certificates, and PQC algorithms.
- We support automating certificates and key lifecycle management for stronger security and continuous compliance.
4. Compliance Enhancement
- Ensure compliance enhancement with industry standards.
- We help you stay updated with the new PQC algorithms and their usage and utilization for your organization.
5. Understanding Challenges and Providing Transition Support
- Assist in acknowledging and overcoming challenges during the transition to post-quantum cryptographic algorithms, ensuring a smooth and secure migration.
6. Vendor Evaluation & POC (Proof of Concept)
- Provide an overview of solution capabilities and vendor/product mapping to the identified use cases.
- Document the test/ evaluation scenarios.
Conclusion
The Post-Quantum Cryptographic Advisory Services offered by Encryption Consulting LLC help clients overcome the cybersecurity obstacles brought on by quantum computing. We offer perspectives on possible quantum hazards, steer the shift towards quantum cyber-preparedness, and align to Post-Quantum Cryptography (PQC) guidelines suggested by top organizations such as NIST. We assist companies in evaluating and updating their cryptographic infrastructure, so they are ready for the quantum age through proactive cryptographic discovery and strategic planning.
Frequently Asked Questions
Which NIST post-quantum algorithms are finalized and ready to implement?
ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205) were all finalized on August 13, 2024, and organizations can begin implementing them today. FN-DSA (FIPS 206) remains in draft, with final publication expected in late 2026 or early 2027.
What were these algorithms called before they were finalized?
ML-KEM was known as CRYSTALS-Kyber, ML-DSA was known as CRYSTALS-Dilithium, SLH-DSA was known as SPHINCS+, and FN-DSA was known as FALCON.
What is HQC, and why did NIST select a fifth algorithm?
HQC is a code-based key-encapsulation mechanism NIST selected in March 2025 as a backup to ML-KEM. It uses a different mathematical foundation than the lattice-based ML-KEM, providing algorithmic diversity in case future cryptanalysis weakens lattice-based approaches.
What deadline applies to U.S. federal agencies for PQC migration?
A June 2026 executive order requires federal agencies to transition high-value assets and high-impact systems to post-quantum key establishment by December 31, 2030, and to post-quantum digital signatures by December 31, 2031.
What is the first step in a PQC migration strategy?
Building a comprehensive, ongoing cryptographic inventory, often expressed as a Cryptographic Bill of Materials (CBOM), and scoping how PQC will affect existing systems. This inventory is the foundation for identifying legacy systems that cannot support PQC and prioritizing which systems to migrate first.
Why does crypto-agility matter for a PQC migration?
Crypto-agility, the ability to switch cryptographic algorithms without major system overhauls, allows organizations to move through inventory, testing, and deployment phases with minimal disruption, and to adapt again if standards or threat assessments change in the future.
