Resource archive
Blog
Technical explainers, migration notes, and operating guidance for teams preparing post-quantum cryptography work.
- Briefings
- 23
- Categories
- 5
- Updated
- June 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 TLS, and standards alignment.
- Defense — harvest-now-decrypt-later risk, Q-Day planning, and crypto-agility 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
23 published briefs for migration planning.
17
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
18
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
19
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 20
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