Guides · Software bill of materials

Asking for a software bill of materials

10 November 2026 · Escherbridge

CISA describes an SBOM as a nested inventory — a list of ingredients that make up software. The 29 July 2026 joint guidance updates and replaces the 2021 NTIA minimum elements. Asking a producer for that inventory is a delivery practice. The inventory itself does not make the software safe, and it is not a certification OSGA or a client holds. This is the delivery-firm reading of the same official sources used on PrimusNeo's SBOM page. It does not invent a second definition.

CISA SBOM landing. An SBOM "is a nested inventory, a list of ingredients that make up software components," and has emerged as "a key building block in software security and software supply chain risk management."

2026 Minimum Elements for a Software Bill of Materials (SBOM), 29 July 2026 (Version 2.1). Updates and replaces the NTIA 2021 minimum elements. "The elements outlined in this document set forth the minimum expected data fields and the practices and processes for an SBOM." Intended audience: organizations that produce, procure, or operate software. Key actions: request, generate, and use tools to ingest and analyze SBOMs that satisfy the updated minimum elements. Minimum elements apply to all software; some types (the document names artificial intelligence and software as a service in cloud environments) may require additional elements; "Any effort to improve software transparency… should begin with the application of minimum elements." Appendix A, Table 1, is the official data-field list. The opened table includes component dependency relationship, hash algorithm and value, identifiers, license, name, producer, version; SBOM author, author signature, data format name and version, generation context, timestamp, tool name and version, and SBOM version. This page points at that table rather than inventing a house subset.

What a delivery program can ask for

You can ask a producer for an SBOM that meets the published minimum elements. That request is not a finding that the software is safe. NIST SSDF: secure software development practices is the practice-framework sibling already in batch 1. This page has no exploit steps, no invented clients, and no politics.

The first conversation still ends with a yes, a no, or a better idea, at Start. The dashboard remains "opening soon."

The useful next step is to ask for an SBOM that meets the 2026 minimum elements, not only for a file with that name. If something on this page is wrong, write to us.

Author: Escherbridge. Last reviewed: 2026-11-10, America/Denver.