NIS2 and SBOMs: does NIS2 require a software bill of materials?
By SBOMBox SBOM experts · · Updated · 5 min readShort answer: the NIS2 Directive does not use the word SBOM, so there is no explicit NIS2 SBOM requirement. But Article 21 obliges covered organisations to manage supply-chain security and vulnerability handling, and regulators and auditors increasingly accept an SBOM as the practical evidence that you do. If you sell software to a NIS2 entity, expect to be asked for one.
What NIS2 is
NIS2 is Directive (EU) 2022/2555. It replaced the original NIS Directive and had to be transposed into national law by 17 October 2024. Most Member States have now done so, some late; Germany's implementation law entered into force on 6 December 2025. Because it is a directive, the exact duties and fines are set by each country's law, so check yours.
Who NIS2 covers
- Medium and large organisations (broadly, 50 or more staff or over 10 million euros turnover) in the sectors listed in Annexes I and II: energy, transport, banking, health, drinking water, digital infrastructure, ICT service management, public administration, space, postal services, waste, chemicals, food, manufacturing, digital providers and research.
- Some entities regardless of size, such as DNS providers, top-level domain registries, trust service providers and public electronic communications networks.
- Entities are 'essential' or 'important'. The duties are the same; supervision and maximum fines differ.
Where SBOMs come in: Article 21
Article 21 lists the cybersecurity risk-management measures every covered entity must take. The supply-chain measure reads:
…supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers;
Two of the Article 21 measures are where an SBOM earns its place:
- Article 21(2)(d), supply chain security: security aspects of the relationships with direct suppliers and service providers. Article 21(3) adds that you must consider the vulnerabilities specific to each supplier and the quality of its products and secure development practices.
- Article 21(2)(e), security in acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
You cannot assess the vulnerabilities in a supplier's product, or handle vulnerabilities in your own systems, without knowing which components are inside. That is what an SBOM is. For digital infrastructure and managed service providers, Implementing Regulation (EU) 2024/2690 spells out these supply-chain measures in more detail.
Incident reporting under NIS2
NIS2 Article 23 sets a reporting sequence for significant incidents: an early warning within 24 hours, an incident notification within 72 hours, and a final report within one month. It mirrors the CRA 24-hour reporting rule, and the same SBOM inventory is what lets you say quickly whether a newly exploited vulnerability affects you.
Fines and management liability
- Essential entities: maximum fines of at least 10 million euros or 2% of worldwide annual turnover, whichever is higher.
- Important entities: at least 7 million euros or 1.4% of worldwide annual turnover.
- Article 20 makes management bodies approve and oversee the risk-management measures, and they can be held liable for failures.
If you are a software supplier to a NIS2 entity
- Expect supplier questionnaires that ask what is in your software, how you handle vulnerabilities and how fast you notify. See how to answer a customer's SBOM and security questionnaire.
- Expect contract clauses requiring an SBOM per release and VEX statements for known vulnerabilities.
- If your software is a product sold in the EU, the Cyber Resilience Act applies to you directly, and it does require an SBOM. See CRA SBOM requirements.
A practical NIS2 SBOM checklist
- Keep an SBOM for every system and release you build, and request one from each critical supplier. Our guide to getting SBOMs from suppliers covers the wording.
- Match those SBOMs continuously against vulnerability feeds, including CISA KEV.
- Record your assessment of each match with VEX, so you can show auditors why something was or was not fixed.
- Check SBOM quality, not just existence. Run any file through the free SBOM checker.
NIS2 vs the Cyber Resilience Act on SBOMs
| NIS2 | Cyber Resilience Act | |
|---|---|---|
| Regulates | Organisations in critical sectors | Products with digital elements and their manufacturers |
| Says 'SBOM'? | No | Yes, Annex I, Part II, point (1) |
| What it requires | Supply-chain security and vulnerability handling (Article 21) | An SBOM in a machine-readable format, covering at least top-level dependencies |
| Who asks for your SBOM | Your NIS2-covered customers and their auditors | Market surveillance authorities, on request |
| Applies since | October 2024, through national law | 11 December 2027 (reporting since 11 September 2026) |
For financial entities, DORA applies instead of NIS2; see DORA and SBOMs. For how NIS2 fits alongside the CRA and US rules, see our overview of SBOM regulations by country.
Frequently asked questions
Does NIS2 require an SBOM?
Not explicitly. The directive never uses the word. Article 21 requires supply-chain security and vulnerability handling, and an SBOM is the most direct evidence for both, so auditors and customers increasingly expect one.
Which NIS2 article covers the software supply chain?
Article 21(2)(d) covers supply-chain security, and Article 21(3) requires entities to consider each direct supplier's vulnerabilities and secure development practices. Article 21(2)(e) covers vulnerability handling and disclosure.
I sell software to a NIS2 entity. Do I need an SBOM?
NIS2 does not oblige you directly, but your customer must manage supplier risk, so expect contracts and questionnaires that ask for an SBOM per release. If your software is a product sold in the EU, the Cyber Resilience Act requires one anyway.
What is the difference between NIS2 and the CRA?
NIS2 regulates how organisations in critical sectors manage cyber risk. The CRA regulates the security of products sold in the EU. A software company can be a supplier under NIS2 and a manufacturer under the CRA at the same time.
This is general information, not legal advice. Confirm how the rules apply to you with counsel.