| name | PS.3.2_ps32 |
| description | Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials .SBOM). |
| category | authorization |
| version | 1.1 |
| author | cyberstrike-official |
| tags | ["nist","sp800-218","ssdf","ps-3-2","ps","secure-development","task"] |
| tech_stack | ["git","ci-cd","docker"] |
| cwe_ids | ["CWE-284"] |
| chains_with | [] |
| prerequisites | ["Archive and Protect Each Software Release (PS.3)"] |
| severity_boost | {} |
PS.3.2 PS.3.2
Task of practice: Archive and Protect Each Software Release (PS.3)
High-Level Description
Practice Group: Protect Software (PS)
Framework: NIST SP 800-218 SSDF v1.1
Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials .SBOM).
What to Check
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PS.3.2 practice implementation.
Step 2: Verify Tooling
# Check CI/CD pipeline configuration
# Verify security tools are integrated
# Example: Check for SAST/DAST in pipeline
grep -r "security\|scan\|sast\|dast" .github/workflows/ 2>/dev/null
grep -r "security\|scan" Jenkinsfile 2>/dev/null
Step 3: Assess Developer Awareness
Verify development team understands and follows PS.3.2 PS.3.2 practice.
Tools
| Tool | Purpose | Usage |
|---|
| github-security-mcp | Check repository security settings | github_security_* tools |
| Manual Review | SDLC process review | Documentation and interviews |
Remediation Guide
Implement PS.3.2 PS.3.2 in the software development lifecycle:
Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials .SBOM).
Risk Assessment
| Finding | Severity | Impact |
|---|
| PS.3.2 PS.3.2 not implemented | Medium | Secure Development - Protect Software |
CWE Categories
| CWE ID | Title |
|---|
| CWE-284 | Improper Access Control |
References
