PS.3.2_ps32

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

• Verify PS.3.2 PS.3.2 is integrated into SDLC
• Review CI/CD pipeline for PS.3.2 implementation
• Confirm automated tooling supports this practice

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

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

CWE Categories

References

• NIST SP 800-218 SSDF v1.1
• NIST SSDF Practices
• NIST OSCAL Content

Checklist

• Practice documented in SDLC policy
• Tooling configured and operational
• Development team trained
• Evidence of consistent application
• Periodic review scheduled