An SBOM intake checklist starts with one question: does this component list describe the release you actually deploy? A tidy file can still be attached to the wrong edition, build or platform. Ask for the file and the release identifier together, then document where its coverage ends.
Contents
Collect evidence for the SBOM intake checklist
- The machine-readable SBOM and its format and version.
- The exact product edition, build and platform, plus a release note or other record connecting the file to that delivery.
- A description of component coverage, including whether nested dependencies are represented and which items are outside scope.
Keep the original supplier file alongside your intake note. Use a shared ticket to record your questions and the date answered so a later reviewer can distinguish a verified detail from a working assumption.
Use this release-matching worksheet
| Check | Evidence to record | When to send it back |
|---|---|---|
| Artifact identity | Edition, build and platform match the order or deployment record. | The file only names the product family. |
| Component identity | Sampled components have names, versions and supplier or package identifiers where available. | Versions are missing without an explanation. |
| Coverage | The supplier explains which dependency levels and bundled items the file covers. | There is no way to distinguish exclusions from omissions. |
| Refresh | A named owner can identify which release requires a replacement SBOM. | Updates are delivered with no release mapping. |
Work through a mismatched release
In this fictional example, procurement orders Widget Enterprise 4.2 and the deployment record names Widget Enterprise 4.2.1 for Linux x86-64. The supplier sends widget-4.2.json. A product-family match leaves the exact build and platform unconfirmed.
The deployment owner records the artifact identifier from the deployment record. Procurement attaches the supplier response to the ticket. If the supplier names the Linux x86-64 build and connects it to the submitted file or provides a replacement file for that build, the intake owner records the evidence and updates the status. If an optional plug-in bundle falls outside the supplier’s scope, the owner records that exclusion and assigns a separate follow-up.
Copy this SBOM intake checklist into your ticket
- Product, edition and build: [from deployment record]
- Platform and artifact identifier: [record ID, package ID or digest if available]
- Supplier SBOM file, format and revision: [attach original]
- Release mapping evidence: [supplier response or release note]
- Coverage and exclusions: [dependency levels, bundled components, unresolved gaps]
- Intake decision, owner and due date: [status / name / date]
Send a focused supplier question
“Can you confirm whether the attached SBOM describes Widget Enterprise 4.2.1 for Linux x86-64, identifier [ID]? Please identify the applicable file and revision, and list bundled items or nested dependencies outside its scope. If this file covers a different build, please send the matching SBOM.”
Record the intake decision and remaining work
Use accepted for inventory when the intake owner confirms the release mapping and documents the coverage. Keep exclusions and their owners visible beside that status. Use clarification required when the mapping is missing or the scope is ambiguous. Track security or deployment decisions on their own record, with links back to the intake evidence.
For a fuller supplier baseline, consult CISA’s software supply chain guidance on open-source software and SBOMs.
Reopen the SBOM intake checklist when the deployment changes
Set a review trigger the deployment owner can actually observe. A new build, a platform change or a change in bundled components can break a previous mapping. Carry forward the old record as history and open a new intake entry tied to the new delivery. If the supplier says the old file still applies, record which artifact it covers and how the supplier confirmed that.
For a product installed on two platforms, give each deployment its own mapping row. A matching file for the Linux build does not establish coverage for another platform. Keep the supplier’s version of the SBOM as received and put local judgments in the ticket. This preserves both the original evidence and the context needed for the next review.
At handoff, ask a teammate to locate the deployment identifier, the matching SBOM and the remaining exclusions using only the ticket. If they cannot reconstruct the decision, add the missing evidence before closing the intake.
For a companion approach to recording evidence and decisions, see Kioptrix’s portable documentation structure. Use the intake ticket to keep the supplier file, deployment record and decision easy to find.
Example intake ticket with a recorded exception
Suppose the deployment record lists an application build for Linux and an optional reporting module installed only on a subset of hosts. The supplier reply confirms the release mapping for the main application but states that the reporting module is provided separately. Attach the response, mark the main application as accepted for inventory, and create a follow-up entry for the module with a named owner.
Record how the owner can find the deployed build in the asset record. If two teams deploy the same product with different optional modules, capture both configurations. A single product-level status leaves the next reviewer guessing which scope was checked.
Use a second reviewer to test the handoff
Ask the reviewer to answer three questions using only the ticket. Where is the original supplier file? What proves that it maps to this deployed artifact? Which dependency or optional item is still outstanding? Add missing links or scope notes before closing the SBOM intake checklist.
Set a review date for any exception that could persist across releases. If the supplier replaces the file after correcting an omission, keep the prior revision linked as evidence and point the active entry at the new one.