Basics

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

By SBOMBox SBOM experts · · Updated · 7 min read

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

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 and Help Net Security. 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
ElementWhat it meansvs 2021CycloneDXSPDX 2.3
SBOM AuthorWho produced the SBOM (may differ from the software producer)Renamedmetadata.authors or metadata.manufacturercreationInfo.creators (Person or Organization)
SBOM TimestampWhen the SBOM was produced, in RFC 9557 date-time formatKeptmetadata.timestampcreationInfo.created
SBOM Author SignatureA signature that proves who produced the SBOM and that it was not alteredNewsignature, or a detached signature or attestationA detached signature or attestation
SBOM Data Format NameThe format, such as CycloneDX or SPDXNewbomFormatspdxVersion (prefix)
SBOM Data Format VersionThe version of that formatNewspecVersionspdxVersion
SBOM Generation ContextWhen in the lifecycle the SBOM was made: source, build or post-build binaryNewmetadata.lifecyclesNo dedicated field; record it in creationInfo.comment
SBOM Tool NameThe tool that generated the SBOMNewmetadata.toolscreationInfo.creators (Tool: name-version)
SBOM Tool VersionThe version of that toolNewmetadata.toolscreationInfo.creators (Tool: name-version)
SBOM VersionThe revision of this SBOM documentNewversion, with a stable serialNumberA new documentNamespace per revision
Component ProducerWho created or maintains the componentRenamedsupplier or manufacturersupplier or originator
Component NameThe component's name; alternate names are allowedKeptnamename
Component VersionThe exact version, not a rangeRenamedversionversionInfo
Component IdentifiersIdentifiers that let tools look the component up, such as a purl or CPERenamedpurl, cpe, swidexternalRefs (purl, cpe23Type)
Component Dependency RelationshipWhich component includes or depends on whichKeptdependenciesrelationships (DEPENDS_ON, CONTAINS)
Component Hash ValueA cryptographic hash of the componentNewhashes[].contentchecksums[].checksumValue
Component Hash AlgorithmThe algorithm used for that hash, such as SHA-256Newhashes[].algchecksums[].algorithm
Component LicenseThe licence of the component, ideally an SPDX identifierNewlicenseslicenseConcluded, 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
FrameworkStatusField listHashes and licencesDepth
NTIA 2021Superseded7 data fieldsNot requiredTop-level at minimum
CISA 2026 minimum elementsUS guidance, used in procurement17 data fieldsRequiredAll components, including transitive
BSI TR-03183-2 (Germany)Technical guideline, the usual CRA benchmarkRequired and optional fields for the SBOM and each componentRequiredComplete, recursively
EU Cyber Resilience ActLaw, applies from 11 December 2027Not listed; the Commission may set them by implementing actNot specifiedAt least top-level dependencies
India CERT-In guidelinesTechnical guidelines; some sectors make them bindingA longer list, including end-of-life datesRequiredComplete

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.

Minimum practices, not just fields

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?.

A practical upgrade checklist

The quickest way to find your gaps is to drop the file on the free SBOM checker. 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.