Over the past five years, three US sources have shaped what buyers expect from an SBOM: Executive Order 14028, the National Security Agency's SBOM management guidance, and the 2026 Minimum Elements for an SBOM published by CISA this summer. Together they have moved the SBOM from a nice-to-have inventory to a document that is requested in procurement, checked against what was delivered, and used to respond when the next critical vulnerability lands.

What does Executive Order 14028 require for SBOMs?

Executive Order 14028 asks federal agencies to buy software from suppliers that follow secure development practices, including providing an SBOM for each product. It does not, on its own, create a legal duty for private companies. That duty arrives through acquisition policy and contract clauses.

Executive Order 14028, Improving the Nation's Cybersecurity, was signed on 12 May 2021. Its fourth section, on enhancing software supply chain security, starts with a diagnosis: commercial software development often lacks transparency, a strong focus on resisting attack, and adequate controls against tampering. The order gives priority to critical software, meaning software that runs with elevated privileges or has direct access to networking and computing resources.

Section 4 tasked the National Institute of Standards and Technology (NIST) with identifying standards and best practices for secure software development. It listed providing a purchaser with an SBOM, directly or on a public website, among the practices expected of federal suppliers. The National Telecommunications and Information Administration (NTIA) was asked to define the minimum elements of an SBOM, which it published on 12 July 2021.

This is where many articles go wrong. An executive order binds the executive branch. It reaches a vendor only once it has been turned into acquisition policy and contract terms. That is why so much of the order consists of instructions to the Office of Management and Budget (OMB), CISA, NIST and the Federal Acquisition Regulation (FAR) Council. Federal agencies can require SBOMs as part of secure procurement, and increasingly do. The order made that possible. It did not make it automatic.

How did EO 14028 become a procurement requirement (SSDF and OMB M-22-18)?

EO 14028 became a procurement requirement through NIST's Secure Software Development Framework (SP 800-218) and OMB memoranda M-22-18 and M-23-16. Federal software suppliers must now sign a CISA self-attestation form confirming that they follow secure development practices.

 The translation happened in three steps:

  1. NIST turned the order's software security mandate into Special Publication 800-218, the Secure Software Development Framework (SSDF).
  2. OMB made it a procurement duty. Memorandum M-22-18 required agencies to obtain supplier attestation of conformance with the SSDF. M-23-16 updated it so that agencies use only software from suppliers that comply with SP 800-218.
  3. CISA provided the instrument itself: a common secure software development self-attestation form, signed by the chief executive or a designee.

What changed for SSDF attestation in 2025 with EO 14144 and EO 14306?

EO 14144 (January 2025) tightened attestation requirements. EO 14306 (June 2025) removed the validation-artifact and audit requirements again. The SSDF self-attestation obligation itself remains in place.

Executive Order 14144, signed on 16 January 2025, tightened the regime. It called for:

  • machine-readable attestations aligned with SP 800-218 and SP 800-218A
  • supporting validation artifacts
  • a list of federal customers using the attested software
  • CISA verification, with false attestations referred to the Department of Justice

Executive Order 14306, signed on 6 June 2025, pulled part of that back. It removed the requirement to submit validation artifacts and the mandate for CISA to audit a sample of attestations. The underlying self-attestation obligation under OMB M-22-18 and its successors stayed in place.

The lesson is not that federal pressure eased. It was redistributed. The formal audit machinery is lighter, but False Claims Act exposure never depended on an executive order, and agencies and prime contractors have moved the evidence request into source selection. A supplier that cannot show what is inside its product still loses the bid. It simply loses it commercially rather than through an audit finding.

What does the NSA say about SBOMs and binary analysis?

The NSA treats the SBOM as an operational tool, not a compliance file. For software developed under contract, it recommends generating SBOMs from source code at build time. Where source code or build information is not available, such as legacy software, it recommends obtaining SBOMs and vulnerability information through binary analysis.

On 14 December 2023, the office of the National Manager for National Security Systems published Recommendations for Software Bill of Materials (SBOM) Management. The guidance is aimed at owners of National Security Systems and was built on hands-on evaluation of commercial SBOM management tools.

The NSA links the SBOM to three continuous activities:

  • risk decisions when acquiring and deploying software
  • vulnerability management during operations
  • incident response when new vulnerabilities appear

None of these is a one-off event. They repeat every time software is added, updated or retired.

The most quoted recommendation in the document is to obtain SBOMs and related vulnerability and code quality information from analysis of software binaries. That information includes Common Vulnerabilities and Exposures (CVEs) and Common Weakness Enumerations (CWEs). The NSA is candid that the accuracy and timeliness of binary analysis still need work. It nevertheless presents binary analysis as the way forward for legacy software without accessible source code or build information.

Both halves matter. For software developed under contract, the guidance says the SBOM should be generated from source code at the build stage. The honest reading is that build-time generation makes the claim and binary analysis tests it. They are two inputs to one pipeline, not competing philosophies. The NSA's tooling requirements reflect this by asking for SBOM generation from build environments, binary files and system registry queries.

What contract clauses does the NSA recommend for SBOM verification?

The NSA advises buyers to negotiate limited rights to reverse-engineer delivered software so they can validate SBOMs. Buyers should also require complete component data, integrity proofs and secure-by-design metrics from suppliers.

Validating a supplier's SBOM against a delivered binary can require techniques that a standard software license forbids. The NSA therefore advises buyers to negotiate limited rights to reverse-engineer delivered software for the specific purpose of validating SBOMs and resolving discrepancies. At that point, binary verification stops being a tooling choice and becomes a clause someone has to negotiate before signature.

The NSA's contract expectations are concrete. They include:

  • component information at minimum-element level for all delivered software
  • third-party dependencies, both open source and proprietary
  • runtime dependencies and container manifests
  • digital signatures or authenticated hashes to prove integrity
  • metrics that track the supplier's secure-by-design performance

Buyers are also expected to check every SBOM for accuracy and completeness on delivery, not file it unread.

What is new in CISA's 2026 Minimum Elements for an SBOM?

On 29 July 2026, CISA, the NSA, the FBI and fifteen international partners published 2026 Minimum Elements for a Software Bill of Materials (SBOM), version 2.1. It replaces the NTIA minimum elements from 2021, adds new elements such as generation context, component hashes and author signatures, and makes SBOMs far easier to verify.

The US position on SBOMs is now expressed jointly and internationally.

The new elements, and why they matter:

New element

Why it matters

SBOM Generation Context

Tells the consumer how the SBOM was produced, so build-time and binary-derived SBOMs are declared rather than guessed.

Component Hash Value

Gives independent analysis a basis for comparing what the supplier declared with what actually shipped.

Component Hash Algorithm

Makes those hash comparisons reproducible.

SBOM Author Signature

Makes the provenance of the SBOM itself verifiable.

SBOM Data Format Name and Version

Shows which standard and version the SBOM follows.

SBOM Tool Name and Version

Identifies the tool that generated the SBOM, so consumers can judge its reliability.

SBOM Version

Tracks revisions of the same SBOM over time.

Component License

Records licensing information for each component.

When a third party generates an SBOM for software it did not write, which is exactly the binary scanning case, the two fields now differ in plain sight.

Several existing elements were substantially updated, including Component Identifiers, Coverage, and Explicitly Identifying Unknown Information. The Access Controls element was folded into Distribution and Delivery.

CISA is careful to say the minimum elements create no new legal requirements. They refine how organizations should request, generate and analyze SBOMs. They apply to all software, including open source, AI systems and software as a service (SaaS).

 

Do US SBOM requirements align with the EU Cyber Resilience Act and other countries?

The EU Cyber Resilience Act requires an SBOM in the technical documentation of products with digital elements, and Germany, Japan and India have published their own SBOM guidance. One well-run SBOM process can serve several regulators at once.

 

The 2026 minimum elements themselves point to the EU Cyber Resilience Act (CRA), Regulation (EU) 2024/2847. The CRA requires manufacturers of products with digital elements to include an SBOM in their technical documentation. CRA reporting of actively exploited vulnerabilities has applied since 11 September 2026, and the full obligations follow on 11 December 2027.

Other countries are moving in the same direction:

  • Germany's BSI has published technical requirements in TR-03183-2.
  • Japan's METI has issued guidance for software suppliers.
  • India's CERT-In has published guidelines on bills of materials.

Internationally, CISA and the NSA joined nineteen international organizations in September 2025 behind A Shared Vision of Software Bill of Materials for Cybersecurity. In May 2026, CISA and G7 partners extended the concept to artificial intelligence.

How do you build an SBOM program that meets US requirements?

Generate SBOMs at build time, verify them with binary analysis, reconcile the two outputs, document how each SBOM was produced, and write the requirements into your contracts.

The program that follows from these documents fits on one page. Most organizations are missing at least half of it.

Generate SBOMs at build time by default. This is what the NSA asks for on contracted software, and it captures dependency data that no after-the-fact analysis can fully reconstruct.

1

Add binary analysis as a check, not a replacement. Cover acquired components, vendor-delivered binaries, container images and legacy systems with no build pipeline.

2

Reconcile the two outputs and keep the record. The new hash elements exist so that declared components can be compared with delivered artifacts. That comparison report is what an auditor or prime contractor wants to see.

3

Record how every SBOM was produced. Use Generation Context, Tool Name and Version, and Author, so downstream consumers can judge each SBOM's completeness.

4

Put the requirements into contracts, not internal wikis. Keep the evidence behind your SSDF self-attestation current. The obligation to attest survived 2025, and the expectation that you can prove it never depended on an audit clause.

5

Tooling checklist. When choosing tooling, use the NSA's functional list as a checklist:

  • support for both CycloneDX and SPDX
  • JSON and XML import with quality checks
  • format conversion and aggregation
  • per-component hashes with Package URL (PURL) or Common Platform Enumeration (CPE) identifiers
  • daily vulnerability updates
  • organization-specific policy rules
  • tracking of remediation over time

US SBOM requirements: frequently asked questions

Get in touch

Talk to our specialists and learn how our Open-Source Management Services can help your business.