Machine-readable SBOM
Manufacturers of products with digital elements document their components in an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies — and use it to handle vulnerabilities.
VamiAppSec generates a CycloneDX or SPDX SBOM in every pipeline run, stores it with the release and keeps matching every shipped component against vulnerability and exploitation data — so you know which products are affected long after they left the build. Reachability checks and VEX drafts tell customers and authorities what really matters.
Regulators, notified bodies and customers ask for SBOMs — but a file generated once is outdated the day a new vulnerability is published. Four requirements shape what an SBOM process has to deliver:
Manufacturers of products with digital elements document their components in an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies — and use it to handle vulnerabilities.
Notified bodies expect an inventory of software of unknown provenance (SOUP) and third-party components, plus vulnerability monitoring across the product lifecycle.
OEMs and operators ask suppliers for SBOMs and want to know whether a published CVE affects the version they run — ideally as a VEX statement rather than a spreadsheet.
Vulnerabilities are disclosed after release. An SBOM only helps if it is versioned per release and checked again whenever new advisories or evidence of exploitation appear.
Every step leaves a record — per product and per release.
| Task | How VamiAppSec does it | Result per release |
|---|---|---|
| Generate build stage | Syft builds CycloneDX and SPDX SBOMs in the pipeline, with direct and transitive dependencies. | SBOM stored with the release |
| Sign and version release gate | The pipeline checks SBOM completeness; the SBOM is signed and versioned with the release, together with VEX and VDR. | Signed SBOM, VEX and VDR |
| Match vulnerabilities continuous | Every released SBOM is matched against NVD, OSV and GitHub advisories; dependencies are also scanned with Grype and Trivy. | Current vulnerability list for each release |
| Detect active exploitation CISA KEV · ENISA EUVD | Exploitation signals from CISA KEV and ENISA's EU Vulnerability Database, prioritised with EPSS. | Alert for the affected products and releases |
| Assess reachability LLM-assisted | The LLM checks whether the vulnerable code path is reachable in your product and drafts the VEX status; your PSIRT decides. | VEX draft: affected, not affected, fixed or under investigation |
| Share and report exports | CycloneDX / SPDX via REST API, VEX / VDR exports and — for actively exploited vulnerabilities — the CRA Art. 14 report drafts. | Exports for customers, auditors and authorities |
The SBOM is created where the software is built and stays connected to the release it describes.
Syft runs in the build stage and records every direct and transitive dependency of the artifact you ship.
The pipeline checks SBOM completeness; the signed SBOM, VEX and VDR are stored with the release.
New advisories and exploitation signals are matched against every released SBOM — not just the latest build.
Affected findings land in DefectDojo or your ticket system; VEX drafts and, where needed, CRA report drafts are prepared.
Matches are tracked per product and release, so you can answer "are we affected?" for every version still in the field.
On T Cloud Public, exclusively in German data centers operated by Deutsche Telekom.
The full stack on your own Kubernetes cluster — useful when SBOMs reveal sensitive product architecture.
SBOMs in CycloneDX and SPDX, available per release and via the REST API — no proprietary format.
An SBOM is a means, not the goal: VamiAppSec automates generation, monitoring and VEX drafts, while decisions about affectedness and disclosure stay with your PSIRT.
A software bill of materials lists the components a product is built from — libraries, frameworks and their versions, including transitive dependencies. It is the basis for answering whether a newly published vulnerability affects your product.
CycloneDX and SPDX — the two widely used machine-readable formats that guidelines such as BSI TR-03183-2 refer to. VamiAppSec generates them with Syft and makes them available per release and via the REST API.
Yes. Annex I, Part II requires manufacturers to identify and document components, including an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies. It does not have to be published. More in CRA compliance with VamiAppSec.
The SBOM lists what is in the product. A VEX (Vulnerability Exploitability eXchange) statement says whether a specific vulnerability actually affects it: affected, not affected, fixed or under investigation. VamiAppSec drafts VEX statements from the reachability check; your PSIRT confirms them.
Yes. Every released SBOM stays under monitoring, so you can see which versions in the field are affected — not only the latest build.
Yes. The same per-release SBOM serves as the SOUP and third-party inventory for MDR and IEC 81001-5-1 and as supplier transparency for UNECE R155 and ISO/SAE 21434 — VamiAppSec maps findings to these frameworks.
We connect a sample repository, generate the SBOM for a release and show you the exploit monitoring, the reachability check and the VEX export.