Vista resources / The reference desk

PQC standards and migration resources

Start with NIST’s FIPS 203 for ML-KEM key establishment and FIPS 204 and 205 for ML-DSA and SLH-DSA signatures. For migration planning or product validation, choose the reading path that matches your question.

11 curated primary referencesReviewed October 31, 2026

Choose your next decision

Three ways into the material.

Start here · Standards overview

NIST PQC overview

Set the vocabulary before you set the plan.

Understand the standards program and follow official migration links.

For security and infrastructure leaders

How to use this reference

When to reach for it

Begin here when you need to explain why algorithm selection, implementation and migration planning are separate workstreams. Follow the publisher’s links to the authoritative standards rather than relying on summaries alone.

Leave with something useful

Write a short scope statement: which services, which cryptographic uses, who owns the work.

Keep the boundary clear

An overview is not a product approval or a migration design.

Start the inventory kit →

NISTRead source ↗

Algorithms · Final standard

FIPS 203 · ML-KEM

Understand the key-establishment building block.

Key-encapsulation mechanism; use it to identify exactly which KEM an implementation claims.

For developers and architects

How to use this reference

When to reach for it

Use this when a supplier says it implements ML-KEM. Identify the parameter set and the protocol that uses the mechanism, then ask how that implementation is configured and tested.

Leave with something useful

Record the algorithm, parameter set, library version and protocol binding in your inventory.

Keep the boundary clear

A standard does not establish that your deployed application uses the algorithm.

Ask the supplier →

NISTRead source ↗

Algorithms · Final standard

FIPS 204 · ML-DSA

Evaluate a signature claim on its own terms.

Digital signatures; review separately from confidentiality and key agreement.

For developers and pki teams

How to use this reference

When to reach for it

Use this for an ML-DSA implementation claim. Map where signing and verification happen, which parties must accept the format, and how the trust and update process works.

Leave with something useful

Identify the signer, verifier, implementation versions and compatibility test needed for a pilot.

Keep the boundary clear

Signature support does not establish post-quantum confidentiality for a connection.

Plan the signing workflow →

NISTRead source ↗

Algorithms · Final standard

FIPS 205 · SLH-DSA

Explore a hash-based signature option.

Stateless hash-based digital signatures; consult the standard for parameter sets.

For developers and signing teams

How to use this reference

When to reach for it

Consult this reference when an architecture or supplier specifies SLH-DSA. Keep the selected parameter set and the actual signing use case explicit in the evidence.

Leave with something useful

Capture the implementation choice and ask for workload-specific signature size and performance tests.

Keep the boundary clear

Algorithm selection still needs a system-level compatibility and lifecycle decision.

Build an evidence request →

NISTRead source ↗

Migration · Project guidance

NCCoE migration resources

Connect discovery to a migration program.

Find discovery, interoperability and migration work to inform your own plan.

For infrastructure and security teams

How to use this reference

When to reach for it

Use the migration collection to orient cryptographic discovery and interoperability work. Choose material that matches the boundary you are investigating and note the maturity of each linked publication.

Leave with something useful

Turn one applicable recommendation into an owned discovery task or a bounded pilot.

Keep the boundary clear

Project material and draft guidance are not blanket requirements for every organization.

Choose a migration playbook →

NISTRead source ↗

Government · Guidance collection

NSA post-quantum resources

Establish applicability before interpreting a requirement.

Locate CNSA 2.0 and related guidance; first establish whether it applies to your system.

For national security system owners

How to use this reference

When to reach for it

Use NSA’s collection when National Security System requirements may apply. Identify the relevant policy, technology category and algorithm requirements, then involve the responsible authorization team.

Leave with something useful

Record the specific source, version, relevant section and applicability decision.

Keep the boundary clear

A claim of CNSA alignment is not itself a product validation or deployment authorization.

Understand approval evidence →

NSARead source ↗

Validation · Official validation program

CAVP

Check an algorithm implementation claim.

Look up tested algorithm implementations and understand the scope of algorithm validation.

For procurement and engineering

How to use this reference

When to reach for it

Use the official program information to locate and interpret algorithm validation evidence. Match the implementation and environment to the supplier’s claim rather than treating a vendor name as the boundary.

Leave with something useful

Record the implementation identifier, algorithms, parameters, environment and review date.

Keep the boundary clear

Algorithm validation and cryptographic module validation are different evidence types.

Open the evidence guide →

NISTRead source ↗

Validation · Official registry

CMVP validated modules

Read the module certificate and its conditions.

Verify a module certificate, security policy, version and operational environment.

For procurement and security reviewers

How to use this reference

When to reach for it

Use the official registry to verify a named module and its current record. Read the security policy alongside the certificate and check the exact version, operating mode and environment.

Leave with something useful

Record the official identifier and status, then list the algorithms and conditions explicitly covered.

Keep the boundary clear

An active module certificate does not automatically cover every product feature or PQC algorithm.

Use the evidence workbook →

NISTRead source ↗

Inventory · Specification resources

CycloneDX CBOM

Make cryptographic evidence portable.

Understand how to represent cryptographic assets and dependencies.

For inventory and software teams

How to use this reference

When to reach for it

Use the CBOM resources to understand how cryptographic assets and relationships can be represented. Connect a file’s fields to its collection scope and the systems that produced the evidence.

Leave with something useful

Inspect one sample artifact and identify the provenance, dependencies and coverage gaps you would need in production.

Keep the boundary clear

A valid JSON file can still contain incomplete or stale observations.

Explore annotated examples →

CycloneDXRead source ↗

Testing · Implementation documentation

OpenSSL TLS client reference

Understand the mechanics of a TLS observation.

Review the handshake options behind the website checker.

For operators and engineers

How to use this reference

When to reach for it

Use the client reference to understand SNI, certificate verification and group selection behind a TLS probe. Keep the client configuration and endpoint in the test record.

Leave with something useful

Preserve the negotiated group, authentication details, timestamp and test scope.

Keep the boundary clear

One handshake is evidence about one connection, not an audit of an entire estate.

Run the website checker →

OpenSSLRead source ↗

Testing · Implementation documentation

Cloudflare PQC to origin

Separate the public edge from the origin.

Understand why a public edge observation does not establish origin protection.

For web and cdn operators

How to use this reference

When to reach for it

Use this when a CDN sits in front of your site. The public hostname and origin connection are different parts of the delivery path and should have separate evidence and owners.

Leave with something useful

Draw the browser → edge → origin path and assign a check to each connection.

Keep the boundary clear

A positive public-endpoint result does not establish the origin configuration.

Map the connections →

CloudflareRead source ↗

From reading to evidence

Make the next step concrete.

Record the source, version, relevant section and date. Decide who owns the follow-up and what evidence will demonstrate progress. Standards, guidance and implementation documentation answer different questions; keep their scope visible in your notes.

Build the inventory →Ask better supplier questions →Review an official record →