Software Bill of Materials (SBOM) Consumer Use Cases
Reduce the risk of open-source and third-party code interfering with your environment with a software bill of materials (SBOM).
As evidenced by some of the most significant cyberattacks in the last few years — from Solar Winds and Kaseya to Colonial Pipeline and the ongoing repercussions of Log4j — supply chain attacks are becoming an even greater threat to today's organizations.
In response to this new world of unverified trust and indirect attacks, the U.S. government issued Executive Order (EO) 14028 in May 2021. One of the most sweeping pieces of presidential policy on cybersecurity, EO 14028 addresses the critical role of improved software supply chain security and the need for more transparency. This includes requiring suppliers to provide an SBOM to downstream organizations and software developers.
In this whitepaper, you’ll learn:
- The role SBOMs play in software development and security
- What to do with SBOMs after you receive them
- How to use SBOMs in procurement
- SBOM use cases