Generate a CBOM for every cryptographic asset you ship
Scan source, dependencies, containers and cloud infrastructure to generate a continuous, audit-ready Cryptographic Bill of Materials in CycloneDX. Built for post-quantum migration and for CERT-In, RBI and SEBI mandates.
Complete infrastructure coverage
O3 CBOM automatically discovers and inventories every algorithm, key, certificate, protocol, and secret across your entire infrastructure.
Source Code
— —— —
Container Images
— —— —
Live Databases
— —— —
Cloud Infrastructure
— —— —
Hardware Security Modules
— —— —
Web Servers & Network
— —— —
TLS Certificates
— —— —
Software Libraries
— —— —
Every asset type, one inventory
What O3 CBOM discovers and inventories, grouped the way CERT-In and RBI define cryptographic scope. A single scan covers all seven domains.
Applications and source
Cipher and hash calls, key material, certificate pinning and hard-coded parameters across 18 programming languages, parsed with full syntax-tree analysis.
Enterprise languages
- Java
- Kotlin
- C#
- Go
- Python
- Rust
- C / C++
- Swift
Web and scripting
- JavaScript
- TypeScript
- PHP
- Ruby
Smart contracts and DLT
- Solidity
- Move
- Cairo
- Func
- Daml
Compiled artifacts
- Android APK / AAB / AAR
- Java JAR / WAR / EAR
- .NET DLL / EXE
One inventory, wherever the cryptography lives
Cryptography does not sit in one place, and the parts that decide what your systems actually negotiate are rarely in the codebase. Each area below is inventoried into the same report, and most need far less access than teams expect.
Applications and services
Where your own code calls cryptography — the algorithms, key sizes and certificate handling written into the services you build and ship.
What it takes from your team
Read-only. Nothing is installed on your hosts and no code changes are needed.
What it surfaces
- Every place a quantum-vulnerable algorithm is used, down to the exact location
- Key sizes and modes that fall below policy
- Certificate pinning and hard-coded parameters that break silently on rotation
Every finding says how it knows
Each component in the inventory is stamped with the strength of the evidence behind it. The tag is a standard CycloneDX property, so auditors and downstream tools can filter on it directly.
The scanner saw it
Proven directly from the artifact — a syntax-tree match in real source, a live TLS handshake, or an attribute read from an HSM or cloud KMS. Carries the file and line, or the endpoint, it came from.
Present, but not exercised
Listed in a manifest, dependency graph or configuration. The presence is known; the actual use is not proven, so it is never counted as verified.
Fingerprint-matched code
Function bodies match a known library above the overlap threshold, with no manifest entry declaring it. Evidence of vendored or forked crypto code, short of proof of an exact release.
Asserted by a third party
A claim from a custody provider, signing service or bank rail, via attestation or questionnaire. Recorded so the fact is in the inventory, explicitly marked as not independently verified.
What most CBOM tools miss
Most cryptographic inventories are built from source code and dependency manifests. That covers the cryptography an application declares, and misses the infrastructure that decides what it actually negotiates.
Observed cryptography, not just declared
Common approach
Most CBOM tooling reads source and manifests. It reports the cryptography a codebase declares, and stops there.
O3 CBOM
O3 also reads TLS handshakes off a packet capture and reports what two real systems actually negotiated, including service-to-service traffic that never passes a gateway. A configuration file cannot tell you a server quietly fell back to TLS 1.0. A capture can.
The infrastructure that sets the real crypto floor
Common approach
Source-centric scanners skip the gateway, the load balancer and the network device, because none of them are code.
O3 CBOM
F5 BIG-IP, Citrix NetScaler, HAProxy, Kong, APISIX, Envoy, Istio, Cisco IOS and Juniper JunOS are parsed as first-class assets. A gateway sets the effective TLS policy for every service behind it, so leaving it out understates the estate.
Evidence strength on every component
Common approach
Tools commonly merge a vendor questionnaire answer, a manifest entry and a proven code path into one undifferentiated list of findings.
O3 CBOM
Every component is stamped verified, declared, structural-match or vendor-attested, as a standard CycloneDX property. An auditor can filter for what the scanner actually proved, and a vendor assertion is never laundered as fact.
Post-quantum exposure with a date on it
Common approach
A quantum-risk view that labels algorithms safe or unsafe tells you what you already suspected.
O3 CBOM
O3 models harvest-now-decrypt-later against how long your data must stay secret. Data with a 15-year confidentiality requirement encrypted under RSA-2048 is exposed today, not in 2035 — and passive capture reports which servers declined a post-quantum key exchange the client already offered.
Regulator field sets, not a generic export
Common approach
A CycloneDX export satisfies the format and leaves the mapping to the compliance team.
O3 CBOM
All four CERT-In field sets — algorithms, keys, protocols, certificates — are populated out of the box, alongside the Indian payment rails (NEFT, RTGS, IMPS, UPI, RuPay, AePS) and the SWIFT CSCF controls that BFSI audits ask about by name.
The same inventory, in your regulator’s language
Select the jurisdiction you operate in and the inventory is assessed against the instruments that actually bind you, each cited to its source and marked as a mandate, guidance or permission.
India
CERT-In field sets, RBI obligations and the NPCI rails, each cited to the specification or circular that imposes it.
CERT-In
All four mandated field sets — algorithms, keys, protocols and certificates — populated in every inventory.
RBI
Cryptographic inventory obligations, including the Master Direction on Cyber Resilience for payment system operators.
SEBI CSCRF
Applied to core banking and market infrastructure systems.
NPCI rails
UPI credential-block encryption, RuPay, and AePS mapped to the UIDAI device specification that governs it.
Know your quantum risk before it becomes a breach
Identify vulnerable legacy algorithms and map immediate migration paths to post-quantum standards across all infrastructure assets.
All CERT-In Parameters. Out of the Box.
Every data point mandated by CERT-In for CBOM - across algorithms, keys, certificates, and protocols - is automatically captured and included in every inventory O3 generates.
Built for Compliance From the Ground Up
Every operational requirement defined by CERT-In — not just the data fields, but how the CBOM is generated, shared, stored, and audited.
Running in minutes, not days
No agents on your hosts, no instrumentation, and no changes to application code. The first inventory is produced on day one, and every one after that happens on its own.
A full inventory
Point it at an environment and get a complete cryptographic inventory, classified to the domains a regulator asks about.
Kept current automatically
The inventory refreshes with your pipeline, so it reflects what is deployed now rather than what was true at the last audit.
Change you can see
New, removed and downgraded cryptography is reported against the previous inventory, and policy breaches are flagged before release.
Ready to Get Compliant?
Book a demo with our team and see O3 Security CBOM give you a clear picture of your compliance gaps, quantum exposure, and what it takes to get audit-ready.
What a CBOM tool has to detect
A CBOM tool has to find the cryptography your systems actually use: the algorithms, key lengths, certificates, protocols, and the libraries that implement them. A useful one can answer “where are we using RSA, and at what key size?” across the whole estate, without a manual search of every repository.
It works like an SBOM, but narrower: instead of listing every package, it records each place a cryptographic primitive is used, so the estate can be reviewed as one inventory.
Read the full CBOM guide for the deeper walkthrough — formats, tooling, and how it fits alongside an SBOM.
Why does a CBOM matter for post-quantum migration?
Post-quantum migration starts with knowing where the quantum-vulnerable algorithms are: RSA, ECC and Diffie-Hellman. A CBOM provides that inventory. CNSA 2.0 expects the move to be well underway this decade.
With the inventory in place, migration can be prioritized by exposure. O3 feeds the CBOM into your quantum readiness picture so you can work outward from the highest-exposure systems first.
Why SBOM tooling alone will not cover this
An SBOM tells you which crypto library you depend on — say, OpenSSL 3.0. It does not tell you that one service still negotiates TLS with a 1024-bit key, or that a batch job signs tokens with SHA-1. The CBOM records that usage layer: which algorithms are called, with what parameters, and where.
How does O3 build the CBOM?
O3 scans source, dependencies, and configuration to find cryptographic usage, then normalizes it into a standard CBOM so every algorithm, key, and certificate sits in one inventory with its location and risk. No agents to install on every host.
It then maps each finding to the frameworks that require it, so the same inventory serves audits directly. See the full set of BOM compliance mappings.
Explore the full O3 BOM Suite
One platform for every bill of materials — software, cryptographic, AI, hardware and quantum — unified for supply-chain visibility and compliance.
- SBOM — Software Bill of MaterialsGenerate and continuously verify SPDX/CycloneDX SBOMs across your build pipeline for CRA and EO 14028.
- AIBOM — AI Bill of MaterialsTrack every model, dataset, and external inference endpoint your apps call — the inventory the EU AI Act expects.
- HBOM — Hardware Bill of MaterialsMap firmware and hardware components to surface supply-chain risk down to the silicon.
- QBOM — Quantum Bill of MaterialsCatalog post-quantum readiness across your cryptographic estate as you migrate to PQC.
- BOM ComplianceSee how SBOM, CBOM, AIBOM and HBOM map to CRA, CERT-In, SEBI, FedRAMP and other frameworks.
- xBOM — the full family comparedSBOM vs CBOM vs AIBOM vs QBOM vs HBOM side by side: what each inventories, the question it answers, and when you need more than one.