CISA’s 2025 SBOM Guidance Adds Hashes, Licenses, Tool Metadata, and Context
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
- Sarah Gooding

On August 22, 2025, the Cybersecurity and Infrastructure Security Agency (CISA) released a draft update to its Minimum Elements for a Software Bill of Materials (SBOM) and opened it for public comment through October 3, 2025.
An SBOM is essentially a software inventory, a detailed list of the components that make up an application. By making software composition transparent, SBOMs give organizations the ability to identify vulnerabilities, assess risks, and make more informed decisions about the software they use. As adoption has expanded across both government and industry, the need for richer, machine-readable, and interoperable formats has become clear.
The 2025 draft builds on the 2021 NTIA SBOM Minimum Elements, reflecting advances in tooling, adoption, and implementation. The changes are designed to make SBOMs more verifiable, transparent, and operationally useful in security workflows.
CISA explained the reason for updating the SBOM minimum elements in the draft as follows:
SBOM implementation practices have advanced significantly since the 2021 document was published. Increased adoption and implementation from stakeholders across the software ecosystem has uncovered new use cases and applications for SBOM data. SBOM tooling, in response to the increased adoption and implementation of SBOM, has matured far beyond the capabilities and functionalities of tools available in 2021. These advancements allow organizations requesting SBOMs to demand more information about their software components and supply chain than they could have in 2021.
What Has Changed in 2025
#The updated draft introduces four entirely new minimum data fields:
- Component hash: a cryptographic value for verifying components
- License: identifying how components are licensed and any proprietary restrictions
- Tool name: indicating which tool or tools generated the SBOM
- Generation context: specifying whether the SBOM was created pre-build, during build, or post-build
Several existing elements have also been revised for clarity. SBOM Author and Software Producer are now better defined, reducing ambiguity around who generates an SBOM versus who creates the software. Component Version allows creation date as a fallback when no version is provided. Software Identifiers have been expanded to include identifiers such as OmniBOR and SWHID. Dependency Relationship now requires documenting forks and backports. The former Depth element has been replaced by Coverage, which accounts for both vertical and horizontal breadth of component information. Known Unknowns must now distinguish between information that is truly unknown and information that is intentionally withheld.
One element has been removed: Access Controls. Instead, access-related considerations are now included under Distribution and Delivery, reflecting more mature practices for SBOM sharing.

From Inventory to Operational Tool
#The 2021 NTIA guidance positioned SBOMs primarily as inventories: standardized lists of the components inside software. This updated draft reflects a shift in how SBOMs are expected to be used operationally, for security and compliance workflows.
With component hashes, SBOMs can now be validated against actual artifacts, strengthening integrity checks and limiting the risk of tampering. Including license data extends their usefulness beyond security into compliance and legal risk management. Tool metadata provides provenance, giving consumers insight into how the SBOM was produced and whether it can be trusted. Generation context clarifies whether an SBOM reflects source code, build-time information, or binary analysis, helping consumers understand both its strengths and limitations.
The new elements show CISA’s intent to make SBOMs practical at scale and push them toward being a reliable foundation for automation, where the quality of SBOM data can directly determine how effectively organizations manage software risk.
Public Comment Process
#The 2025 update reflects how SBOM practices are maturing but the draft also highlights areas where SBOM practices will need further development, including how to handle cloud and SaaS environments, AI systems, and validation. These discussions show that while the minimum elements are advancing, the work of adapting SBOMs to new technologies and use cases is still ongoing.
The draft guidance is open for feedback until October 3, 2025. CISA is encouraging developers, security professionals, open source maintainers, vendors, academics, and other stakeholders to provide input via the Federal Register. In particular, the agency is seeking feedback on whether any elements should be removed, whether additional elements should be required, whether the updated definitions are clear enough to support automation, and whether certain technologies or sectors face challenges in applying the minimum elements.
The full draft is available as a 17-page PDF: 2025 Minimum Elements for a Software Bill of Materials (SBOM).




