Glossary

SBOM

Software bill of materials

Definition

A software bill of materials lists the components and relationships that make up a particular software product or release.

It provides component information for a particular product or release. It is an input to security assessment, rather than proof that the software is safe.

A customer may include “SBOM” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

A software bill of materials (SBOM) is a structured record of the components in software and their relationships. It can identify included libraries and versions, helping a buyer or developer understand dependencies that are otherwise difficult to see. An SBOM should be associated with the relevant product or release.

The record is useful when a weakness is discovered in a component. It can help a team identify software that may need investigation. It does not, by itself, establish whether the weakness can be exploited in that product or whether the supplier has fixed it.

A maintained SBOM can support triage when a component vulnerability is disclosed, but it does not show whether the component is reachable or affected in the deployed product.

Compare the listed component and version with the affected product release and vendor advisory. Assign an owner to assess exposure and track fixes; an outdated or incomplete SBOM limits that work.

Sources

CISA: SBOM resources and NIST: software component transparency and SBOMs