pw-1-2-pw12

name	PW.1.2_pw12
description	Track and maintain the software’s security requirements, risks, and design decisions.
category	input-validation
version	1.1
author	cyberstrike-official
tags	["nist","sp800-218","ssdf","pw-1-2","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.2 PW.1.2

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

Track and maintain the software’s security requirements, risks, and design decisions.

What to Check

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

How to Test

Step 1: Review SDLC Documentation

Examine development lifecycle documentation for evidence of PW.1.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 PW.1.2 PW.1.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 PW.1.2 PW.1.2 in the software development lifecycle:

Track and maintain the software’s security requirements, risks, and design decisions.

Risk Assessment

Finding	Severity	Impact
PW.1.2 PW.1.2 not implemented	Medium	Secure Development - Produce Well-Secured Software

CWE Categories

CWE ID	Title
CWE-20	Improper Input Validation

References