Some recent high-profile vulnerabilities, such as Log4Shell, left many AppSec teams wondering, “Do I have vulnerable open source code in any of my apps?” Many were unsure, which illustrated perfectly the need for a Software Bill of Materials (SBOM), increasingly a must-have for those who build and use modern applications.
Developers source most of the code in their applications from the open source community and other vendors to form the basic plumbing of an application, allowing them to focus on their custom code. But with so much open source code, which in turn often includes other open source code, it’s nearly impossible to manually track what’s in an application. Without the transparent view that an SBOM delivers, organizations struggle to identify and address vulnerabilities like Log4Shell.
In this webinar, you’ll learn:
- What’s driving the need for SBOMs, including compliance mandates
- What an SBOM contains and how it’s generated
- How an SBOM increases visibility into application composition
- The value of an SBOM in real-world scenarios