SSDF
Build and Test
A secure build process turns approved source into a reproducible and reviewable delivery activity. Testing checks the software and its dependencies, while the build environment protects the credentials, tools and artifacts used to produce a release.
How the work is approached
- Define controlled build inputs, runners and dependency handling
- Integrate relevant static, component and dynamic checks
- Record findings, exceptions and artifact generation results
Build and test evidence supports release decisions and later investigation. Teams can identify what was built, which checks ran and which unresolved findings were accepted for further review. The review should retain controlled build workflow so the team can explain the decisions later.
Useful starting information
- Build pipeline and runner configuration
- Dependency sources and testing tools
- Release gates and exception responsibilities
Outputs to agree and review
- Controlled build workflow
- Test results and finding dispositions
- Build records linking source and artifacts
A practical example
A pipeline runs code analysis and dependency checks on an approved revision, then tests the running application in an isolated environment. Findings have owners and release decisions are recorded.
What to watch for
The SAST, SCA and DAST labels describe different checks; no combination of tool names substitutes for a risk-appropriate testing strategy.
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 Build and Test worksheet (CSV)Continue within this service
Framework reference
NIST SSDF publication. Use the baseline and direction applicable to your environment and engagement.
