# How to get SBOMs from your suppliers (and check they are any good)

URL: https://sbombox.com/blog/how-to-get-sboms-from-suppliers
By SBOMBox SBOM experts. Published 2026-11-11

> Getting SBOMs from suppliers is one of the hardest parts of SBOM adoption. What to ask for, contract wording that works, and how to check what arrives.

Short answer: ask for a machine-readable SBOM (CycloneDX or SPDX) for every release you receive, put the request in the contract, and check each file on arrival. Under the CRA, components you integrate are your responsibility, so a supplier's gap becomes yours.

## Why this is hard

ENISA's 2026 report on SBOM adoption lists obtaining SBOMs from suppliers alongside completeness and data quality as the main challenges organisations face. Many suppliers have never been asked, and some see an SBOM as exposing their product.

## What to ask for

- Format: CycloneDX or SPDX, in JSON. Not a PDF or spreadsheet.
- Frequency: one SBOM per release you receive, delivered with the release.
- Content: at least CISA's [2026 minimum elements](https://sbombox.com/blog/sbom-minimum-elements), which include hashes, licences and the generating tool.
- Depth: transitive dependencies, not only top-level ones.
- VEX or advisories for known vulnerabilities, so you do not have to triage every scanner hit yourself.
- A named security contact and the product's support period.

## Contract wording that works

Keep it short and specific. For example: 'Supplier shall deliver, with each release, a Software Bill of Materials in CycloneDX or SPDX JSON format meeting the CISA 2026 minimum elements, and shall notify Customer of actively exploited vulnerabilities affecting delivered components within 48 hours of becoming aware.' Adapt the timings to your own CRA reporting obligations, and have counsel review it.

## When the supplier says no

- Offer to accept it under NDA, or to receive VEX statements instead of the full SBOM.
- Ask for a list of open-source components and versions as a stopgap.
- Generate a binary-analysis SBOM yourself, and record that it is your own reconstruction.
- Weigh the refusal in supplier selection. It is evidence about their security maturity.

## Keep it current

Agree a format and delivery channel up front, such as a shared portal or an artifact repository, so files do not arrive scattered across email threads. An SBOM from last year's release says little about the one you deployed this week. Tie delivery to the release process, store each version, and ask for VEX updates when a new critical vulnerability appears in a component the supplier ships. Review supplier SBOM quality at least once a year as part of supplier assessment.

## Check what arrives

Do not file supplier SBOMs unread. Validate the schema, check that versions and identifiers are present, and match it against vulnerability feeds. Run any file through the [free SBOM checker](https://sbombox.com/audit) to see its score and gaps in seconds. In SBOMBox, supplier SBOMs are stored and monitored alongside your own.
