You got a SBOM!  But is it the right one?

Anthony Harrison, APH10 & SBOMeurope

In today’s increasingly regulated software landscape, Software Bill of Materials (SBOM) have emerged as a crucial tool for understanding the components within our applications. However, simply having an SBOM isn’t always enough. Just as a hammer is great for nails but not for screws, an SBOM’s utility in meeting the intended use cases is tied to the type of SBOM as not all SBOMs are created equal. Using the wrong type of SBOM for your intended use case can leave you and your customers exposed or, at best, working with incomplete or irrelevant information and doesn’t contain the correct information appropriate to the intended use cases.

SBOMs can be created throughout the secure development lifecycle and are represented by six types of SBOMs, each offering a unique perspective on your software’s composition at different stages of its lifecycle. Understanding these distinctions is key to maximising their value and selecting the right tool.

By breaking down each type of SBOM and exploring what use cases they are best suited for, this session will enable you to ensure that have the correct information to support your risk management process particularly when working with the supplychain.