M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Software bill of materials (SBOM)

Concept

A software bill of materials (SBOM) is a machine-readable inventory of the components and dependencies that make up a piece of software.

✦ CONCEPTSoftware bill ofmaterials (SBOM)M365.FM
Title graphic: Software bill of materials (SBOM) (Concept)

Description

A software bill of materials (SBOM) is a machine-readable inventory of the components and dependencies that make up a piece of software. It records what a software artifact contains, including packages and files, so that the composition of a product can be inspected, tracked and checked. In practice, an SBOM serves as the list that a team or a customer can consult when they need to know which parts a given piece of software is built from.

The purpose of an SBOM is closely tied to security and supply chain management. When the contents of a software package are documented in a structured form, it becomes easier to manage components, identify what is installed and handle questions about dependencies. An episode of M365.FM touches on this in a PowerShell security context: in "Run Your Full Stack Locally with .NET Aspire", the episode lists the Software Bill of Materials as one of several security features and describes it as listing all components in install packages for better security management. It appears alongside other measures such as antimalware scanning of script blocks, Constrained Language Mode, Application Control and encrypted SecureString transfer in remoting sessions.

How an SBOM is produced can be seen in Microsoft's open-source SBOM tool, which generates software bills of materials for software artifacts of any variety. According to its repository documentation, the output is compatible with SPDX 2.2 by default, and SPDX 3.0 can be selected as well. Both versions can be validated with the tool. To build the inventory, the tool hashes the files in a drop directory and lists them in the files section of the SBOM. It also scans a build components path for project files such as csproj or package.json in order to detect packages and dependencies, using the Component Detection library. License information is filled in through the ClearlyDefined API. Each generated SBOM receives a unique namespace that is based on an organization-wide base URI.

The tool offers commands for generating an SBOM for a given package name, version and supplier, for validating an existing SBOM, and for redacting file references. Typical use is inside automated build processes: integration into CI/CD is described for GitHub Actions and Azure DevOps pipelines. For installation, the repository lists several routes, namely WinGet, Homebrew, a .NET tool, a Docker image and a NuGet package. This range of options lets teams on different platforms add SBOM generation to their existing build and release workflow.

There are limits to keep in mind when working with generated SBOMs. Redaction of file references only works for SPDX 2.2 SBOMs. The components that are detected also depend on the package formats that Component Detection supports, so an SBOM reflects what the scanner can recognize rather than guaranteeing a complete picture of every possible dependency. Teams therefore need to check that their package formats are covered and validate the output instead of assuming completeness.

A further decision concerns the format version. Because SPDX 2.2 is the default and SPDX 3.0 is optional, a team has to choose which version fits its consumers and tooling, and if redaction is required, the documentation indicates that SPDX 2.2 is the version that supports it. The episode on PowerShell security also places the SBOM next to change tracking and logging advice for a Microsoft 365 tenant, which frames it as one part of a broader set of practices for keeping software and environments manageable and secure.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What is a software bill of materials (SBOM)? (AI)

A software bill of materials (SBOM) is a machine-readable inventory of the components and dependencies that make up a piece of software. It documents what a software artifact contains so that its composition can be reviewed.

Which formats does Microsoft's SBOM tool produce? (AI)

According to the repository documentation, the tool outputs SPDX 2.2 by default and can be set to SPDX 3.0. Both versions can be validated with the tool, while redaction only works for SPDX 2.2 SBOMs.

How does the SBOM tool detect components? (AI)

It hashes the files of a drop directory and lists them in the SBOM, and it scans a build components path for project files such as csproj or package.json using the Component Detection library. License information is filled in through the ClearlyDefined API.

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Maintained by Mirko Peters (Microsoft MVP) · Last updated: