NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Products›CBOM

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.

cryptographic_inventory.json
// Audit summary of cryptographic assets
{
"totalAssets": 672,
"algorithms": {
"secure": ["AES-256", "ML-KEM"],
"deprecated": ["SHA-1", "MD5"]
},
"keys": {
"rsa_2048": 12,
"ecc_p256": 48
}
}
CRYPTO RADAR
PQC READY
94%
Overall Security ScorePost-Quantum AlignedFIPS 203/204 Compliant
AlgorithmsSecure
ML-KEM · AES-256 · ML-DSA
Risk Assets2 Legacy
SHA-1 · MD5 (Flagged for migration)
Key ProtectionHSM
612 keys stored in secure KMS
Discovery Engine

Complete infrastructure coverage

O3 CBOM automatically discovers and inventories every algorithm, key, certificate, protocol, and secret across your entire infrastructure.

QUEUED

Source Code

— —

SCANNED

Source Code

4,128 algorithms

QUEUED

Container Images

— —

SCANNED

Container Images

11,402 images

QUEUED

Live Databases

— —

SCANNED

Live Databases

14 databases

QUEUED

Cloud Infrastructure

— —

SCANNED

Cloud Infrastructure

84 resources

QUEUED

Hardware Security Modules

— —

SCANNED

Hardware Security Modules

612 keys

QUEUED

Web Servers & Network

— —

SCANNED

Web Servers & Network

8,917 endpoints

QUEUED

TLS Certificates

— —

SCANNED

TLS Certificates

1,204 certs

QUEUED

Software Libraries

— —

SCANNED

Software Libraries

2,491 libraries

SCAN.RUN
0%
Supported Assets

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
Across the estate

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
Evidence

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.

Verified

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.

Declared

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.

Structural match

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.

Vendor attested

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.

Why O3

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.

Regulatory mapping

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.

Quantum Readiness

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.

#AssetRisk LevelPQC StatusVulnerableMigration Path
01
RSA-2048
auth-svc / jwt
CriticalDeprecatedYESML-DSA-65
02
ECDSA-P256
tls / edge
HighDeprecatedYESML-DSA-65
03
3DES
legacy-db / storage
CriticalDeprecatedYESAES-256-GCM
04
SHA-1
web / legacy-signature
HighDeprecatedYESML-DSA-87
Cryptographic Reference

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.

Secure your Algorithms

ParametersO3 Supports
Name
The name of the cryptographic algorithm or asset, such as "AES-128-GCM".
Asset Type
Specifies the type of cryptographic asset. For algorithms, the asset type is "algorithm".
Primitive
Describes the cryptographic primitive, such as "signature" or "hash".
Mode
The operational mode used by the algorithm, such as "gcm" or "cbc".
Crypto Functions
The cryptographic functions supported by the asset, such as encryption and decryption.
Classical security level
The strength of the asset in terms of its resistance to classical attacks (e.g. 128 bits).
OID
Globally unique Object Identifier (OID) used to distinguish algorithms across systems.
List
Lists all cryptographic algorithms employed by a device or system for security audits.
Compliance & Audit

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.

CI / CD

Runs in every pipeline.

Automatic on every push — no manual triggers, no gaps between deployments.

Push
→
Build
→
Scan
→
Ship
Access Control

Role-based views.

Separate views for security teams, compliance officers, and auditors.

SSecurity
scoped
CCompliance
scoped
AAuditor
scoped
Standards

SPDX & CycloneDX.

Industry-standard formats accepted by regulators and supply-chain partners.

SPDX
CycloneDX
Export

JSON & CSV.

Audit-ready exports — ready for your auditor or regulator.

cbom.json
{
"algorithm": "SHA-1",
"status": "deprecated"
}
Sharing

Public & private BOMs.

Share with regulators without exposing internal details. Granular disclosure.

PUBLIC
PRIVATE
Ingestion

Source & build output.

JARs, .NET assemblies, Android packages and container images — assets that only appear after the build.

SOURCE
.go.py.ts.java
BINARY
.jar.bin.dll
Versioning

Every CBOM, versioned.

Full history of how your cryptographic posture has changed over time — immutable and auditable.

v2.1 (Active)
now
v2.0Jul 09
v1.2Apr 28
Data Residency

Stored inside India.

Three sovereign data centers meet localization requirements for BFSI entities.

Mumbai
ap-south-1
Chennai
ap-south-2
Deployment

Multiple deployment options.

Deploy as SaaS or on-premise depending on your organization's data policies and infrastructure requirements. Full support for air-gapped secure local environments.

SaaS CloudFully Managed
On-PremSelf-Hosted
HybridSaaS + On-Prem
Rollout

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.

Day one

A full inventory

Point it at an environment and get a complete cryptographic inventory, classified to the domains a regulator asks about.

Every build

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.

Every release

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.

Evaluating a CBOM tool

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.

FAQ

Questions,
answered.

Everything teams ask before rolling this out. Still stuck? Reach our team.

  • Application source in 18 programming languages; API gateways and load balancers including F5 BIG-IP, Citrix NetScaler, HAProxy, Kong, Apache APISIX, AWS ALB/NLB, Azure Application Gateway and Google Cloud Load Balancing; ingress and service mesh including Kubernetes ingress-nginx, Envoy, Istio and Linkerd; network devices running Cisco IOS and Juniper JunOS; hardware security modules from Thales, Entrust, Utimaco and SafeNet plus KMIP key managers; cloud key services across AWS KMS, Azure Key Vault and Google Cloud KMS; container images; databases with transparent data encryption; IBM z/OS mainframe applications written in COBOL and PL/I; live TLS endpoints; and passively observed network traffic.
  • Yes. A gateway or load balancer sets the effective cryptographic floor for every service behind it, so its TLS policy belongs in the inventory as a first-class asset. O3 inventories the protocol versions and cipher suites each listener accepts, the certificates and keys the device holds, and policy drift between environments. An exported configuration is enough — no control-plane credentials, no agent, and no change to the device. Endpoints can also be scanned live where no configuration is available.
  • Every component carries an evidence disposition recorded as a standard CycloneDX property, so an auditor can filter on what was actually proven. Verified means the scanner observed it directly — a syntax-tree match in real source, a live TLS handshake, or an attribute read from an HSM or cloud KMS. Declared means it appears in a manifest, dependency graph or configuration but its use is not proven. Structural match means function bodies matched a known library above an overlap threshold, indicating vendored or forked cryptographic code. Vendor attested means a third party asserted it and the scanner did not observe it. A vendor assertion is never reported as a verified fact.
  • Yes. Jurisdiction is a scan-level setting, and the obligations assessed change with it. India covers CERT-In, RBI, SEBI CSCRF and the NPCI rails. The European Union covers NIS2 Article 21, GDPR Article 32, eIDAS for qualified trust service providers, and the EU post-quantum roadmap with its 2026 and 2030 milestones. Brazil covers BACEN instruments, PIX participant requirements and ICP-Brasil. The United States covers FFIEC examination guidance plus state law including New York NYDFS Part 500, Massachusetts and Nevada. Card schemes including PCI DSS v4.0.1, PCI PIN and SWIFT CSCF apply across jurisdictions. Each finding is cited to its source instrument and marked as a mandate, guidance or permission.
  • A CBOM is an inventory of every cryptographic algorithm, key size, library, and protocol used across your codebase, dependencies, containers, and cloud infrastructure. It lets security teams identify quantum-vulnerable algorithms like RSA-2048 and plan migration to NIST-approved post-quantum cryptography (PQC) standards before quantum computers break current encryption.
  • NIST and leading cryptographers estimate cryptographically-relevant quantum computers capable of breaking RSA-2048 could arrive between 2030 and 2035. Organizations need to complete crypto migrations before that window. CBOM discovery is the mandatory first step to understand scope and prioritize migration.
  • O3 inventories cryptography across application code, dependencies, container images, cloud key services, hardware security modules and network infrastructure such as API gateways and load balancers. Every finding is classified by evidence strength and mapped to the regulatory domains an audit asks about, with a prioritized migration roadmap and break-year estimates.
  • In India, CERT-In mandates a CBOM with four defined field sets, and RBI and SEBI CSCRF impose cryptographic inventory obligations. The EU Cyber Resilience Act and the EU post-quantum roadmap recommend cryptographic asset management, with NIS2 Article 21 requiring cryptography policies. In the United States, NSA CNSA 2.0 and Executive Order 14028 set transition expectations, and NYDFS Part 500 imposes prescriptive encryption requirements. PCI DSS v4.0.1 and PCI PIN govern card and PIN cryptography for any entity handling cardholder data. O3 maps findings to each of these, along with NPCI rail requirements, SWIFT CSCF controls, Brazil BACEN and ICP-Brasil, and FFIEC examination guidance.
  • An SBOM (Software Bill of Materials) lists software components and their known CVEs. A CBOM specifically inventories cryptographic algorithms, key sizes, and protocols, including ones with no CVE but that are quantum-vulnerable. Both are complementary: SBOM for dependency risk, CBOM for cryptographic risk.