The Four Capabilities a PQC Program Needs
Most organizations don't need four post-quantum hires. They need four capabilities: discovery, architecture, implementation, and delivery. How those map to headcount depends on the…
Archive
Most organizations don't need four post-quantum hires. They need four capabilities: discovery, architecture, implementation, and delivery. How those map to headcount depends on the…
Cryptography hides in places no network scanner reaches. A domain-by-domain guide to finding it, and to what every inventory record has to say once…
Regulators require an inventory of cryptography your suppliers are not obliged to disclose. Four governance artifacts that close the gap and keep third-party PQC…
One network, three cryptographic primitives, five layers, five different sets of owners. Ethereum as a worked example in reading a cryptographic inventory.
NIST IR 8547 is usually reduced to 2035. It sets two dates, and the earlier one is already shaping procurement and risk acceptance decisions.
Two planners can size the same estate at 2,000 tasks and 120,000. Here is the unit to count, the ratio that catches a bad…
Scope is not what sinks a post-quantum program. Order is. A practical guide to gates, dependencies, and how to cut a migration wave that…
A payment from a phone crosses up to nine institutional boundaries. Only some of them are yours to inventory. Here is how a CBOM…
European post-quantum regulation rarely says "deploy PQC by date X." It says produce the file. Here is what that file contains, and what your…
The algorithms are settled. What stops most carriers is that nobody can yet read a cryptographic inventory and say which findings matter first.