SBOM, the Beginning of Transparency
summary
An overview of Software Bill of Materials (SBOM) as a compliance and supply-chain security tool in light of the EU Cyber Resilience Act, explaining that SBOMs should be part of project documentation and help protect against supply‑chain attacks. It describes La Poste’s choice to use Dependency‑Track to centralize and store SBOMs for internal projects to better identify vulnerabilities, and covers how to generate SBOMs automatically (including for legacy projects) and how to leverage Dependency‑Track’s features.
AI-written summary · about
chapters (15)
- 0:00SBOM and visibility
- 1:07Cyber Resilience Act
- 2:31SBOM origins
- 3:54SBOM vs XBOM
- 4:15Generating SBOM
- 5:17SBOM content risks
- 6:20SBOM standards
- 7:04SBOM in CI/CD
- 8:08Dependency-Track features
- 9:14Dependency-Track demo
- 11:20EPSS prioritization
- 12:23Policy management
- 13:05SBOM limitations
- 14:115-year traceability
- 15:16Toward XBOM
related talks
35mSBOMs: Navigating the Evolving Landscape of Software Bill of Materials
40mDBOM and SBOM: New Options For Better Supply Chain Cybersecurity
27mSBOM: The Rest Of the Story
16mKeynote: SBOM is Coming: Why You Should Care and How You Can Help
30mTransparency in the Software Supply Chain: Making SBOM a Reality
26mSBOM today: What is the state of SBOMs?
22mSBOM and Security Transparency - How it all fits together
01h 26mPractical Software Bill of Materials: From Generation to Distribution Workshop