Part II · Some tech background · 6 lessons · about 83 minutes
Practitioner
For IT, security, compliance and product people. The new NIST standards, the government deadlines, and how a real migration runs from inventory to rollout.
By the end you can: Plan a post-quantum migration: what to inventory, what to replace first, and which deadlines apply.
- 07Meet the new standards: ML-KEM, ML-DSA and friends14 min · 1 interactiveFIPS 203, 204 and 205 explained for practitioners: what ML-KEM, ML-DSA and SLH-DSA do, how big they are, and which one to pick.
- 08Hybrid key exchange: post-quantum TLS today14 min · 1 interactiveHow X25519MLKEM768 works, which browsers and libraries already use it, what breaks, and how to check whether your connections are post-quantum.
- 09The deadlines: who requires what, and when13 min · 1 interactiveCNSA 2.0, NSM-10, OMB M-23-02, NIST IR 8547, the UK NCSC and the EU roadmap: the post-quantum dates that matter, what's binding and what's guidance.
- 10Cryptographic inventory: find it before you fix it14 min · 1 interactiveHow to find every place your organization uses cryptography, what to record, how to prioritize, and the traps that hide quantum-vulnerable keys.
- 11Crypto-agility: build to swap13 min · 1 interactiveWhy algorithms keep getting replaced, what crypto-agility looks like, and the design choices that turn a multi-year migration into a config change.
- 12Migrating certificates, code signing and firmware15 min · 1 interactiveWhy signatures migrate differently, how big post-quantum certificate chains get, where the web PKI is heading, and how to sign code and firmware.
Next up: Engineer (Part III)
For developers and engineers. Lattices and Learning With Errors, ML-KEM from the inside, hash-based signatures built from scratch, and the implementation bugs that bite. See the track →
Track created by Kyeson Blake Utley.