Software bill of materials (SBOMs) is something the industry needed since the creation of software programs. Afterall, with all the open source code that goes into software builds, there should be a listing of what is in the final product.

Software users should understand what “ingredients” end up contained in their software package and if there are any vulnerabilities attached. Plus, you can add on top of that, the 2021 Executive Order mandating the supply of SBOMs for all “critical software.” So, starting in 2024, if you sell systems to the U.S. federal government, you must provide SBOMs with your software. And that does not even get into the requirements of when you sell software into a critical infrastructure organization.

Software producers, such as product manufacturers and integrators, often need to assemble and test a set of products together before delivering to their customers. This set of products may contain components that undergo version changes over time and need to undergo tracking.

To that end, the Cybersecurity and Infrastructure Security Agency (CISA) published Guidance on Assembling a Group of Products created by the Software Bill of Materials (SBOM) Tooling & Implementation Working Group, one of the five SBOM community-driven workstreams facilitated by CISA.

In the guidance, reference examples include embedded and Internet of Things (IoT) products, personal computers, servers, software releases with integrated components, etc.

Schneider Bold

Historically, the software engineering term used for describing these groups of products is a software product line. In this document, the term “product line build SBOM” or “PLB-SBOM” will refer to a collection of products. These terms can tie to a specific version of hardware as well as being referenced standalone.

To describe a product line with a build SBOM, there must be the following required information:

  1. Determine an identifier to use
  2. Determine a versioning system to use with that identifier
  3. List all the product’s components distributed together as a group
  4. Provide a version number for each component
  5. Provide a reference to the build SBOM that generated each component image included in the product group as part of the PLB-SBOM

Additionally, the following information are recommendations:

  • Provide a hash of the artifact associated with each component as a cross check for drift. Examples could include tarball, zipfile, container image, install package, disc image, source file, etc., and may be machine specific – x86, arm, etc. A recommendation is to apply the same type of hash, but it is not a requirement.
  • Provide available identifiers (PURL, CPE, SWID tags) for the product component when appropriate.
  • The author of the PLB-SBOM data should be the entity that releases the product line.
  • The PLB-SBOM should remain maintained as updates to the product components end up applied.

CISA’s community-driven working groups publish documents and reports to advance and refine SBOM and ultimately promote adoption.

Click here for more on the SBOM guidance.

Pin It on Pinterest

Share This