| name | PW.1.3_pw13 |
| description | Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log m... |
| category | input-validation |
| version | 1.1 |
| author | cyberstrike-official |
| tags | ["nist","sp800-218","ssdf","pw-1-3","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.3 PW.1.3
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
Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and vulnerability management systems) instead of creating proprietary implementations of security features and services. .Formerly PW.4.3
What to Check
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PW.1.3 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.3 PW.1.3 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.3 PW.1.3 in the software development lifecycle:
Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and vulnerability management systems) instead of creating proprietary implementations of security features and services. .Formerly PW.4.3
Risk Assessment
| Finding | Severity | Impact |
|---|
| PW.1.3 PW.1.3 not implemented |
