How to generate deterministic CycloneDX 1.5 SBOMs, enrich transitive dependencies against OSV.dev, CISA KEV, and EPSS, and record auditable VEX exploitability states.
Deterministic Compliance Checklist
Generate CycloneDX 1.5 JSON SBOMs directly from lockfiles (package-lock.json, poetry.lock, Cargo.lock, go.sum) or GitHub repositories.
Cross-reference every Package URL (PURL) against OSV.dev advisories, CISA KEV, and EPSS exploitability scores.
Attach OpenVEX / CycloneDX VEX states (not_affected, affected, fixed, under_investigation) with written justification.
Seal the SBOM and audit report with an HMAC-SHA256 cryptographic digest for Annex VII technical documentation.
Frequently Asked Questions
Why combine SBOMs with VEX (Vulnerability Exploitability eXchange)?
An SBOM lists all components, while VEX proves which CVEs are actually reachable or mitigated in your runtime context—preventing false-positive compliance blockers.