Engineers with a laptop at automation test rigs in a bright production hall

SBOM

SBOM Minimum Elements: what a compliant SBOM must contain

Last updated:

The SBOM Minimum Elements are CISA's baseline of 17 data fields (9 SBOM-metadata fields plus 8 component-data fields) and 6 practices a Software Bill of Materials must satisfy to be usable for software supply-chain risk management. The current version, 2026 Minimum Elements for a Software Bill of Materials (SBOM), was published 29 July 2026 by CISA together with the NSA, FBI and 15 other national cybersecurity agencies, and "updates and replaces" NTIA's original document, published 12 July 2021 under Executive Order 14028.

Key takeaways

  • The 2026 document splits data fields into two groups: SBOM Metadata, about the SBOM document itself, and Component Data, about the target component and each subcomponent it enumerates.
  • The 2026 document does not prescribe field names.
  • The excerpt below is synthetic: a made-up gateway firmware image from a made-up vendor, reduced to one component.
  • A supplier can run these checks before an SBOM leaves the building.

Where does the requirement come from?

Executive Order 14028, "Improving the Nation's Cybersecurity," signed 12 May 2021, directed in Section 4(f): "Within 60 days of the date of this order, the Secretary of Commerce, in coordination with the Assistant Secretary for Communications and Information and the Administrator of the National Telecommunications and Information Administration, shall publish minimum elements for an SBOM." Section 10(j) of the same order defines an SBOM as "a formal record containing the details and supply chain relationships of various components used in building software," comparing it to "a list of ingredients on food packaging." NTIA's resulting 2021 report set the first baseline; the version history recorded in the 2026 document shows two further revisions: a version 2.0 draft published 22 August 2025 for public comment (closing 3 October 2025), and the current version 2.1, finalized 29 July 2026 after incorporating that comment period's feedback.

The 17 data fields

The 2026 document splits data fields into two groups: SBOM Metadata, about the SBOM document itself, and Component Data, about the target component and each subcomponent it enumerates.

SBOM Metadata (9 fields)

Field Definition
SBOM Author "The name of the entity that creates the SBOM data for the target component."
SBOM Author Signature "A digital signature attributable to the SBOM author."
SBOM Data Format Name "The name of the data format used to represent the SBOM data."
SBOM Data Format Version "Identifier designated by the SBOM data format to specify the version of the data format."
SBOM Generation Context "The relative software lifecycle phase and data available at the time the SBOM author generated the SBOM" — e.g. "before build" or "after build."
SBOM Timestamp "Record of the date and time of the most recent update to the SBOM data."
SBOM Tool Name "The name of the tool used by the SBOM author to generate or amend the SBOM."
SBOM Tool Version "Identifier for the version of the tool identified in the SBOM Tool Name element."
SBOM Version "Identifier designated by the SBOM author to specify a change in the SBOM document from a previously identified version."

Component Data (8 fields)

Field Definition
Component Producer "The name of an entity that creates, defines, and identifies components" — replaces the 2021 "Supplier Name" field.
Component Name "The name assigned by the component producer to a software component." Now allows multiple entries for alternate names.
Component Version "Identifier used by the component producer to specify a change in a software component from a previously identified version."
Component Identifiers At least one software identifier, such as Common Platform Enumeration (CPE) or Package-URL (PURL); may also include UUIDs, organization-specific identifiers, commit hashes, OmniBOR or SWHID.
Component License "The identifiers for the licenses under which the software component is available," ideally using SPDX license identifiers — new in 2026.
Component Hash Value A cryptographic hash of the executable component artifact — new in 2026.
Component Hash Algorithm The algorithm used to compute the hash, identified via IANA's hash function text names — new in 2026.
Component Dependency Relationship "The relationship between two components, where one component is necessary for the operation of the other."

Every "unknown" field should be marked explicitly as unknown rather than left blank — one of the six Practices and Processes below.

The 6 practices and processes

Separate from the data itself, the document sets six baseline expectations for how an organization handles SBOM data across its lifecycle:

Practice What it requires
Accommodation of Updates to SBOM Data SBOM authors correct errors promptly; recipients should expect corrections.
Coverage All components including transitive dependencies, with "no minimum depth" — a 2026 change from the 2021 "Depth" element, which covered only top-level dependencies.
Distribution and Delivery SBOMs available promptly to those who need them; access controls must not block sharing between authorized parties.
Explicitly Identifying Unknown Information State whether missing data is unknown to the author or deliberately withheld, rather than leaving it blank.
Frequency A new or revised SBOM for each software version, build or update.
Machine-Processable Data Automation support "critical for managing software component data at scale." The document names SPDX and CycloneDX as the two formats "currently widely used by software ecosystem stakeholders to generate and consume SBOMs," and drops SWID tags from the recommended list, stating they are "not a widely used SBOM data format for which multiple tools exist."

What's new versus the 2021 NTIA version

Ten fields were added in the 2026 update, all aimed at letting a recipient trust and process the SBOM automatically: SBOM Author Signature, SBOM Data Format Name, SBOM Data Format Version, SBOM Generation Context, SBOM Tool Name, SBOM Tool Version, SBOM Version, Component Hash Value, Component Hash Algorithm and Component License. Several 2021 fields were renamed or redefined rather than dropped: Supplier Name became Component Producer (the document notes "Supplier Name has proven ambiguous in practice, particularly around distributors of software"), Other Unique Identifiers became Component Identifiers, Depth became the broader Coverage, and Automation Support became Machine-Processable Data. The Access Control element was removed outright, with its substance folded into Distribution and Delivery.

Which CycloneDX and SPDX fields carry each element?

The 2026 document does not prescribe field names. It says a minimum element "need not correlate directly with a particular data field in an SBOM data format," and one format field may satisfy several elements. The table below is SoftWSP's reading of where each element lands in the CycloneDX 1.6 JSON schema and the SPDX 2.3 specification. It is a working aid, not an official crosswalk.

Minimum element CycloneDX 1.6 SPDX 2.3
SBOM Author metadata.authors or metadata.manufacturer Creator: Organization: or Person:
SBOM Author Signature top-level signature (JSON Signature Format) no native field; sign the file outside the document
SBOM Data Format Name / Version bomFormat / specVersion SPDXVersion (for example SPDX-2.3)
SBOM Generation Context metadata.lifecycles[].phase (pre-build, build, post-build and others) no 2.3 field; SPDX 3.0 adds an sbomType vocabulary
SBOM Timestamp metadata.timestamp Created
SBOM Tool Name / Version metadata.tools.components[].name / .version Creator: Tool: name-version
SBOM Version version, plus a unique serialNumber no dedicated field
Component Producer component.manufacturer (supplier "may also be a distributor or repackager") PackageOriginator (PackageSupplier is the distribution source)
Component Name / Version name / version PackageName / PackageVersion
Component Identifiers purl, cpe, omniborId, swhid, swid ExternalRef (for example SECURITY cpe23Type, PACKAGE-MANAGER purl)
Component License licenses PackageLicenseDeclared / PackageLicenseConcluded
Component Hash Value / Algorithm hashes[].content / hashes[].alg PackageChecksum: SHA256: …
Component Dependency Relationship dependencies[].ref + dependsOn Relationship: … DEPENDS_ON …

Sources: CycloneDX 1.6 JSON schema; SPDX 2.3 chapters 6, 7 and 11; SPDX 3.0.1 SbomType. Read 2026-11-10.

For the trade-offs between the two formats on embedded devices, see CycloneDX vs SPDX. For identifier syntax, see the purl guide.

What does a minimum-elements firmware SBOM look like?

The excerpt below is synthetic: a made-up gateway firmware image from a made-up vendor, reduced to one component. It shows where the 2026 elements sit in a CycloneDX 1.6 document generated by binary analysis of the shipped image:

{
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:3e671687-395b-41f5-a30f-a58921a69b79",
  "version": 1,
  "metadata": {
    "timestamp": "2026-11-10T09:00:00Z",
    "lifecycles": [{ "phase": "post-build" }],
    "manufacturer": { "name": "Example Devices GmbH" },
    "tools": { "components": [{ "type": "application", "name": "example-sbom-tool", "version": "2.4.0" }] },
    "component": { "type": "firmware", "bom-ref": "fw", "name": "gw-100-firmware", "version": "4.2.1" }
  },
  "components": [{
    "type": "library", "bom-ref": "zlib",
    "manufacturer": { "name": "zlib project" },
    "name": "zlib", "version": "1.3.1",
    "purl": "pkg:generic/[email protected]",
    "licenses": [{ "license": { "id": "Zlib" } }],
    "hashes": [{ "alg": "SHA-256", "content": "…" }]
  }],
  "dependencies": [{ "ref": "fw", "dependsOn": ["zlib"] }]
}

Which hash belongs in Component Hash Value? The 2026 document defines it as the hash of "an executable component artifact." For firmware, that is the binary or library as extracted from the shipped image, not the upstream source archive. If the SBOM author has no access to that artifact, the document says to state that the value is unknown.

The post-build phase matches the document's own example that "binary analysis tools can generate an SBOM 'after build'." The signature is added last, over the finished document.

How do you check an SBOM against the minimum elements?

A supplier can run these checks before an SBOM leaves the building. A customer can run the same checks on intake:

  1. Format and versionConfirm that the format name and version are declared and that the format version is not one its maintainers have deprecated. The document says deprecated versions "should not be used."
  2. Document metadataCheck the author, tool name and version, timestamp (RFC 9557 format) and SBOM version. With Semantic Versioning, the major version of a published SBOM should be "1."
  3. SignatureVerify the author signature against a published key, using an algorithm approved by an authority such as NIST.
  4. CoverageEvery component has a dependency relationship back to the target, including transitive ones. There is "no minimum depth."
  5. Component fieldsCheck producer, name, version, at least one identifier, licence, and hash value plus algorithm for every component. Fields that are missing are marked as unknown or as withheld, never left blank.
  6. UsabilityLoad the file into a viewer and run a vulnerability match. Components without an identifier are hard to match automatically against vulnerability databases. The SBOM viewer shows this in the browser.
  7. Pair with status dataThe 2026 document points to VEX and CSAF as the way to tell recipients which listed vulnerabilities do not affect the product.

Which mistakes make an SBOM fall short?

  • A distributor named as producer. This ambiguity is why the document dropped "Supplier Name." In SPDX 2.3, PackageSupplier is defined as the distribution source; the originator field is closer to Component Producer.
  • Blanket "no assertion" values. SPDX's NOASSERTION covers a failed attempt, no attempt, and a deliberate omission alike. The 2026 practice asks authors to say which one applies.
  • Hashing the wrong artifact. A hash of a source tarball cannot be compared with what runs on the device.
  • One SBOM per product line. The Frequency practice expects an SBOM for each version, build or update.
  • Acronyms in name fields. Author, tool, producer and component names should use full names unless the official name is an acronym.
  • Top-level only. That was the 2021 floor. Coverage now includes transitive dependencies.

Scope: beyond traditional software

The 2026 document states the minimum elements "apply to SBOMs for all software, including open source software, AI software, and SaaS," while noting that AI systems and cloud/SaaS software "may require additional elements" not covered here — the document explicitly does not introduce AI- or SaaS-specific fields itself, pointing instead to a companion guidance, Software Bill of Materials (SBOM) for Artificial Intelligence – Minimum Elements, issued jointly by CISA and G7 partners in May 2026.

How this relates to the CRA and device firmware

The document states plainly that "the European Union's Cyber Resilience Act (Regulation (EU) 2024/2847) requires manufacturers of products with digital elements to provide an SBOM as part of the technical documentation." The CRA's own text, however, sets a narrower, separate requirement: Annex I Part II point (1) calls for a machine-readable SBOM covering at least top-level dependencies, without formally adopting the CISA-led Minimum Elements as the legal standard. A device maker building firmware for the EU market should treat the CRA text as the compliance floor and the Minimum Elements as a stronger, internationally-recognized baseline to build toward — see our guide on building a firmware SBOM without source code for the binary-analysis side of generating one, and CSAF and VEX for device makers for pairing an SBOM with vulnerability status data, which the Minimum Elements document also calls out as a complementary practice.

SoftWSP extracts the component inventory from a firmware image by binary analysis and exports it as a CycloneDX 1.6 SBOM with each component's name, version and CPE or purl identifiers. It then matches those identifiers against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories, and drafts a cited vulnerability report for engineer review. Metadata such as the author signature, licences and artifact hashes come from the manufacturer's own release process: see device firmware security.

This guide summarises a public CISA-led, multi-government document; it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What are the SBOM Minimum Elements?

A baseline specification of what a Software Bill of Materials must contain: a set of Data Fields (information about the SBOM document and about each component) and a set of Practices and Processes (how an organization generates, updates and shares SBOM data). The current version is the 2026 Minimum Elements for a Software Bill of Materials (SBOM), published 29 July 2026 by CISA together with the NSA, FBI and 15 other national cybersecurity agencies, which "updates and replaces" NTIA's original 2021 document.

What data fields does a 2026-compliant SBOM need?

Seventeen fields across two groups. SBOM Metadata (about the document itself): SBOM Author, SBOM Author Signature, SBOM Data Format Name, SBOM Data Format Version, SBOM Generation Context, SBOM Timestamp, SBOM Tool Name, SBOM Tool Version, SBOM Version. Component Data (about the target component and its subcomponents): Component Producer, Component Name, Component Version, Component Identifiers, Component License, Component Hash Value, Component Hash Algorithm, Component Dependency Relationship.

What changed between the 2021 NTIA version and the 2026 update?

Ten fields are new (SBOM Author Signature, SBOM Data Format Name, SBOM Data Format Version, SBOM Generation Context, SBOM Tool Name, SBOM Tool Version, SBOM Version, Component Hash Value, Component Hash Algorithm, Component License). Supplier Name was renamed Component Producer, Other Unique Identifiers became Component Identifiers, Depth became the broader Coverage, and Automation Support became Machine-Processable Data (dropping SWID tags from the recommended format list). The Access Control element was removed and folded into Distribution and Delivery.

What are "Practices and Processes" as distinct from Data Fields?

Six baseline expectations for how an organization operates with SBOM data, not fields in the document itself: Accommodation of Updates to SBOM Data, Coverage (all components including transitive dependencies, no minimum depth), Distribution and Delivery, Explicitly Identifying Unknown Information, Frequency (a new or revised SBOM per software version or update), and Machine-Processable Data — the 2026 document names SPDX and CycloneDX as the two data formats "currently widely used by software ecosystem stakeholders."

Does the Cyber Resilience Act require an SBOM that meets these minimum elements?

The CRA (Regulation (EU) 2024/2847) requires manufacturers to provide an SBOM as part of the technical documentation, and the 2026 Minimum Elements document itself states this directly. The CRA's own Annex I Part II point (1) sets a separate, shorter EU requirement (a machine-readable SBOM covering at least top-level dependencies) and does not formally adopt the CISA-led Minimum Elements as its legal standard; the two overlap in substance but are not the same text. See our firmware SBOM guide for the CRA-specific requirement.

Sources

  1. CISA, NSA, FBI and 15 international partners: 2026 Minimum Elements for a Software Bill of Materials (SBOM), 29 July 2026
  2. CISA: 2026 Minimum Elements for a Software Bill of Materials (SBOM) — resource page
  3. NTIA: The Minimum Elements For a Software Bill of Materials (SBOM), 12 July 2021
  4. Executive Order 14028, Improving the Nation's Cybersecurity, Section 4(f) and 10(j), Federal Register Vol. 86 No. 93, 17 May 2021
  5. Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex I Part II, EUR-Lex
  6. CycloneDX 1.6 JSON schema (bom-1.6.schema.json), CycloneDX/specification on GitHub
  7. SPDX Specification 2.3, chapter 7: Package information
  8. SPDX Specification 3.0.1: SbomType vocabulary
Was this guide helpful?

In this cluster

SBOM Minimum Elements: what a compliant SBOM must contain