# SBOM minimum elements: the 2026 CISA list, field by field

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

> The 2026 SBOM minimum elements replace NTIA's 2021 list: 17 data fields, what each means, where it lives in CycloneDX and SPDX, and how BSI and the CRA compare.

Short answer: the SBOM minimum elements are the baseline data every software bill of materials should contain. The current list is the 2026 Minimum Elements for a Software Bill of Materials, published in July 2026 by CISA with the NSA, the FBI and international partner agencies. It replaces the 2021 NTIA list and its 2025 draft update. It has 17 data fields: nine about the SBOM document and eight for every component. It is guidance, not law, but buyers use it as the checklist.

## What changed in 2026

- Seven fields became seventeen. The new ones are mostly about provenance and verification: hashes, licences, the tool that produced the SBOM, the format, a signature and the generation context.
- Four fields were renamed: 'Supplier name' is now Component Producer, 'Author of SBOM data' is SBOM Author, 'Version of the component' is Component Version and 'Other unique identifiers' is Component Identifiers.
- Coverage is now expected to be complete: all components, including transitive dependencies, with no minimum depth. Linked sub-SBOMs are acceptable if the recipient can access them.
- Authors must distinguish information they do not know from information they have chosen to withhold, and give recipients a way to request withheld data.
- SPDX and CycloneDX are the accepted formats. SWID tags are no longer listed as an SBOM format.
- The 2021 'accommodation of mistakes' practice gave way to a presumption that SBOM data is accurate, and the separate access-control element was folded into distribution and delivery.

If you followed the August 2025 draft, most of your work carries over: the draft already added hashes, licences, tool name and generation context. The final text adds the remaining format, version and signature fields. Sources: [FOSSA's summary of the 2026 release](https://fossa.com/blog/cisa-releases-2026-minimum-sbom-elements/) and [Help Net Security](https://www.helpnetsecurity.com/2026/07/30/cisa-sbom-guidance-updated/). Check the CISA publication itself for the authoritative wording.

## The 17 SBOM minimum elements, field by field

**2026 minimum elements and where they live in each format**

| Element | What it means | vs 2021 | CycloneDX | SPDX 2.3 |
| --- | --- | --- | --- | --- |
| SBOM Author | Who produced the SBOM (may differ from the software producer) | Renamed | `metadata.authors` or `metadata.manufacturer` | `creationInfo.creators` (Person or Organization) |
| SBOM Timestamp | When the SBOM was produced, in RFC 9557 date-time format | Kept | `metadata.timestamp` | `creationInfo.created` |
| SBOM Author Signature | A signature that proves who produced the SBOM and that it was not altered | New | `signature`, or a detached signature or attestation | A detached signature or attestation |
| SBOM Data Format Name | The format, such as CycloneDX or SPDX | New | `bomFormat` | `spdxVersion` (prefix) |
| SBOM Data Format Version | The version of that format | New | `specVersion` | `spdxVersion` |
| SBOM Generation Context | When in the lifecycle the SBOM was made: source, build or post-build binary | New | `metadata.lifecycles` | No dedicated field; record it in `creationInfo.comment` |
| SBOM Tool Name | The tool that generated the SBOM | New | `metadata.tools` | `creationInfo.creators` (Tool: name-version) |
| SBOM Tool Version | The version of that tool | New | `metadata.tools` | `creationInfo.creators` (Tool: name-version) |
| SBOM Version | The revision of this SBOM document | New | `version`, with a stable `serialNumber` | A new `documentNamespace` per revision |
| Component Producer | Who created or maintains the component | Renamed | `supplier` or `manufacturer` | `supplier` or `originator` |
| Component Name | The component's name; alternate names are allowed | Kept | `name` | `name` |
| Component Version | The exact version, not a range | Renamed | `version` | `versionInfo` |
| Component Identifiers | Identifiers that let tools look the component up, such as a purl or CPE | Renamed | `purl`, `cpe`, `swid` | `externalRefs` (purl, cpe23Type) |
| Component Dependency Relationship | Which component includes or depends on which | Kept | `dependencies` | `relationships` (DEPENDS_ON, CONTAINS) |
| Component Hash Value | A cryptographic hash of the component | New | `hashes[].content` | `checksums[].checksumValue` |
| Component Hash Algorithm | The algorithm used for that hash, such as SHA-256 | New | `hashes[].alg` | `checksums[].algorithm` |
| Component License | The licence of the component, ideally an SPDX identifier | New | `licenses` | `licenseConcluded`, `licenseDeclared` |

Field paths are a mapping guide, not part of the CISA text. SPDX 3.0 restructures several of them; the meaning is the same.

## How the major frameworks compare

**Minimum SBOM content by framework**

| Framework | Status | Field list | Hashes and licences | Depth |
| --- | --- | --- | --- | --- |
| NTIA 2021 | Superseded | 7 data fields | Not required | Top-level at minimum |
| CISA 2026 minimum elements | US guidance, used in procurement | 17 data fields | Required | All components, including transitive |
| [BSI TR-03183-2](https://sbombox.com/blog/bsi-tr-03183-2-sbom-requirements) (Germany) | Technical guideline, the usual CRA benchmark | Required and optional fields for the SBOM and each component | Required | Complete, recursively |
| [EU Cyber Resilience Act](https://sbombox.com/blog/cra-sbom-requirements) | Law, applies from 11 December 2027 | Not listed; the Commission may set them by implementing act | Not specified | At least top-level dependencies |
| India CERT-In guidelines | Technical guidelines; some sectors make them binding | A longer list, including end-of-life dates | Required | Complete |

Build to the strictest list you face. In practice that is the CISA 2026 elements plus BSI's contact and file-property fields. A file that meets both will meet the CRA's floor easily. For the wider picture, see [SBOM regulations by country](https://sbombox.com/blog/sbom-regulations).

## Minimum practices, not just fields

- Frequency: a new SBOM for every build or release, and a new SBOM version whenever the data changes.
- Coverage: every component, including transitive dependencies. State known unknowns explicitly rather than leaving gaps silent.
- Generation context: record whether the SBOM came from source, the build or the shipped binary. They list different things. For containers, generate from the image you ship; see [container image SBOMs](https://sbombox.com/blog/container-image-sbom).
- Distribution and delivery: agree how SBOMs reach the people who need them, and who may see them.
- Machine-processable formats: CycloneDX or SPDX in JSON or XML. Not a spreadsheet or a PDF.

## Is it mandatory?

No. CISA presents the minimum elements as recommended guidance, not regulation, and some vendor articles overstate this. In practice, US agencies and enterprise buyers cite the list in contracts and questionnaires, so it is the bar customers will hold you to. AI systems have a separate, supplementary list; see [what is an AI-BOM?](https://sbombox.com/blog/ai-bill-of-materials).

## A practical upgrade checklist

- Turn on hash output in your generator and use SHA-256 or stronger. Hash the components, not just the SBOM file.
- Emit licences as SPDX licence identifiers or expressions, not free text or URLs.
- Keep the generator's name and version in the metadata. Do not strip it in post-processing.
- Record the lifecycle stage. CycloneDX 1.5 and later has a `lifecycles` field for this.
- Sign the SBOM. See [SBOM signing and provenance](https://sbombox.com/blog/sbom-signing-and-provenance).
- Re-check the old fields: exact versions, purls and producer names are still the most common gaps.

The quickest way to find your gaps is to drop the file on the [free SBOM checker](https://sbombox.com/audit). It shows which elements pass, which are partial and which are missing.

## Frequently asked questions

### What are the SBOM minimum elements?

The baseline data an SBOM should contain so it can be used to find vulnerable components. The 2026 CISA list has 17 data fields: SBOM author, timestamp, author signature, format name and version, generation context, tool name and version and SBOM version, plus, for every component, its producer, name, version, identifiers, dependency relationships, hash value, hash algorithm and licence.

### What were the original NTIA minimum elements?

The 2021 NTIA list had seven data fields: supplier name, component name, version, other unique identifiers, dependency relationship, author of SBOM data and timestamp. It is now superseded by the 2026 list.

### What happened to CISA's 2025 minimum elements?

CISA published a draft in August 2025 for public comment. The final version was published in July 2026 as the 2026 Minimum Elements, co-authored with the NSA, the FBI and international partners.

### Are the SBOM minimum elements mandatory?

No. They are recommended guidance. They become binding only where a contract, procurement rule or sector regulator adopts them.

### Does the EU Cyber Resilience Act use the CISA minimum elements?

Not directly. The CRA requires an SBOM in a commonly used, machine-readable format covering at least top-level dependencies, and leaves the detailed fields to a possible implementing act. Germany's BSI TR-03183-2 is the usual reference until then.
