# SBOM

> An SBOM (software bill of materials) is a machine-readable record of the components of a software product and of their supply chain relationships.

Original page: https://t10.de/en/glossary/sbom
Publisher: total10 GmbH, https://t10.de/en/glossary

An SBOM lists the parts of a piece of software and where they come from. Article 3(39) of the [Cyber Resilience Act](https://data.europa.eu/eli/reg/2024/2847/oj) (CRA) defines the software bill of materials as a formal record of the details and supply chain relationships of the components in the software elements of a product with digital elements. The Regulation's English text uses the abbreviation SBOM in its recitals. The BSI's [Technical Guideline TR-03183-2](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2_v2_1_0.pdf?__blob=publicationFile&v=6) defines the SBOM as a machine-processable file containing the supply chain relationships and details of the components used.

From 11 December 2027, Annex I Part II No. 1 of the CRA requires manufacturers to identify and document vulnerabilities and components of their products. This includes drawing up a software bill of materials in a commonly used, machine-readable format covering, at the very least, the top-level dependencies. According to recital 77, manufacturers should not be obliged to make the SBOM public.

The BSI's [FAQ for manufacturers](https://www.bsi.bund.de/EN/IT-Sicherheitsvorfall/IT-Schwachstellen/FAQ_Hersteller/FAQ_Hersteller_node.html) on coordinated vulnerability disclosure notes that a vulnerability may be reported for one product while another is affected through shared components. An SBOM helps to check whether another product is affected. ENISA's [2021 report on supply chain attacks](https://www.enisa.europa.eu/sites/default/files/publications/ENISA%20Threat%20Landscape%20for%20Supply%20Chain%20Attacks.pdf) names software libraries and third-party packages among the supplier assets such attacks target. Where a shop or business application uses many third-party packages, an SBOM gives an overview.

## See also

- [Supply chain attack](https://t10.de/en/glossary/supply-chain-attack): A supply chain attack is a cyber attack in which attackers first compromise a supplier, such as a provider of software or components, in order to reach the actual target through it.
- [Connected product](https://t10.de/en/glossary/connected-product): Under the Data Act, a connected product is an item that obtains, generates or collects data about its use or environment and is able to communicate that data.
- [Dependency](https://t10.de/en/glossary/dependency): A dependency is a third-party software package that a project builds on and needs in order to run; packages required by a dependency count as dependencies too.
- [Lock file](https://t10.de/en/glossary/lock-file): A lock file records the exact versions of all packages installed in a project, so that every installation ends up in the same state; with Composer it is composer.lock.

## Sources

1. [Technische Richtlinie BSI TR-03183-2: Cyber Resilience Requirements for Manufacturers and Products, Part 2: Software Bill of Materials (SBOM), Version 2.1.0 vom 2025-08-20](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2_v2_1_0.pdf?__blob=publicationFile&v=6), Bundesamt für Sicherheit in der Informationstechnik (BSI), accessed 2026-11-18
2. [Verordnung (EU) 2024/2847 (Cyberresilienzverordnung), ABl. L vom 20.11.2024](https://data.europa.eu/eli/reg/2024/2847/oj), Europäisches Parlament und Rat der EU (Amtsblatt der EU), accessed 2026-11-18
3. [CVD: FAQ für Hersteller](https://www.bsi.bund.de/DE/IT-Sicherheitsvorfall/IT-Schwachstellen/FAQ_Hersteller/FAQ_Hersteller_node.html), Bundesamt für Sicherheit in der Informationstechnik (BSI), accessed 2026-11-18
4. [ENISA Threat Landscape for Supply Chain Attacks (July 2021)](https://www.enisa.europa.eu/sites/default/files/publications/ENISA%20Threat%20Landscape%20for%20Supply%20Chain%20Attacks.pdf), ENISA (Agentur der Europäischen Union für Cybersicherheit), accessed 2026-11-18
