Glossary · Cross-cutting
SBOM
- Area
- Both strands
- Related
- Supply chain attack, Connected product, Dependency, Lock file
An SBOM (software bill of materials) is a machine-readable record of the components of a software product and of their supply chain relationships.
An SBOM lists the parts of a piece of software and where they come from. Article 3(39) of the Cyber Resilience Act (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 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 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. Read in the glossary → . According to recital 77, manufacturers should not be obliged to make the SBOM public.
The BSI's FAQ for manufacturers on coordinated vulnerability disclosure Coordinated vulnerability disclosure Coordinated vulnerability disclosure is a procedure in which details of a vulnerability are made public in a planned sequence, coordinated with the release of a fix for it. Read in the glossary → 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 ENISA ENISA is the European Union Agency for Cybersecurity, whose tasks are aimed at achieving a high common level of cybersecurity across the Union. 's 2021 report on supply chain attacks names software libraries and third-party packages among the supplier assets such attacks target. Where a shop or business application Business application In general terms, a business application is software used to perform or support business functions. Read in the glossary → uses many third-party packages, an SBOM gives an overview.
See also
-
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.
Cross-cutting
-
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.
E-commerce
-
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.
E-commerce
-
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.
E-commerce
Sources
-
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 (opens in a new tab)
Bundesamt für Sicherheit in der Informationstechnik (BSI) accessed
-
Verordnung (EU) 2024/2847 (Cyberresilienzverordnung), ABl. L vom 20.11.2024 (opens in a new tab)
Europäisches Parlament und Rat der EU (Amtsblatt der EU) accessed
-
CVD: FAQ für Hersteller (opens in a new tab)
Bundesamt für Sicherheit in der Informationstechnik (BSI) accessed
-
ENISA Threat Landscape for Supply Chain Attacks (July 2021) (opens in a new tab)
ENISA (Agentur der Europäischen Union für Cybersicherheit) accessed