SSDF
Release Integrity
Release integrity connects the software delivered to customers with its approved source, build process and recorded components. Provenance, signing and component inventories help explain what was released and support later vulnerability and incident investigations.
How the work is approached
- Link release artifacts to approved source and build records
- Protect signing operations and distribution channels
- Maintain component and version records, including an SBOM where required
Customers and internal teams can identify a release and trace its origin. The organization can respond more quickly when a component or build process is later found to be affected. The review should retain release manifest and provenance records so the team can explain the decisions later.
Useful starting information
- Release artifacts and distribution channels
- Signing and provenance arrangements
- Component and supported-version inventories
Outputs to agree and review
- Release manifest and provenance records
- Signing and verification procedures
- Component inventory and SBOM handling plan
A practical example
A customer reports a problem with a specific release. The release record identifies the source revision, build results, component versions and signature verification steps needed to investigate the delivered package.
What to watch for
An SBOM is a component record, not a security certificate. Keep it aligned with the actual artifact and supported release.
Scope, ownership and acceptance criteria should be agreed for the actual environment. The example describes a planning approach, not a promised result or a determination of compliance.
Planning worksheet
Use this short worksheet to record your starting information, action owners and evidence locations before a detailed review.
Download the Release Integrity worksheet (CSV)Continue within this service
Framework reference
NIST SSDF publication. Use the baseline and direction applicable to your environment and engagement.
