# Release inventory and SBOM review

CISA software attestation | Worked example with fictional data

Step: Prepare and validate requested SBOM evidence
Owner: Release engineering + product security + vendor management
When: Before an applicable submission or request deadline

## Gather first
- Buyer requirements
- Deployment manifest
- Dependency outputs
- Release inventory
- Distribution instructions

## How to prepare it
1. Confirm format, fields, version and scope with the buyer. For a cloud runtime request, identify production components and images that actually run for the covered service.
2. Match inventory objects to immutable release references, component identities and versions. Check output against the requested syntax and compare a sample to deployment records.
3. Document gaps, what is excluded and when the inventory was generated. Store approved output and send it through the required channel only after a handling review.

## Example

### Fictional review result
The initial inventory reflects the web image but misses a production job image. The owner adds the missing components, reruns validation and records both image references in the review memo.

## Review
The software inventory can be tied to the intended product release and inspected by the buyer.

## Handoff
Save the approved artifact and receipt with the release record.

Use the current rules and any prescribed forms for your engagement.
