Cryptographic Management Modernization
Build a modern cryptographic posture management program across certificates, libraries, software, and keys. Compare iterative management practices and a conditional business case, with and without quantum-related benefits.
Why this matters: Certificate outages and unmanaged keys create present-day costs. Compare a management programme’s expected savings with its costs, including a case without quantum-related benefits; the return depends on scoped work and assumptions.
Start here: Load a sample SBOM into the Library & Hardware CBOM Builder: it becomes a crypto-focused CBOM with library end-of-life and FIPS 140-3 status, and feeds the risk engine in step 7.
For your role
- Executive / Business Leader
- The CPM Maturity Self-Assessment scores five pillars and four asset classes, and the ROI step models quantum-happens and quantum-never-happens scenarios: certificate outages and forgotten keys pay for the programme either way.
- Developer / Engineer
- The Library & Hardware CBOM Builder maps SBOMs into crypto-focused CBOMs and tracks library end of life: the inventory step where your dependencies show up.
- Security Architect
- The Inventory Lifecycle Simulator walks assets through the six-stage loop from Discover onward, and the CBOM builder covers libraries and hardware: the posture-management design in nine steps.
- Researcher / Academic
- The maturity model's five pillars and four asset classes are explicit, and the ROI model's two scenarios are parameterised, so both can be reproduced against your own estate.
- IT Ops / DevOps
- The six-stage operational loop in Step 2 is the certificate and key lifecycle you run; the maturity self-assessment in Step 1 says which stage is manual today.
Why Modernize Crypto Management Now
Quantum-safe migration gets the headlines, but four compounding forcing functions — one per crypto asset class — already bite every enterprise, whether a arrives in 2030 or never. Certificates, libraries, application software, and key material each have their own deadline; managing one without the others leaves the chain weakest at the unmanaged class.
CA/B Forum SC-081v3 (April 2025), ratified into TLS BR §6.3.2: 398d until 2026-03-15, then 200d, then 100d from 2027-03-15, then 47d from 2029-03-15. It applies to publicly trusted TLS server certificates only; private PKI, device, code-signing and document-signing certificates follow their own policies. Manual CLM breaks mathematically at this cadence.
The NIST CMVP Modules-in-Process list (checked 24 Sep 2026) lists, for each submission, the status and the date it went into that state, not an expected completion date. Plan around an issued certificate. OpenSSL 1.1.1 reached end of life on 11 September 2023.
US federal agencies must submit a prioritized cryptographic inventory, excluding national security systems, annually until 2035 or as directed by superseding guidance (M-23-02 §II.A, Nov 2022).
CNSSP 15 requires new NSS acquisitions to be CNSA 2.0-compliant from 1 Jan 2027, phases out equipment and services that cannot support CNSA 2.0 by 31 Dec 2030 unless excepted, and mandates CNSA 2.0 algorithms by 31 Dec 2031 unless otherwise noted (NSA CNSA 2.0 FAQ Ver. 2.2, October 2026). Earlier category dates remain historical context; use the current FAQ for planning.
Inventory the use of cryptography for data protection across the organization by adopting an assets-centric approach … to identify the organization’s use cases and most valuable assets, such as application codes, libraries, software, hardware, firmware, user-generated content, communication protocols, enterprise services, and systems.
— NIST CSWP.39 (upd1) §5, Considerations for Achieving Crypto Agility (December 2025, updated June 2026)
The four classes compound. A pristine certificate inventory does not save you when the underlying library is stuck in the CMVP queue; an upgraded library does not help if the application still calls a deprecated API; a clean codebase still fails audit if the keys it consumes live in an HSM that cannot rotate fast enough. Each driver below is already in force today.
- Certificates & PKI — Organizations manage an average of 114,591 internal certificates (Ponemon Institute, Trends in PKI Security: A Global Study, sponsored by CyberArk, February 2026).
- Crypto Libraries — a module on the NIST CMVP Modules-in-Process list has a status, not a completion date, and the FIPS 140-3 Implementation Guidance added self-test requirements for FIPS 203/204/205 in August 2024 and, in September 2025, let their key-generation tests check against the private key only. You cannot “audit once” and walk away.
- Application Software — OMB Memorandum M-23-02 mandates annual cryptographic-inventory submissions for US federal agencies through 2035, and EU DORA (Art. 9 — ICT risk management) and NIS2 (Art. 21 — cybersecurity measures) demand demonstrable cryptographic governance across the entire application portfolio — not just the TLS edge.
- Key Material — CNSA 2.0 forces HSM and KMS roadmaps now (new NSS acquisitions from 1 January 2027, unsupported equipment phased out by 31 December 2030); NIST SP 800-57 Pt 1 Rev 5 key-validity periods drive rekey cadence (Rev 6 is an initial public draft, not yet final); and orphaned keys, secrets-in-repo, and unrotated service credentials remain a top breach vector.
NIST CSWP.39 — The Crypto Agility Strategic Plan
NIST CSWP.39 (December 2025, updated June 2026, Considerations for Achieving Crypto Agility) defines the Crypto Agility Strategic Plan as a continuously repeated five-step process. CPM is the organisational discipline that executes this loop.
- Govern — embed crypto policy into standards, mandates, technology supply chains, threats, processes, business requirements, partner ecosystem, stakeholders, crypto policies, and crypto architecture.
- Inventory — build an asset-centric CBOM across Code, Libraries, Applications, Files, Protocols, and Systems.
- Identify Gaps — audit Management Tools for discovery, assessment, configuration, and enforcement coverage.
- Prioritise — run a Risk Analysis Prioritisation Engine informed by crypto policy to produce a ranked asset list and KPIs.
- Implement — execute Mitigation (compensating controls / crypto gateway) or Migration (algorithm replacement) based on each asset's agility level.
See the Visual tab for an interactive diagram of the full CSWP.39 Fig. 3 framework — click any zone to see what belongs there, which CPM pillar it maps to, and the relevant CSWP.39 section.
Source: NIST CSWP.39, December 2025 (updated June 2026)
The Management Tools Layer
CSWP.39 places a Management Tools layer between the asset inventory and the Risk Analysis Engine. Without automation at this layer, the Information Repository is populated manually and the risk engine operates on incomplete, stale data.
Detect algorithms, key lengths, cert details across code and traffic.
CVE feeds, crypto library EoL tracking, CMVP historical-cert alerts.
SBOM → CBOM pipelines feed the Information Repository automatically.
Detect crypto-drift events and cipher-suite anomalies in real time.
Policy engines that block disallowed cipher suites at the network layer.
Classify data assets by sensitivity; drive inventory prioritisation.
CSWP.39 Crypto Agility Maturity Tiers
CSWP.39 §6.5 defines a 4-tier maturity model derived from the NIST Cybersecurity Framework (CSF). The Workshop's Maturity Self-Assessment maps your CPM score to the corresponding CSWP.39 tier automatically.
| CSWP.39 Tier | CPM Tier | Characteristics |
|---|---|---|
| Tier 1 — Partial | L1 · Partial | Crypto practices unstructured; teams pick their own algorithms; no formal policy; supply-chain crypto risks unknown. |
| Tier 2 — Risk-Informed | L2 · Risk-Informed | Management-approved crypto policy exists but not organisation-wide; crypto architecture being developed; risk assessments drive prioritisation. |
| Tier 3 — Repeatable | L3 · Repeatable | Crypto agility formally integrated into risk management; roles defined; automated discovery and remediation tools deployed; agility practices tested. |
| Tier 4 — Adaptive | L4 · Adaptive | Crypto agility measured and reported to executives; linked to financial and mission objectives; policies updated in near-real-time as standards and threats evolve. |
CPM vs Crypto-Agility vs CryptoCOE
Vendors and analysts routinely conflate three distinct layers. The module carves them out up front so your next conversation with a product, a consultant, or your board is unambiguous.
| Layer | Scope | Question it answers |
|---|---|---|
| Crypto-Agility (LM-007) | Technical capability: abstraction layers, protocol/provider swapping | “Can we change?” |
| Cryptographic Posture Management (CPM) (this module) | Program: inventory · governance · lifecycle · observability · assurance | “Do we know what we have, is it healthy, can we prove it?” |
| Cryptographic Center of Excellence (CryptoCOE) (touched in LM-037) | Operating model — RACI, ownership, skills | “Who owns it?” |
This module's view: an organization that stands up a Cryptographic Center of Excellence and a formal posture management program is in a better position to run PQC migration as a managed program than one that treats it as a one-off project. The module gives no cost figure for this.
Four Asset Classes, One Inventory
A CPM program treats cryptography as four tightly-linked asset classes, each with its own discovery technique but rolled up under a single .
Discovery via CT-log ingest, ACME/EST/CMP inventories, internal CA enumeration, passive TLS scanning. Lives mostly in the Lifecycle pillar (CLM).
OpenSSL, BoringSSL, liboqs, WolfSSL, Bouncy Castle, Mbed TLS. Discovery via SBOM ingestion (SPDX/CycloneDX), package-manager scanning, runtime attestation. Tracked against CMVP validation status, PQC support, and CVE feeds.
Source-code crypto usage patterns (regex/AST signatures for RSA, ECDSA, MD5, SHA-1, weak RNGs) and runtime protocol inventory. Complements library tracking by catching rolled-your-own crypto.
Keys, secrets, and HSM/KMS entries. CPM tracks inventory and policy enforcement; technical depth (hierarchies, KMIP, envelope encryption) stays in LM-024 KMS & PQC.
The Five Pillars of CPM
Unified CBOM across the four asset classes. Continuously refreshed, not point-in-time.
Policy, standards, exception handling, ownership. Detailed in LM-037.
Provisioning → rotation → retirement. 47-day public TLS cert automation (ACME/EST/CMP), shadow-cert discovery, root rotation, revocation propagation.
Posture metrics, SIEM drift alerts, coverage trends. Feeds both loops of the iterative process.
Audit, attestation, CMVP validation tracking for libraries & HSMs, CAVP algorithm re-validation, IG-delta compliance.
When a validated module is revalidated, the CMVP Management Manual (section 7.1.14) marks, route by route, whether the submission must meet all the latest guidance or only the requirements of the original validation (apart from exceptions its table lists). The Assurance pillar subscribes to CMVP change notices and flags drift within the same loop as CVE triage.
An algorithm validation (CAVP, certificate numbers such as A3548) tests one algorithm implementation; NIST describes it as a prerequisite of module validation, not a substitute. A FIPS 140-3 module certificate (CMVP, for example #4985) covers one named module with its status, level, approved algorithms and caveats. An SP 800-90B Entropy Source Validation certificate (ESV, numbers such as E321) covers one entropy source and lists the operating environments it was tested on. None of the three stands in for another, so the CBOM should carry a status field for each.
Since 7 November 2020 CMVP has required module submissions to include documentation of SP 800-90B conformance where it applies, but a module certificate can still say little about key strength: certificate #4985 (OpenSSL FIPS Provider) carries the caveat “No assurance of the minimum strength of generated SSPs (e.g., keys).” Read the caveat and the Security Policy to see which entropy source the module uses and whether that source holds an ESV certificate; do not infer entropy quality from the module certificate alone.
How much randomness an operation needs is set per algorithm, not by a general rule that PQC needs better randomness. FIPS 203 requires fresh bytes from an approved RBG whose security strength is at least 128, 192 or 256 bits for ML-KEM-512, -768 and -1024 (key generation draws two 32-byte strings, encapsulation one). FIPS 204 draws a 32-byte seed for ML-DSA key generation from an RBG of at least 192 bits for ML-DSA-65 and 256 bits for ML-DSA-87. For ML-DSA-44 the minimum is 128 bits and 192 bits is advised; with less than 192 bits the claimed strength drops from Category 2 to Category 1. The random value used in hedged signing should ideally come from an approved RBG, but FIPS 204 allows other methods because its purpose is to harden against side-channel and fault attacks.
An ESV certificate names the operating environments it was tested on (certificate E321, for example, lists specific Linux images on specific processors). When the environment changes, such as a different processor, hypervisor or container image, check the certificate's operating environments and the module's Security Policy to see whether the claim still covers the new platform. This lesson does not assume that every migration triggers a new entropy assessment; the certificate and Security Policy decide.
The same CMVP change-notice subscription that tracks FIPS 140-3 Implementation Guidance updates should also track SP 800-90A/B/C revisions. When one is issued, the CBOM workflow should list which entropy sources and modules cite the superseded revision, whether the revision changes what must be re-tested, and which vendor roadmaps commit to updated ESV submissions.
Entropy & Randomness (LM-009) covers the technical depth; the CMM process obligation is to track and close the status gap.
The cryptographic posture of an organization is not defined by libraries and certificates alone. Every protocol version and cipher suite negotiated on the wire is a posture element: TLS 1.0/1.1 deprecated by (IETF) RFC 8996, 3DES sunset by (NIST) SP 800-131A Rev 2, SHA-1 code-signing banned by CA/B Forum, RSA-1024 below NIST minimum-security thresholds, RC4 prohibited by (IETF) RFC 7465. Each of these was a standards-body decision published on a specific date with a specific effective date — and organizations that had no process to track standards-body publications discovered the gap only when auditors or scanners flagged live endpoints still negotiating deprecated suites.
The CMM Assurance pillar must maintain a standards-watch subscription across the relevant bodies: IETF RFC Obsoletes/Updates, NIST SP 800-131A revision cycle, NSA CNSA suite announcements, CA/B Forum ballot outcomes, ETSI TS 119 312, BSI TR-02102, and ANSSI RGS. When a deprecation notice is published, the CBOM classification rules must be updated to flag the newly prohibited primitive, and the operational loop must trigger a discovery scan for affected endpoints, libraries, and application cipher-suite configurations. Remediation is not limited to patching a library version — it includes reconfiguring cipher-suite preference lists in TLS termination points, SSH server policies, IKEv2 proposals, and code-signing pipeline configurations, each of which may have separate ownership and change-management tracks.
The Observability pillar closes the loop: continuous protocol-version and cipher-suite scanning (passive TLS inspection, SSH banner collection, IKE proposal enumeration) ensures that deprecated primitives do not re-appear after routine infrastructure refreshes. A deprecation remediation that is not covered by ongoing detection is not a remediation — it is a point-in-time fix waiting to regress.
Crypto library CVEs introduce a constraint that generic vulnerability management does not encounter: patch-then-revalidate bind. Patching the library can leave the validated FIPS provider unchanged: the OpenSSL project lists validated provider versions 3.1.2, 3.0.9, 3.0.8 and 3.0.0 and says other OpenSSL releases “MAY use the validated FIPS provider”. Which provider build is in use, and whether it is on the validated list, therefore has to be tracked separately from the library version. The remediation workflow must treat the CVE fix and the validation status as two separate work items with separate timelines, and the CBOM must carry a “patch applied, revalidation in progress” state that is distinct from both “vulnerable” and “validated.”
For HSM firmware CVEs, the constraint is even harder: the validated firmware revision is chosen by the vendor, not the customer. There is no published timeline from CVE disclosure to a re-validated firmware release appearing on the CMVP active list: the Modules-in-Process list shows a resubmission's status and status date, not when it will finish (NIST CMVP Modules-in-Process list, checked 24 Sep 2026). During that window, the organization's options are limited to residual-risk acceptance, compensating controls, or emergency procurement of an alternate validated module. This window must be tracked explicitly in the Assurance pillar, not assumed away because the vendor has acknowledged the CVE.
The third constraint is detection prerequisite: you cannot triage a crypto CVE against components you have not enumerated. An OpenSSL 3.1.x CVE published on a Thursday morning requires knowing, within hours, which services in production are running a 3.1.x build. If CBOM completeness is below 80%, a significant fraction of the affected surface is invisible until discovered manually. CBOM completeness directly gates crypto CVE mean-time-to-detect and is therefore a security metric, not just a compliance metric.
The Dual-Loop Iterative Process
CPM is never “done.” It runs two nested loops at different cadences.
- Plan: set maturity target, refresh policy, approve budget
- Do: execute initiatives (library upgrades, CA rotation, HSM firmware)
- Check: re-run the maturity self-assessment, review KPI trends
- Act: board attestation, adjust policy and budget for next cycle
- Discover — scanners, CT logs, SBOMs, runtime agents
- Classify — HNDL sensitivity, FIPS/CNSA scope, compliance tags
- Score — risk weighting, policy-drift flags
- Remediate — tickets, automated rotation, migration PRs
- Attest — CMVP cert check, ACME renewal proof, audit evidence
- Reassess — re-discover, measure MTTR reduction, feed next iteration
Cryptographic inventory is a foundational, continuous activity — not a one-time project. Agencies should prioritize automated discovery capabilities that can run alongside existing vulnerability-management workflows.
— CISA, Strategy for Migrating to Automated PQC Discovery and Inventory Tools (Sep 2024)
CLM quarterly review: shadow-cert count trend, % certs auto-renewed, root-CA rotation readiness, 47-day-cadence simulation.
FIPS monthly monitor: CMVP validation status diff, CAVP re-validation backlog, IG-update applicability check, MIP-queue tracking.
The No-Regret ROI
Five potential operational benefit streams do not depend on CRQC arrival. Whether they outweigh programme costs depends on the selected scope and assumptions.
an illustrative assumption of ~$11M per cert-expiry event × 86% annual incidence (this module's assumption, not a sourced figure).
A DigiCert-commissioned Forrester composite model reported 312% ROI and $10.1M NPV over three years; these are modeled total-programme results, not measured CLM labour savings.
Avoided re-validation cost, preserved eligibility for federal/regulated contracts.
Faster detect → patch → attest cycles reduce exposure windows.
Unified crypto policy accelerates product launches and acquisition integration.
Study summary — Hub paraphrase
The July 2025 DigiCert-commissioned Forrester TEI models one composite organisation, with $13.3M in three-year risk-adjusted benefit present value. This total combines several benefit types; it is not annual labour savings or an established upper bound for another organisation. The workshop uses the study’s Year 1 renewal-labour amount as an editable benchmark and exposes its own projection assumptions.
Read the commissioned study and its assumptionsProgram Office Model — Who Runs CPM
A CPM program stalls when it is owned by nobody or owned by everyone. The five roles below map to pillar ownership; headcount scales with organizational complexity.
| Role | Pillar ownership | FTE — small / mid / large |
|---|---|---|
| Crypto Program Manager | All pillars (program owner) | 0.5 / 1 / 2 |
| FIPS / CMVP Engineer | Assurance | 0.5 / 1 / 2–3 |
| CLM Architect | Lifecycle | 0.5 / 1 / 2 |
| Crypto Developer Champion | Inventory + Governance | 0 / 1 per BU / 1 per BU |
| Supplier Crypto Risk Analyst | Governance + Observability | 0.25 / 0.5 / 1 |
| Pillar | Crypto PM | FIPS Eng. | CLM Arch. | Dev Champion | Supplier Analyst |
|---|---|---|---|---|---|
| Inventory | A | C | C | R | I |
| Governance | R/A | C | C | C | R |
| Lifecycle (CLM) | A | C | R | C | I |
| Observability | A | C | R | I | R |
| Assurance (FIPS) | A | R | C | I | C |
R = Responsible · A = Accountable · C = Consulted · I = Informed
Understanding CMVP submission, IG updates, MIP queue management
ACME/EST/CMP protocols, CA integration, EJBCA / Keyfactor / Venafi API depth
SBOM generation (Syft, cdxgen), CycloneDX enrichment, inventory pipeline
ML-KEM, ML-DSA, SLH-DSA parameter sets, hybrid construction tradeoffs
Reading CMVP cert scope, firmware upgrade impact analysis, re-validation timelines
OMB M-23-02, CNSA 2.0, DORA Art. 9, NIS2 — mapping requirements to CPM pillar actions
Pre-Deployment Lab Blueprint
Crypto changes — library upgrades, HSM firmware, CA rotation, cipher-suite reconfiguration — must be validated in an isolated environment before touching production. The lab below is the minimum viable configuration; scale it to your risk profile.
- 1× network-attached HSM with a named FIPS 140-3 certificate — choose a unit whose CMVP certificate names the exact module, firmware version, level and approved algorithms you plan to test, and read its status (Active, Historical or Revoked) and Security Policy. For PQC lab work, check whether the certificate lists the PQC algorithm you intend to use; if it does not, treat those operations as non-validated lab use, not as covered by the certificate. Used for key generation, signing, and firmware-upgrade testing under lab conditions; the HSM view of this module's Library CBOM Builder step shows how certificate scope is recorded.
- 1× TLS termination appliance or isolated VM (nginx / HAProxy) — for cipher-suite configuration testing and protocol-version enforcement validation.
- 1× network tap / span port — passive capture shows what the clients and servers in the captured handshakes offer and choose. In TLS 1.3 the ClientHello lists the groups and signature algorithms a client offers and the ServerHello shows what was selected, but later handshake messages, including the certificate, are encrypted (RFC 9846). Passive capture does not enumerate every suite a server supports and cannot show configured policy. Use active enumeration against the lab stack (nmap ssl-enum-ciphers, sslyze, testssl.sh connect to the server and test what it accepts; check that your version reports the key-exchange groups you need, including any hybrid group), then compare all three views (capture, scan, configuration files).
- Optional: a smart card or USB token and a representative IoT/embedded device sample for constrained-environment library validation. For any token, record the certificate number, level and mode from its CMVP entry rather than assuming a level.
- FIPS-validated library build — a validated OpenSSL FIPS provider or wolfCrypt FIPS, compiled and installed in a clean isolated test environment (separate from the OS package manager's OpenSSL).
- ACVP client + NIST ACVTS Demo — with Demo access from NIST, run the library's ACVP client against the ACVTS Demo sandbox before and after any library or HSM firmware change. Demo results are test evidence for the Assurance pillar, not a CAVP validation: only ACVTS Prod, used by accredited labs, creates algorithm certificates.
- Certificate scanner — Keyfactor Discovery, Venafi TLC scanner, or open-source tooling (crt.sh lookups + custom scripts) for shadow-cert discovery in the lab network.
- SBOM generator → CBOM enrichment pipeline — Syft or cdxgen generates CycloneDX SBOM; enrichment maps crypto components to CMVP status and PQC readiness.
- Separate test CA hierarchy — never share roots with production. Document expiry of all test CA certs; include them in the lab CBOM.
- VLAN-segregated from production; no direct internet routing (proxy only for NIST/CMVP lookups).
- HSM partition separate from any production HSM tenant; use dedicated lab slots.
- Lab credentials must not be usable in production; separate PKI roots enforces this structurally.
- Cipher-suite / protocol-version change: cipher-suite scan clean (all endpoints negotiate approved suites), testssl.sh report attached, no deprecated protocol negotiated.
- Library upgrade: CMVP cert number verified active on csrc.nist.gov for the new version; ACVP run results attached; CVE scan clean on the new version.
- HSM firmware upgrade: new firmware hash verified against vendor security advisory; CMVP cert number for the upgraded firmware confirmed active (not historical); HSM self-test passed; ACVP evidence re-run if algorithm set changed.
- CA rotation (intermediate or root): test CA hierarchy created, all relying-party systems updated and re-tested, CRL/OCSP propagation verified, expiry of new certs entered in CLM system.
- Protocol deprecation rollout: all endpoints in scope confirmed non-negotiating of deprecated protocol by passive scan; rollback procedure documented and tested; SIEM drift-alert rule updated for the new policy baseline.
PQC Maturity Models — Cross-Walk
Four frameworks independently converge on the same progression arc — from unstructured, ad-hoc crypto practices to continuous, executive-reported quantum readiness. The table aligns them by readiness band so you can map your organization across models used by different stakeholders and regulators.
| Band | CSWP.39 (4 tiers) | Meta PQC Levels (5) | CMMI (5 levels) |
|---|---|---|---|
| No awareness | Tier 1 · Partial | PQ-Unaware | Level 1 · Initial |
| Threat recognized | Tier 1 · Partial | PQ-Aware | Level 2 · Managed |
| Policy & design | Tier 2 · Risk-Informed | PQ-Ready | Level 3 · Defined |
| Tools deployed | Tier 3 · Repeatable | PQ-Hardened | Level 4 · Quantitatively Managed |
| Continuous | Tier 4 · Adaptive | PQ-Enabled | Level 5 · Optimizing |
CSWP.39 uses 4 tiers — this module's native scale. Meta and CMMI use 5 levels. CSWP.39 Tier 1 spans two Meta levels (PQ-Unaware and PQ-Aware) because the spec treats both as “Partial” practice.
Further Reading & Case Studies
Where this module sits
Pair CMM with Crypto Agility (LM-007) for the technical swap-ability side, PQC Governance (LM-037) for the operating model, KMS & PQC (LM-024) for key technical depth, and Business Case (LM-036) for quantum-dependent ROI modeling.
On this page
Related modules
- PQC Governance & PolicySame track · Governance & Risk · Shares ML-DSA, ML-KEM, SLH-DSA
- Compliance & Regulatory StrategySame track · Governance & Risk · Shares ML-DSA, ML-KEM, NIST SP 800-90B
- PQC Risk ManagementSame track · Governance & Risk · Shares ML-DSA, ML-KEM, NIST SP 800-131A
- Researcher Quantum ImpactShares ML-DSA, ML-KEM, SLH-DSA
Check your understanding
8 questions on Cryptographic Management Modernization, each with its answer and the reason.
Take the quizNext step
Produce the artifact: Management Tools AuditThis module belongs to phase 1 (Discovery & Inventory); Management Tools Audit produces a deliverable of that phase in the Command Center.
Production Tool Capabilities & Verification ChecklistEnterprise Architects, PKI/KMS Leads & Platform Directors
Capabilities to require in your production tools:
- Unified Cryptographic Management Plane integrating network TLS discovery, code/binary CBOM scanning, CLM certificate automation, and KMS/HSM key inventory.
- Automated coverage-gap detection identifying shadow certificates, unmanaged SSH keys, and EoL cryptographic libraries (e.g., OpenSSL 1.1.1).
- Shared-responsibility governance across multi-cloud KMS/HSM providers (AWS KMS/CloudHSM, Azure Key Vault/Managed HSM, GCP Cloud KMS, IBM HPCS, OCI Vault).
How to evaluate in your environment
Reconcile active network discovery scans against CLM/KMS inventories to measure real estate coverage percentage and remediate unmanaged endpoints.
Production evidence to collect
Estate coverage reconciliation report, multi-cloud KMS PQC capability matrix, and EoL library remediation tracker.
Completing this Hub module and its browser-based sample exercises teaches the technical and governance decision criteria for your role; it does not test, validate, or certify your deployed production systems.
Record evidence for your environment
Identify the tested build and configuration. Use reference IDs for observations. For a proposed exclusion, record the system boundary or rule and why it excludes this build.
Evidence missing. 0 of 3 requirements have a reference or scope rationale.
Learning module content can be inaccurate. Please double-check its information. Report inaccuracies in PQC Today GitHub Discussions.