Every month there seems to be a new software vulnerability showing up on social media which causes open source program offices and security teams to start querying their inventories to see how FOSS components they use may impact their organizations.
Frequently this information is not available in a consistent format within an organization for automatic querying and may result in a significant amount of email and manual effort. By exchanging software metadata in a standardized software bill of materials SBOM format between organizations automation within an organization becomes simpler accelerating the discovery process and uncovering risk so that mitigations can be considered quickly.
In the last year weve also seen standards like OpenChain ISOIEC 53202020 gain adoption in the supply chain. Customers have started asking for a bill of materials from their suppliers as part of negotiation and contract discussions to conform to the standard. OpenChain has a focus on ensuring that there is sufficient information for license compliance and as a result expects metadata for the distributed components as well. A software bill of materials can be used to support the systematic review and approval of each components license terms to clarify the obligations and restrictions as it applies to the distribution of the supplied software and reduces risk.