An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesSoftware Bill of Materials and NIS2 Cybersecurity
Secure Acquisition Development Vulnerabilities / 2026-10-10

Software Bill of Materials and NIS2 Cybersecurity

A software bill of materials (SBOM) can improve visibility into third-party components used in software supporting covered services. NIS2 Article 21(2)(e) includes acquisition, development, maintenance and vulnerability handling, but does not establish a universal SBOM format or require every covered entity to produce an SBOM for every product.

Know what an SBOM can and cannot show

An SBOM identifies components and versions in a particular software build. It can help teams investigate a published vulnerability and assess which deployed services rely on an affected library. Its usefulness depends on completeness, accuracy, build provenance and mapping to systems actually in use.

An SBOM does not by itself demonstrate that software is secure, that components are maintained or that a vulnerability is exploitable. Teams still need risk analysis, reliable update processes and knowledge of deployed configurations.

Choose scope according to criticality

Identify software that supports important services, exposes privileged functions or has extensive external dependencies. Prioritise these applications for component visibility and supplier discussions, with an inventory owner and links to deployment versions.

Where source code is unavailable, ask the vendor what composition evidence can reasonably be provided. Record gaps without representing supplier refusals as proof of a defect.

Integrate component data with vulnerability assessment

When a component advisory appears, compare affected versions against the SBOM and deployed environment. Confirm whether the vulnerable code path exists and whether other controls reduce exposure, rather than escalating every theoretical match.

A dependency used only by build tooling may create a different exposure from a library running in an internet-facing application. Use that distinction when ranking action.

Protect integrity and update information

Generate or obtain component data from a trustworthy build or supplier process. Record product version, date, origin, relationships and the responsible team. Refresh data following meaningful releases and dependency changes.

Treat SBOM data as potentially sensitive architectural information. Define appropriate access and sharing arrangements, particularly where documentation reveals internal systems or exploitable component combinations.

Use SBOMs within supplier and development controls

Clarify whether development teams, external vendors or managed providers own component inventory and vulnerability communication. Align the information with secure acquisition, release verification and maintenance obligations.

Article 21(2)(d) also makes supplier relationships relevant. A contractual promise to deliver SBOMs is less useful if no one maintains or uses the data after acceptance.

Retain evidence and check legal scope

Keep records of SBOM coverage, relevant vulnerability decisions, supplier responses, remediation and exceptions. Review the approach as software and supporting services change.

The general NIS2 Directive is risk-based. Check national implementing law and any specifically applicable requirements, including the defined scope of Implementing Regulation (EU) 2024/2690, before claiming SBOM production is universally mandated.

Questions arising

Does NIS2 require an SBOM for every software product?

Article 21(2)(e) does not impose a universal SBOM format or an across-the-board obligation to create one for every product.

Can an SBOM replace vulnerability scanning?

No. It helps identify potentially affected components but does not establish exploitability or replace testing, monitoring and remediation.

Related entries

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.