# SBOM regulations and requirements by country: the 2026 guide

URL: https://sbombox.com/blog/sbom-regulations
By SBOMBox SBOM experts. Published 2026-11-11, updated 2026-11-13

> Which laws require an SBOM? The EU CRA, NIS2, DORA, FDA, PCI DSS, US federal policy, BSI and CERT-In compared: what is mandatory and what is guidance.

Short answer: the EU Cyber Resilience Act is the broadest SBOM law: every manufacturer of products with digital elements sold in the EU must have one by 11 December 2027. The US FDA already requires SBOMs for connected medical devices. Elsewhere, NIS2, DORA, PCI DSS, US federal contracts and national guidelines such as Germany's BSI TR-03183-2 and India's CERT-In rules make SBOMs expected rather than strictly mandated.

**SBOM rules at a glance**

| Jurisdiction | Rule | Status | Who it affects | Applies |
| --- | --- | --- | --- | --- |
| European Union | [Cyber Resilience Act](https://sbombox.com/blog/cra-sbom-requirements) | Mandatory SBOM | Manufacturers of products with digital elements | 11 December 2027 (reporting from 11 September 2026) |
| European Union | [NIS2](https://sbombox.com/blog/nis2-sbom-supply-chain), Article 21 | SBOM expected as evidence | Essential and important entities, and their suppliers | Since October 2024, via national law |
| European Union | [DORA](https://sbombox.com/blog/dora-sbom-requirements) | SBOM expected as evidence | Financial entities and their ICT suppliers | Since 17 January 2025 |
| European Union | [AI Act](https://sbombox.com/blog/ai-bill-of-materials) | Documentation an AI-BOM supports | Providers of high-risk AI and general-purpose models | Phased, 2025 to 2027 |
| United States | [FDA section 524B](https://sbombox.com/blog/fda-sbom-medical-devices) | Mandatory SBOM | Manufacturers of cyber devices | Since 29 March 2023 |
| United States | [Federal procurement](https://sbombox.com/blog/us-sbom-requirements) | Contract-dependent | Software suppliers to federal agencies | OMB M-26-05, January 2026 |
| United States | [CISA 2026 minimum elements](https://sbombox.com/blog/sbom-minimum-elements) | Voluntary guidance | Anyone producing SBOMs | July 2026 |
| Global | PCI DSS v4, 6.3.2 | Component inventory required | Organisations handling card data | Since 31 March 2025 |
| Germany | [BSI TR-03183-2](https://sbombox.com/blog/bsi-tr-03183-2-sbom-requirements) | Technical guideline | Manufacturers; the usual CRA benchmark | Part 2, version 2.x (2025) |
| India | CERT-In SBOM guidelines | Guidance, binding in some sectors | Government and regulated sectors | Version 2.0, July 2025 |
| Japan | METI SBOM guidance | Guidance | Software suppliers | Current |

## Mandatory SBOM requirements

- EU Cyber Resilience Act (Regulation (EU) 2024/2847): manufacturers must identify and document components, including an SBOM in a commonly used, machine-readable format covering at least top-level dependencies. Reporting duties apply from 11 September 2026; the SBOM duty applies with the rest of the regulation from 11 December 2027. See [CRA SBOM requirements](https://sbombox.com/blog/cra-sbom-requirements).
- US FDA, section 524B of the FD&C Act: manufacturers of 'cyber devices' must include an SBOM in premarket submissions and manage component vulnerabilities after clearance. See [SBOMs for medical devices](https://sbombox.com/blog/fda-sbom-medical-devices).
- PCI DSS v4, requirement 6.3.2: an inventory of bespoke and custom software and its third-party components, assessed since 31 March 2025. It does not say 'SBOM', but an SBOM is the usual way to meet it.

## Requirements that make SBOMs expected

- NIS2 (Directive (EU) 2022/2555): Article 21 requires supply-chain security and vulnerability handling for essential and important entities. No explicit SBOM, but it is the practical evidence. See [NIS2 and SBOMs](https://sbombox.com/blog/nis2-sbom-supply-chain).
- DORA (Regulation (EU) 2022/2554), applying since 17 January 2025: financial entities must manage ICT third-party risk and keep information on the ICT assets and services they rely on. Software suppliers to banks and insurers are increasingly asked for SBOMs. See [DORA and SBOMs](https://sbombox.com/blog/dora-sbom-requirements).
- EU AI Act: technical documentation duties for high-risk AI start with knowing your components, models and datasets. See [what is an AI-BOM?](https://sbombox.com/blog/ai-bill-of-materials).
- US federal software: OMB M-26-05 (January 2026) rescinded the M-22-18 attestation regime; agencies now decide whether to require an SBOM, and many still do in contracts. See [US SBOM requirements](https://sbombox.com/blog/us-sbom-requirements).

## Technical guidelines that define a good SBOM

- Germany, BSI TR-03183-2: the most detailed public specification of SBOM fields and formats, widely used as the CRA benchmark. See [BSI TR-03183-2 explained](https://sbombox.com/blog/bsi-tr-03183-2-sbom-requirements).
- US, CISA 2026 minimum elements (July 2026): voluntary, but used in procurement. Replace the NTIA 2021 list with 17 fields, adding hashes, licences, tool, format, signature and generation context. See [SBOM minimum elements](https://sbombox.com/blog/sbom-minimum-elements).
- India, CERT-In technical guidelines: first issued on 3 October 2024, with version 2.0 (July 2025) extending them to QBOM, CBOM, AIBOM and HBOM. They list minimum data fields and recommend SPDX or CycloneDX. Financial regulators have pointed regulated entities to them; check whether your sector makes them binding.
- Japan: the Ministry of Economy, Trade and Industry (METI) publishes guidance on introducing SBOMs for software management. It is guidance, not law.

## How to read this if you sell internationally

The requirements overlap far more than they differ. They all want a machine-readable SBOM (CycloneDX or SPDX), per release, with exact versions, unique identifiers, dependencies, hashes and licences, kept current and matched against vulnerabilities. Build once to the strictest profile you face, usually the CRA with BSI TR-03183-2 as the field-level guide, and you will meet the others.

## A one-page SBOM compliance plan

- List the markets and customers you sell to, and which rules on this page apply.
- Generate an SBOM for every release, from the artifact you ship. If you ship containers, see [how to generate a container SBOM](https://sbombox.com/blog/container-image-sbom).
- Score every SBOM against the profiles you need. The [free SBOM checker](https://sbombox.com/audit) gives an instant quality score; signed-in projects add requirement-level profile checks.
- Monitor SBOMs for new vulnerabilities and record VEX decisions.
- Keep each release's SBOM for its support period, so you can answer questions about products already in the field.

## Frequently asked questions

### Which laws require an SBOM?

The EU Cyber Resilience Act (from 11 December 2027) and the US FDA's section 524B for cyber medical devices require one explicitly. NIS2, DORA, PCI DSS v4 and US federal contracts make one expected in practice without naming it.

### Is an SBOM mandatory in the US?

Only in specific cases: for cyber medical devices under FDA section 524B, and where a federal or commercial contract requires one. OMB M-26-05 left the decision to individual agencies. CISA's minimum elements are voluntary guidance.

### Does NIS2 require an SBOM?

Not by name. Article 21 requires supply-chain security and vulnerability handling, and SBOMs are the usual evidence for both. See [NIS2 and SBOMs](https://sbombox.com/blog/nis2-sbom-supply-chain).

### Which SBOM standard should I build to if I sell internationally?

Build once to the strictest profile you face. For most teams that is the CRA with BSI TR-03183-2 for field detail, cross-checked against CISA's 2026 minimum elements. That file will meet the other regimes.

This is general information, not legal advice. Confirm how the rules apply to your products with counsel.
