Cryptographic resilience, in practice.
Practical guides on cryptographic inventory, CycloneDX CBOM, post-quantum migration and EU regulation (DORA, NIS2, CRA) — written by a practitioner, not a marketing team. Articles en français →
Free tool · 2 minutesHow quantum-ready is your organisation? Take the self-assessment
Ten questions, a readiness score by area and your three next steps. No email required — answers stay in your browser.
Latest · November 2026
How to prepare your post-quantum roadmap: a 7-step method and a template
Mandate, scope, inventory, risk classification, target state, dated waves and suppliers — with the KPIs to track and an 11-section document structure.
10 min read Glossary · Reference NewPost-quantum cryptography glossary: 43 terms, defined plainly
CBOM, CRQC, HNDL, ML-KEM, ML-DSA, hybrid cryptography, DORA, NIS2 and more — each with its own link and a pointer to the deeper guide.
Reference Evidence · Python · CycloneDX 1.6 NewPython CBOM example: pyca/cryptography
A pinned Python inventory run on a public library, CycloneDX 1.6 export, reviewed source evidence and explicit coverage limits — reproducible from the published bundle.
Case study Migration · Planning NewHow to estimate the blast radius of a post-quantum migration
A count of RSA findings is not a scope. Five steps from an inventory to reach, choke points, effort and waves — with a worked example.
6 min read Energy & utilities · Post-quantum NewPost-quantum cryptography for energy & utilities: where to start
Field equipment outlives its algorithms. What to inventory, what to move first — firmware signing, device identities, SCADA links — and what to ask suppliers.
7 min readCBOM & inventory
Every post-quantum or compliance programme starts with knowing where cryptography lives. What a Cryptographic Bill of Materials contains and how to produce one — see also the cryptographic inventory and CBOM generator pages.
Evaluating a cryptographic discovery or CBOM tool: 24 questions to ask every vendor
Coverage, evidence quality, CycloneDX 1.6, deployment, CI/CD, risk scoring, EU regulatory mapping and commercial terms — with what a good answer looks like. Printable.
9 min read CBOM · SBOM · CycloneDX NewCBOM vs SBOM: what’s different, and why you need both
An SBOM lists the libraries you ship; a CBOM lists the cryptography you use, where and with which parameters. A side-by-side example from pyca/cryptography and what the CRA asks for.
7 min read CBOM · CycloneDXWhat is a CBOM? The CycloneDX 1.6 Cryptographic Bill of Materials, explained
What a CBOM captures, a concrete CycloneDX 1.6 example, and how it generates — the foundation for post-quantum and compliance work.
Post-quantum migration
From quantum risk to a sequenced plan: the NIST standards, harvest-now-decrypt-later exposure, scoping and the questions a CISO should be able to answer.
How to prepare your post-quantum roadmap: a 7-step method and a template
Mandate, scope, inventory, risk classification, target state, dated waves and suppliers — with the KPIs to track and an 11-section document structure.
10 min read Algorithms · ML-KEM · FIPS 203 NewML-KEM (FIPS 203) explained: what it replaces, how big it is and how to deploy it
The post-quantum key exchange most organisations deploy first: parameter sets and sizes, hybrid X25519MLKEM768 in TLS 1.3, library support and the migration steps.
9 min read Algorithms · ML-DSA · FIPS 204 NewML-DSA (FIPS 204) explained: the post-quantum signature most systems will use
Parameter sets and sizes, what kilobyte signatures do to certificates and TLS handshakes, hybrid and composite signatures, and how to plan the move.
9 min read Algorithms · SLH-DSA · FIPS 205 NewSLH-DSA (FIPS 205) explained: when conservative hash-based signatures are worth their size
Stateless hash-based signatures: the 12 parameter sets, how they compare with ML-DSA and LMS/XMSS, and where they fit — roots, firmware, archives.
9 min read Post-quantum · NIST FIPSPost-quantum migration roadmap: ML-KEM, ML-DSA & FIPS 203/204/205
What the NIST standards replace, how to prioritise by risk, and how to plan migration in waves toward crypto-agility.
HNDL · Quantum riskHarvest now, decrypt later: how to assess your HNDL exposure
The quantum risk that is already happening — and a practical method to quantify and prioritise it across your estate.
Migration · Planning NewHow to estimate the blast radius of a post-quantum migration
A count of RSA findings is not a scope. Five steps from an inventory to reach, choke points, effort and waves — with a worked example.
6 min read Checklist · CISO NewPost-quantum readiness checklist: 15 questions every CISO should be able to answer
Inventory, HNDL risk, governance, suppliers and crypto-agility — with what good evidence looks like for each. Printable.
7 min readEU regulation: DORA, NIS2, CRA and national guidance
What European texts actually require for cryptography, and the evidence supervisors ask for. ANSSI guidance is covered in French.
BSI, ENISA, NCSC and ANSSI on post-quantum cryptography: where they agree, where they differ
Hybrid use, algorithms, parameter levels and timelines side by side — and six design rules for groups that must satisfy several agencies at once.
9 min read EU roadmap · Deadlines NewThe EU post-quantum roadmap: what you must have done by 2026, 2030 and 2035
First steps including cryptographic inventories by end-2026, high-risk use cases by 2030: what each milestone means under DORA and NIS2, and a 90-day plan to meet the first one.
7 min read NIS2 · Compliance NewNIS2 Article 21 and cryptography: what evidence auditors will actually ask for
“We use TLS” is not a cryptography policy. What Article 21(2)(h) and Implementing Regulation 2024/2690 require, and how to evidence it.
7 min read DORA · Primary sources UpdatedDORA cryptography requirements: what Article 9 and the RTS actually say
DORA Article 9 and RTS 2024/1774 Articles 6, 7 and 13, quoted from the official texts: the policy, key management, the certificate register, and the evidence each provision calls for.
10 min readCrypto-agility
Post-quantum will not be the last algorithm change. How to measure and build the ability to swap cryptography quickly — see also crypto-agility with CRYPTAGION.
Sectors
Where sector constraints change the order of work: long-lived data and field equipment, supplier dependencies and sector supervisors.
DORA for insurers: cryptography, post-quantum risk and the data that must outlive the contract
Health and life data kept for decades, broker and partner links, signed contracts: DORA and RTS 2024/1774 read for an insurer, likely supervisory questions and a 90-day plan.
9 min read Banking · DORA · Post-quantum NewDORA for banks: cryptography, post-quantum risk and what supervisors will ask
DORA Articles 5, 8, 9 and 28 and RTS 2024/1774 applied to a bank’s cryptography: where it hides — payments, open banking, interbank links — the evidence to prepare and a 90-day plan.
9 min read Energy & utilities · Post-quantum NewPost-quantum cryptography for energy & utilities: where to start
Field equipment outlives its algorithms. What to inventory, what to move first — firmware signing, device identities, SCADA links — and what to ask suppliers.
7 min readEvidence
Real runs on public code — ours and other tools’ — with the CBOMs, the source evidence and the coverage limits published so you can check them.
Post-quantum TLS in Europe 2026: ML-KEM adoption study
We tested the public websites of 380 major European organisations for hybrid ML-KEM key exchange: 64% accept it, mostly thanks to their CDN. Method, aggregates and data published.
Study Evidence · Comparison · CBOMkit NewCBOMkit vs CRYPTAGION: two tools, two real repositories, every CBOM published
Keycloak (Java) and pyca/cryptography (Python) at pinned commits. CBOMkit found far more in the Java app at first; after fixing our Java rules, we find 74 of its 78 production lines. CRYPTAGION found more in the library. Every CBOM, log and script is published.
Comparison Evidence · Python · CycloneDX 1.6 NewPython CBOM example: pyca/cryptography
A pinned Python inventory run on a public library, CycloneDX 1.6 export, reviewed source evidence and explicit coverage limits — reproducible from the published bundle.
Case studyWant to see it on real code? Request a demo — we scan a public repository that matches your stack, live. · ← Back to home
No guide matches your search.