PQC (Post-Quantum Cryptography) 06-04-2026

NIST advances post-quantum signature algorithms

Larry Seltzer
Post Quantum Migration Plan Blog Hero

The transition to post-quantum cryptography (PQC) is entering a new phase. While core standards are already emerging, the industry is still working through the operational and security realities of long-term PQC deployment.

NIST’s latest announcement reflects that ongoing process.

The agency has launched another round of evaluation for post-quantum digital signature algorithms, advancing nine candidates for additional review. The move reinforces an important theme in PQC standardization: Cryptographic resilience depends on both strong algorithms and the ability to adapt as standards, threats, and implementation guidance evolve.

For enterprises, that makes crypto-agility just as important as algorithm selection itself.

NIST continues evaluating backup PQC algorithms

NIST recently announced a third round of competition for post-quantum digital signature algorithms. The agency continues to evaluate additional candidates as part of its broader effort to standardize cryptography capable of resisting future quantum computing attacks.

As NIST notes, any newly selected signature schemes would augment existing standards, including:

  • FIPS 204, Module-Lattice-Based Digital Signature Standard
  • FIPS 205, Stateless Hash-Based Digital Signature Standard
  • FIPS 186-5, Digital Signature Standard (DSS)
  • SP 800-208, Recommendation for Stateful Hash-Based Signature Schemes

The continued evaluation process reflects the importance of cryptographic diversity within the PQC ecosystem.

NIST has deliberately pursued algorithms based on different mathematical approaches. The goal is to reduce systemic risk if vulnerabilities or implementation weaknesses emerge in one family of algorithms over time. Additional detail on the mathematical foundations behind these schemes is available in NIST IR 8610.

That strategy matters because post-quantum migration is not a single deployment event. Organizations will likely operate hybrid cryptographic environments for years as standards mature and vendors update products, protocols, hardware, and infrastructure.

In practice, that means enterprises may need to support both classical and post-quantum cryptography simultaneously across applications, certificates, devices, and authentication systems. It also means that new PQC algorithms will likely be available in the future, and enterprises will need to be ready to implement them.

For most organizations, however, the implementation path remains relatively clear. ML-DSA is still expected to become the primary post-quantum digital signature algorithm for the majority of enterprise applications.

Crypto-agility is now an operational requirement

The larger challenge facing enterprises is not choosing a PQC algorithm. It's operational readiness.

Organizations must be able to update cryptographic systems quickly and consistently across distributed environments. That capability is known as crypto-agility.

Crypto-agility is the ability to adapt cryptographic systems, certificates, protocols, and policies within an established management framework.

Teams that remember the SHA-1 deprecation understand how difficult large-scale cryptographic transitions can become. Even organizations that understood the coming change often struggled with incomplete inventories, manual certificate processes, and inconsistent visibility across networks and platforms.

The transition to PQC will likely be even more operationally demanding.

Certificate lifecycles continue to shrink. Browser and platform requirements continue to evolve. Machine identities continue to grow across cloud, hybrid, and connected environments.

Many organizations still rely on partially automated certificate management processes assembled over years of incremental growth. Those approaches may automate parts of issuance or renewal, but they often still depend on manual approvals, disconnected tooling, or incomplete visibility into certificate inventories.

That model becomes increasingly difficult to sustain as certificate volumes and renewal frequency increase.

Certificate lifecycle automation supports PQC readiness

A complete certificate lifecycle management strategy does more than reduce operational overhead. It helps organizations build the foundation required for long-term crypto-agility. 

Centralized lifecycle management improves visibility across certificate inventories and automates issuance, renewal, revocation, and policy enforcement. Automation also reduces outages caused by expired or misconfigured certificates.

Those capabilities become increasingly important as organizations prepare for post-quantum migration. 

The organizations best positioned for PQC are not waiting for standards to fully stabilize before modernizing operations. They are improving visibility, automating lifecycle management, and building the operational flexibility needed to support ongoing cryptographic change.

PQC migration will ultimately be a long-term operational challenge as much as a cryptographic one. Organizations that strengthen crypto-agility now will be better prepared for whatever standards evolution comes next. 

Subscribe to the blog