PW.2.1 PW.2.1
Task of practice: Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2)
High-Level Description
Practice Group: Produce Well-Secured Software (PW) Framework: NIST SP 800-218 SSDF v1.1
Have 1) a qualified person (or people) who were not involved with the design and/or 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets all of the security requirements and satisfactorily addresses the identified risk information.
What to Check
- Verify PW.2.1 PW.2.1 is integrated into SDLC
- Review CI/CD pipeline for PW.2.1 implementation
- Confirm automated tooling supports this practice
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PW.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 PW.2.1 PW.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 PW.2.1 PW.2.1 in the software development lifecycle:
Have 1) a qualified person (or people) who were not involved with the design and/or 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets all of the security requirements and satisfactorily addresses the identified risk information.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| PW.2.1 PW.2.1 not implemented | Medium | Secure Development - Produce Well-Secured Software |
CWE Categories
| CWE ID | Title |
|---|---|
| CWE-20 | Improper Input Validation |
References
Checklist
- Practice documented in SDLC policy
- Tooling configured and operational
- Development team trained
- Evidence of consistent application
- Periodic review scheduled