Resource archive
Blog
Technical explainers, migration notes, and operating guidance for teams preparing post-quantum cryptography work.
- Briefings
- 29
- Categories
- 5
- Updated
- August 19, 2026
The Blog collects technical explainers, migration notes, and operating guidance for teams planning post-quantum cryptography work. Start with the core pages below if you are building an inventory or preparing an internal migration brief.
Recommended starting points
- Encryption — ML-KEM, ML-DSA, SLH-DSA, hybrid TLSHybrid modeRunning a classical and a quantum-safe algorithm side by side, so the connection stays secure as long as either one holds. It is the recommended way to cross the transition period., and standards alignment.
- Defense — harvest-now-decrypt-later risk, Q-Day planning, and crypto-agilityCrypto-agilityBeing able to swap one encryption algorithm for another without rebuilding your systems. It is what turns the next migration into a configuration change instead of a project. runbooks.
- Solutions — sector-specific migration paths for regulated teams.
- Trust center — how evidence, test vectors, and certification status should be reviewed.
Research notes and case studies are published only after review for factual accuracy, customer confidentiality, and export-control sensitivity. Press releases and approved media facts are kept separate in the Newsroom.
Latest analysis
Research notes
29 published briefs for migration planning.
23
Crypto-agility runbooks for regulated infrastructure teams
Crypto-agility is only useful when teams can operate it. A practical runbook defines owners, test vectors, rollback rules, exception handling, telemetry, and evidence that auditors can review.
Read post
24
How to brief risk committees on HNDL without overclaiming
Harvest-now/decrypt-later risk belongs in risk governance, but the briefing needs precision. Avoid quantum hype, separate present capture risk from future decryption capability, and anchor decisions in data lifetime.
Read post
25
Crypto inventory before PQC migration: what to count first
Post-quantum migration planning starts with inventory, not algorithm selection. Teams need a practical map of certificates, libraries, protocols, keys, and data-retention exposure before they can sequence remediation.
Read post 26
Hybrid TLS rollout model: lessons from a 12-month plan
Running ML-KEM alongside ECDH in TLS 1.3 across distributed infrastructure is straightforward in theory. This composite rollout model highlights practical planning issues around certificate chain sizes, middlebox interference, and HSM firmware constraints.
Read post 27
What the BSI’s PQC migration guide actually says
Germany's Federal Office for Information Security has published detailed post-quantum migration guidance. Here is what it recommends, what it maps, and what it leaves to your own risk assessment.
Read post
28
Choosing between ML-KEM and X-Wing for KEM
ML-KEM (FIPS 203) is the NIST standard. X-Wing is a hybrid combiner that pairs ML-KEM with X25519. Understanding when to use each, and why hybrid matters during the migration window.
Read post 29
Harvest now, decrypt later: a 2030 board-room problem
Nation-state adversaries are archiving encrypted traffic today. Under common 2029–2033 planning scenarios, that archive could become readable within retained-data lifetimes. The window to migrate is now.
Read post