12 months of SBOMs - an experience report
- Track: Software Bill of Materials devroom
- Room: K.4.401
- Day: Sunday
- Start: 13:30
- End: 14:00
- Video only: k4401
- Chat: Join the conversation!
The CVE Binary Tool (https://github.com/intel/cve-bin-tool) is a Python tool which helps you determine if your system includes known vulnerabilities. It takes a variety of inputs including binaries and SBOMs (both SPDX and CycloneDX are supported). Our build process has been generating a SBOM (a build/deploy version using SBOM4Python (https://github.com/anthonyharrison/sbom4python)) every week and storing it within the GitHub repo. A detailed analysis of the generated SBOMs over the past 12 months has identified a number of interesting observations which were not immediately apparent before SBOMs were being generated. It addresses some key questions such as “How much does an SBOM change and how often?“ and “ Does your SBOM depend on your environment?“. This presentation shares these observations and provides a number of recommendations to be followed when generating SBOMs as part of the build process.
Speakers
Anthony Harrison |