What is a CBOM generator?
A CBOM generator scans software and infrastructure for cryptography and writes what it finds as a Cryptographic Bill of Materials: a machine-readable list of algorithms, keys, certificates and protocols, each with where it was found. CRYPTAGION generates CBOMs in CycloneDX 1.6, validated against the official schema, from source code, certificates and live TLS endpoints.
Inspect a pinned Python CBOM example
Two scans of 243 Python files in pyca/cryptography produced matching normalized findings and a schema-valid CycloneDX 1.6 CBOM. The evidence separates library source, tests and documentation scripts, and states the Rust coverage limits.
Explore the methodology, reviewed source evidence and downloads →
What goes into the CBOM
Unlike a single-source scanner, CRYPTAGION combines three discovery surfaces into one inventory:
- Code — Python (AST), plus JavaScript/TypeScript, Java, Go and C/C++ (static analysis).
- Certificates — X.509 in PEM, DER, CRT and CER.
- TLS endpoints — live handshake inspection (protocols, cipher suites).
Each cryptographic asset becomes a first-class CycloneDX cryptographic-asset component, with algorithm family and primitive, key size or curve, mode and padding where detected, certificate validity, and a description recording the quantum-security status and the source location (for example encrypt.go:11).
Inventory facts, kept separate from interpretation
The CBOM records what was found, in standard CycloneDX fields, with a description that keeps the source location. This component is taken unchanged from the illustrative fixture CBOM:
{
"type": "cryptographic-asset",
"name": "RSA-OAEP",
"description": "RSA padding: OAEP discovered in key_manager.py:19",
"cryptoProperties": {
"assetType": "algorithm",
"algorithmProperties": { "primitive": "pke", "padding": "oaep" }
}
}
CRYPTAGION's assessment — risk score and reasoning, data sensitivity, HNDL exposure, recommended replacement and migration year — is written to separate outputs (risk score --output, the PDF report, SARIF and the roadmap). The CBOM stays a portable, vendor-neutral inventory any CycloneDX tool can read; the interpretation stays explicit and attributable.
Validated, portable, vendor-neutral
The output is schema-validated CycloneDX 1.6 — not a bespoke format. It is portable across your tooling, it survives the vendor, and it is the same artefact auditors increasingly expect. See what a CBOM captures, with an example.
The CBOM is the evidence layer
CRYPTAGION adds context, risk, policy and migration decisions on top of that inventory — CycloneDX CBOM → cryptographic context → risk → decision → migration roadmap. It produces a per-asset quantum-risk score, a harvest-now-decrypt-later exposure analysis, a board-ready PDF, and a wave-based migration roadmap. See how that compares to open-source CBOM tooling, or what one finding looks like.
Generated inside your perimeter
The CBOM is produced where your code lives — on-prem or air-gapped, with no source code in the exported file. See deployment & data flow.
CRYPTAGION supports compliance activities; use of the product does not by itself establish regulatory compliance.
CBOM generator: frequently asked questions
What is a CBOM?
A cryptographic bill of materials (CBOM) is a machine-readable inventory of the cryptographic assets in your systems, with where each one was found. It is the cryptography counterpart of an SBOM. See what a CBOM captures, with an example.
What is the difference between a CBOM and an SBOM?
An SBOM tells you which libraries you ship. A CBOM tells you which cryptography you use, where, and with which parameters. A hard-coded RSA.generate(1024) in your own code is not a component, so an SBOM cannot see it; a CBOM records it. The two are complementary. See CBOM vs SBOM, side by side.
Why CycloneDX 1.6?
CycloneDX 1.6 has first-class cryptographic-asset components, so a CBOM is an open-standard file rather than a vendor format. CRYPTAGION validates every export against the official schema, so your GRC tooling can ingest it and it stays usable if you stop working with us.
What is in a CRYPTAGION CBOM, and what is not?
Each cryptographic asset, with algorithm family and primitive, key size or curve, mode and padding where detected, certificate validity, and a description recording its quantum-security status and source location. Risk scores, data sensitivity and migration recommendations go into separate outputs (the PDF report, SARIF and the roadmap), and no source code is included in the file.
Can we generate a CBOM on every commit?
Yes. In CI/CD, discovery runs in the pipeline so source code never leaves the runner. It produces a CycloneDX 1.6 CBOM on every change, can fail the build when new broken or quantum-vulnerable cryptography breaches your policy, and writes SARIF for code-scanning tools.
How does this compare with open-source CBOM tools?
Open-source CBOM tools generate a cryptographic inventory; they are free, capable and the right call if you have the in-house expertise to assemble and maintain them. CRYPTAGION uses the same open standard and adds per-asset quantum-risk scoring, HNDL exposure, a board report and a migration roadmap. We published a head-to-head with CBOMkit on two real repositories, including where CBOMkit found more than we did. See also when to use which.
Want to see a real CBOM generated live? We scan a public repository that matches your stack in the call — no payment until you’ve seen it work.
Request a free demo →