Most post-quantum migration advice I found was either a vendor pitch or a summary of a summary. So I built a checklist where every item is a yes/no question with a test you can run, and every claim was checked against the standard itself.

Repo: https://github.com/sunilgentyala/pqc-migration-checklist (22 items, MIT)

What it covers

  1. Inventory: every use of RSA, ECDSA, EdDSA and Diffie-Hellman, including embedded and third-party code.
  2. Prioritisation and timelines: NIST IR 8547, US federal dates, UK NCSC and EU roadmaps.
  3. Algorithm choices: FIPS 203, 204 and 205, and what is not yet approved.
  4. Protocol deployment: hybrid TLS and SSH, certificate profiles, chain size.
  5. Crypto agility.
  6. Governance and evidence.

Three things I got wrong before checking

  • NIST IR 8547 is final (27 October 2026). It says quantum-vulnerable public-key cryptography will be deprecated after 2030 and disallowed after 2035. It does not say RSA is disallowed in 2030, which is what many articles repeat from the 2024 draft.
  • FN-DSA and HQC are not final standards. NIST IR 8547 says a FIPS is in development for each. Do not put them in production baselines.
  • You can test hybrid TLS in one command. With OpenSSL 3.5 or later: openssl s_client -connect HOST:443 -groups X25519MLKEM768 -brief. Look for Negotiated TLS1.3 group: X25519MLKEM768. I ran it on 2026-11-17 and the repo records the result.

About CNSA 2.0

I read the NSA advisory directly. The PDF at the NSA's URL is PP-22-1338, September 2022, Version 1.0. It names CRYSTALS-Kyber and CRYSTALS-Dilithium with the specification listed as "TBD", so it predates FIPS 203 and 204. Many posts quote dates from it as if they were current. The repo only states what that document says (AES-256, SHA-384 or SHA-512, LMS or XMSS for firmware signing) and says plainly that the current CNSA 2.0 FAQ was not read.

What was not verified

Each README has a "What was not verified" section. For this one it includes the current CNSA 2.0 FAQ, one row of an IR 8547 table that needs a visual check, the ssh -vv negotiated line, and the IANA registry entry for the X25519MLKEM768 codepoint. If you can confirm or correct any of these, there is an issue form.

Companion checklists