| name | PW.1.1_pw11 |
| description | Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software. |
| category | input-validation |
| version | 1.1 |
| author | cyberstrike-official |
| tags | ["nist","sp800-218","ssdf","pw-1-1","pw","secure-development","task"] |
| tech_stack | ["any"] |
| cwe_ids | ["CWE-20"] |
| chains_with | [] |
| prerequisites | ["Design Software to Meet Security Requirements and Mitigate Security Risks (PW.1)"] |
| severity_boost | {} |
PW.1.1 PW.1.1
Task of practice: Design Software to Meet Security Requirements and Mitigate Security Risks (PW.1)
High-Level Description
Practice Group: Produce Well-Secured Software (PW)
Framework: NIST SP 800-218 SSDF v1.1
Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.
What to Check
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PW.1.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.1.1 PW.1.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.1.1 PW.1.1 in the software development lifecycle:
Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.
Risk Assessment
| Finding | Severity | Impact |
|---|
| PW.1.1 PW.1.1 not implemented | Medium | Secure Development - Produce Well-Secured Software |
CWE Categories
