COPRSETR WORKSHEET
Release inventory and SBOM review
CISA software attestation · Step 3 · Prepare and validate requested SBOM evidence- Who prepares it
- Release engineering + product security + vendor management
- When to prepare it
- Before an applicable submission or request deadline
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- 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.
Gather first
- Buyer requirements
- Deployment manifest
- Dependency outputs
- Release inventory
- Distribution instructions
How to prepare it
- 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.
- Match inventory objects to immutable release references, component identities and versions. Check output against the requested syntax and compare a sample to deployment records.
- 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.
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.