M365Con 2027 – die kostenlose Online-Konferenz · 11–22 Jan 2027 · 120 sessions m365con.net

Software bill of materials (SBOM)

Konzept

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

✦ KONZEPTSoftware bill ofmaterials (SBOM)M365.FM
Titelbild: Software bill of materials (SBOM) (Konzept)

Beschreibung

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.

Überblick, mit KI aus M365.FM-Folgen und den Fakten dieser Seite zusammengestellt. Du kannst ihn unten über „Bearbeiten“ verbessern.

TypKonzept

Diese Kurzbeschreibung gibt es noch nicht in deiner Sprache – gern ergänzen.

Glossar

Community-Wiki

Oben die Kurzinfo, unten das Wissen der Community: ergänze praktische Tipps, Beispiele oder Korrekturen. Neue Beiträge werden zuerst geprüft, bewährte Mitglieder veröffentlichen direkt.

Experten und Firmen zu diesem Thema

Dieses Thema hat noch niemand im Profil angegeben. Trag es in deinem Profil ein.

Gepflegt von Mirko Peters (Microsoft MVP) · Zuletzt aktualisiert: