cyberstrikeus PS.2.1 PS.2.1
Task of practice: Provide a Mechanism for Verifying Software Release Integrity (PS.2)
High-Level Description
Practice Group: Protect Software (PS) Framework: NIST SP 800-218 SSDF v1.1
Make software integrity verification information available to software acquirers.
What to Check
- Verify PS.2.1 PS.2.1 is integrated into SDLC
- Review CI/CD pipeline for PS.2.1 implementation
- Confirm automated tooling supports this practice
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PS.2.1 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.2.1 PS.2.1 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.2.1 PS.2.1 in the software development lifecycle:
Make software integrity verification information available to software acquirers.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| PS.2.1 PS.2.1 not implemented | Medium | Secure Development - Protect Software |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-284 | Improper Access Control |
References
Checklist
- Practice documented in SDLC policy
- Tooling configured and operational
- Development team trained
- Evidence of consistent application
- Periodic review scheduled