Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› CBOM
Cyber Security

CBOM

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

CBOM is a cryptographic bill of materials that inventories algorithms, certificates, protocols, and related crypto assets. It is used to identify weak or outdated cryptography, support policy enforcement, and plan migration to stronger or post-quantum primitives.

What CBOM Covers and Why It Matters

CBOM turns cryptography into an inventoryable asset class. By listing algorithms, certificates, protocols, keys, and related crypto components, it gives teams a practical view of where cryptography is used, which primitives are present, and which dependencies may become obsolete, weak, or non-compliant over time.

That matters because crypto risk is often hidden in transitive dependencies, legacy services, and configuration drift. A CBOM helps organisations move from assumptions such as “we use strong crypto” to evidence about what is actually deployed across applications, platforms, and integrations.

What a CBOM Typically Records

A useful CBOM is broader than a certificate list. It normally describes the cryptographic algorithms in use, the protocols or transport layers that rely on them, and the certificates or other crypto assets tied to specific systems, services, or products. In practice, this creates a searchable record of crypto posture rather than a one-time snapshot.

Because cryptography changes over time, the inventory has to stay current. New libraries, updated protocol settings, or newly issued certificates can all change the security profile of the environment. That is why CBOMs are most valuable when they are maintained as part of operational governance, not treated as static documentation.

How CBOM Supports Weak-Crypto Discovery and Migration

CBOM is especially useful for finding outdated or fragile primitives before they become incidents. It helps security teams identify where older algorithms, weak key sizes, or soon-to-be-retired protocols are still embedded, and then prioritise remediation by business criticality, exposure, and replacement complexity.

It is also a migration tool. When organisations plan upgrades to stronger cryptography or post-quantum primitives, a CBOM makes it easier to assess blast radius, find dependencies that need testing, and sequence changes in a controlled way. That is why CBOM is closely related to Cryptographic Inventory and CBOM Guide and Post-Quantum Cryptography Migration Guide.

For certificate-heavy environments, the same inventory logic also supports planning around Post-Quantum Readiness for Identity and PKI, where cryptographic dependencies affect authentication, signing, and trust chains.

Operational Challenges and Limitations

CBOMs are only as good as the discovery behind them. Dynamic cloud workloads, embedded libraries, managed services, and shadow IT can all hide crypto use from manual review. If the inventory misses those assets, the organisation may falsely believe it is ready for deprecation deadlines or post-quantum migration.

A second limitation is interpretation. A CBOM tells you what is present, but not by itself whether the implementation is correctly configured, whether the certificate is trusted everywhere it should be, or whether the system depends on a crypto component in an unexpected way. It is a decision-support artifact, not a complete assurance mechanism.

Risk and Threat Considerations

CBOM reduces blind spots, but gaps in the inventory create real exposure. If weak algorithms, long-lived certificates, or outdated protocols are not discovered early, organisations can carry insecure crypto into production, delay migration, or miss the systems most likely to fail when a primitive is deprecated.

Failure mechanism: Incomplete discovery, stale records, or unmanaged dependencies leave weak cryptography hidden in applications, libraries, and services, which can produce avoidable exposure, failed migrations, or trust breakdowns when crypto policy changes.

Impact: The result can be continued use of vulnerable primitives, delayed remediation, and higher operational risk during crypto transitions, especially where certificates, signatures, or transport security are business-critical.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-57, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-57NIST-800-57 — Key ManagementCBOM tracks cryptographic assets that must be rotated, retired, and migrated.
Recommendation — Use key lifecycle guidance to inventory cryptographic dependencies and plan rotation or retirement.
NIST SP 800-53 Rev 5SC-13 — Cryptographic ProtectionCBOM supports identifying where cryptographic protection is deployed and where weaker primitives persist.
CM-8 — System Component InventoryCBOM is an inventory of crypto components and dependencies that must stay current.
IA-5 — Authenticator ManagementCertificates and other crypto assets in a CBOM often support authenticators and trust material.
Recommendation — Document crypto use and verify protected data paths use approved cryptography. Maintain an authoritative inventory of cryptographic components and their dependencies. Track cryptographic authenticators and manage their lifecycle before they expire or weaken.
NIST CSF 2.0ID.AM-01 — Physical Devices and Systems InventoryCBOM extends asset inventory by identifying cryptographic components across the environment.
Recommendation — Include cryptographic components in your asset inventory and keep the record current.

Practitioner Guidance

Why practitioners should care: CBOM is most valuable when it becomes part of normal security operations, not a one-off compliance exercise. Owners need a repeatable process for discovering crypto assets, mapping them to services, and keeping the inventory aligned with configuration and certificate change.

Governance implication: Treat CBOM ownership as shared across security, platform, and application teams so that policy decisions about allowed algorithms, renewal cycles, and migration priorities are backed by current evidence rather than assumptions.

Practitioner takeaway: The practical test for CBOM is whether it helps you answer, quickly and with confidence, where cryptography exists today and what must change before the next policy or platform shift.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org