Ship post-quantum cryptographyand know why it’s secure.

Why December 2026

Post-quantum migration now has dates attached. Teams are being asked for a plan, and most engineers have never been taught how these algorithms work. Recorded traffic can be decrypted later, so key exchange can’t wait for a quantum computer.

1. End of 2026EU member states begin the PQC transition and cryptographic inventories (NIS Cooperation Group roadmap).
2. Jan 1, 2027CNSA 2.0: new US National Security System acquisitions must support quantum-resistant algorithms.
3. 2030 → 2035NIST IR 8547 (draft): RSA-2048 and P-256 deprecated after 2030, all quantum-vulnerable public-key crypto disallowed after 2035.

What you’ll leave with

Curriculum

Tuesdays & Thursdays, 16:00–17:30 UTC (11:00 New York · 17:00 Berlin · 13:00 São Paulo). Each session is followed by a lab you finish during the week, with help in the cohort chat.

1. Session 1Tue, Dec 1

   The threat, the deadlines, and the one idea behind it all

   • What Shor’s algorithm actually breaks — and what it doesn’t (AES, SHA-2)
   • Harvest-now-decrypt-later and Mosca’s inequality for your data
   • Lattices and Learning With Errors from zero, built on intuition

   Lab: Encrypt with toy LWE in Python, then break it at small dimension with LLL — and watch the attack die as n grows.

   Pre-read: LWE, LLL

2. Session 2Thu, Dec 3

   From LWE to ML-KEM (FIPS 203)

   • Module-LWE, the NTT, compression and the q = 3329 choices
   • The Fujisaki–Okamoto transform and implicit rejection
   • Parameter sets, key/ciphertext sizes, failure probability

   Lab: Implement ML-KEM-768 key generation, encapsulation and decapsulation from the spec, and pass the official test vectors.

   Pre-read: Kyber / ML-KEM

3. Session 3Tue, Dec 8

   Signatures: ML-DSA, SLH-DSA and FN-DSA

   • Fiat–Shamir with aborts, and why signing loops
   • Choosing between ML-DSA, SLH-DSA and FN-DSA (Falcon)
   • Where bigger signatures hurt: certificates, firmware, JWTs

   Lab: Sign and verify with ML-DSA-65 in Python and Go, then benchmark size and latency against Ed25519 on your machine.

   Pre-read: ML-DSA, Signatures

4. Session 4Thu, Dec 10

   Hybrid key exchange in production TLS

   • X25519MLKEM768: how the hybrid combiner works
   • OpenSSL 3.5, Go crypto/tls, BoringSSL — what’s on by default
   • ClientHello size, middleboxes, and how to roll out safely

   Lab: Stand up a hybrid TLS server, capture the handshake, and verify the negotiated group and handshake size.

   Pre-read: Post-quantum security

5. Session 5Tue, Dec 15

   Crypto inventory and your migration plan

   • Finding every RSA/ECC use: TLS, SSH, JWT, code signing, KMS/HSM, SDKs
   • Crypto-agility: algorithms as configuration, not code
   • Prioritizing by data lifetime; questions to ask vendors

   Lab: Run an inventory over a sample service and draft the migration plan for your own system using the course template.

   Pre-read: Migration checklist

6. Session 6Thu, Dec 17

   Pitfalls, validation, and capstone reviews

   • Side channels and constant-time code; what never to roll yourself
   • Test vectors, ACVP, FIPS 140-3 validated modules
   • Reading a security estimate: what “Level 3” really promises

   Lab: Capstone: present your migration plan (or hybrid deployment) and get reviewed by the instructor and peers.

   Pre-read: Parameter selection

Who it’s for

Not for you if you want a research-level cryptanalysis course (the free algorithms chapters go deeper there) or a compliance-only overview with no code.

Your instructor

Ask your manager

Most participants can expense this as professional development. Copy this, edit, send.

Subject: Training request — Post-Quantum Cryptography for Engineers (Dec 1–Dec 17)

Hi [manager],

I’d like to take a 3-week live course on post-quantum cryptography: https://www.lattices.io/pro

Why now: NIST has standardized ML-KEM and ML-DSA, CNSA 2.0 requires quantum-resistant support in new national-security acquisitions from January 2027, and NIST plans to deprecate RSA-2048 and P-256 after 2030. We will need a migration plan for [our systems/product].

What I’ll bring back:
- A crypto inventory and prioritized PQC migration plan for [system], reviewed by the instructor
- Hands-on experience deploying hybrid (X25519MLKEM768) TLS and ML-DSA signatures
- Enough depth to evaluate vendor claims and library choices

Time: 6 × 90-minute live sessions (Tue/Thu, Dec 1–Dec 17) plus ~2 hours of labs per week.
Cost: $249 per seat (team pricing: 5 seats for $1,250). Invoice and completion certificate provided; full refund until the end of the second session.

Thanks,
[name]

FAQ