pw-4-2-pw42

name	PW.4.2_pw42
description	Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot
category	input-validation
version	1.1
author	cyberstrike-official
tags	["nist","sp800-218","ssdf","pw-4-2","pw","secure-development","task"]
tech_stack	["any"]
cwe_ids	["CWE-20"]
chains_with	[]
prerequisites	["Reuse Existing, Well-Secured Software When Feasible Instead of Duplicating Functionality (PW.4)"]
severity_boost	{}

PW.4.2 PW.4.2

Task of practice: Reuse Existing, Well-Secured Software When Feasible Instead of Duplicating Functionality (PW.4)

High-Level Description

Practice Group: Produce Well-Secured Software (PW) Framework: NIST SP 800-218 SSDF v1.1

Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot be better met by third-party software components.

What to Check

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

How to Test

Step 1: Review SDLC Documentation

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

Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot be better met by third-party software components.

Risk Assessment

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

CWE Categories