Migration guides

Why a quantum computer that does not yet exist is already a problem for data you send today, and how to reason about which of your secrets are actually at risk. The threat model, the maths of the exposure window, and where to start.

Crypto-agility is the property that lets you replace a cryptographic algorithm without re-architecting the system around it. What it means concretely, the anti-patterns that block it, and why it is the real deliverable of a post-quantum migration.

How to turn a cryptographic inventory into a prioritized, deadline-aware migration plan: the five phases, how to sequence by data shelf life rather than by ease, and how to roll out hybrids without breaking production.

A practical walkthrough of moving TLS 1.3 to X25519MLKEM768 hybrid key exchange: what changes on the wire, where support already exists, the handshake-size cost, and how to roll it out without breaking classical clients.

The whole picture in one read: what a quantum computer actually breaks, what it leaves alone, the NIST standards that replace the broken parts, the deadlines that make it a program and not a project, and where to start. The on-ramp to everything else.

A side-by-side of RSA and ECDH against ML-KEM: the hardness assumptions Shor's algorithm breaks, the encapsulate/decapsulate message pattern, key and ciphertext sizes, and performance, so you know exactly what changes in your systems, and what ML-KEM does not replace.

NIST standardised two post-quantum signature schemes with very different trade-offs. Which one to use where, why SLH-DSA exists at all, and the sizes that decide it.

How to turn on hybrid post-quantum key exchange (X25519MLKEM768), why modern stacks may already have it, the config that silently disables it, and the middlebox failure to expect.

The X + Y > Z inequality that decides whether a given secret is exposed to harvest-now-decrypt-later: what each term means, how to estimate them honestly, and how to turn the result into a per-system migration priority.

A post-quantum readiness assessment is a breadth-first evaluation of how prepared your organization is to migrate, turning a vague sense of quantum risk into a scored, prioritized baseline. What it evaluates, how it differs from a full technical audit, and what you get out of it.

Replacing classical key establishment with ML-KEM is more than a TLS change: key exchange lives in SSH, VPNs, email, messaging, and data at rest. What actually changes, hybrid vs pure, and how to stage the migration without stranding half your estate on classical crypto.

The concrete patterns that make an algorithm a replaceable component: runtime negotiation, a provider abstraction, config-driven selection, self-describing versioned formats, size-agnostic storage, and automated rotation. The engineering behind agility, not the argument for it.