The two papers, “Types of SBOM” and “Minimum Requirements for Vulnerability Exploitability eXchange (VEX)”.
The Types of SBOM document summarizes common types of SBOMs that tools may create in the industry today, along with the data typically presented for each type of SBOM. As software goes from planning to source to build to deployed and used, tools may be able to detect subtle differences in the underlying components. These types will allow for better differentiation of tools and in the broader marketplace.
Today there is a widely used definition of the minimum content of a Software Bill of Material (SBOM). However, an SBOM may contain different forms of the minimum information sourced from different product artifacts. Given the disparate ways SBOM data can end up collected, tool outputs may vary and provide value in different use cases. This document summarizes some common types of SBOMs that tools may create today, along with the data typically presented for each type of SBOM. An SBOM document may combine information for multiple SBOM types.
This document is a starting point for clarifying SBOM types that varying tooling types and methods may create. Different tooling approaches may create the same SBOM type for different kinds of software. This document may evolve as the innovation around SBOMs and their uses may require the addition of more SBOM types.
Click here for the entire “Types of SBOM document.”
In the other document called the “Minimum Requirements for VEX document” specifies the minimum elements to create a VEX document. This will allow interoperability between different implementations and data formats of VEX. It will also help promote integration of VEX into novel and existing security tools. This document also specifies some optional VEX elements.
VEX indicates the status of a software product or component with respect to a vulnerability. A common VEX use case is to indicate where software is suffering from a vulnerability.
At its core, a VEX data format is a machine-readable collection of information conveying the status of products or components with respect to a vulnerability. As VEX implementation occurs across the diverse software ecosystem, the community sought to further define and specify the needed and optional elements to support automation, tooling, and interoperability.
VEX can integrate with SBOM, vulnerability databases, and security advisories, but does not require any of these. VEX documents can be from the supplier of the software or by a third party.
As practical implementation of VEX continues, changes to the minimum elements will occur. Elements may be added, removed, or changed, but the minimum requirements should allow for scalable implementations and should harmonize the community’s expectations.
Click here for the entire “Minimum Requirements for VEX document.”

