Back to skills
SKILL.md
PW.8.1 Pw81
ASecurityDetermine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if
- 3,518 stars
- 0 votes
- 0 copies
- 2 views
- Added September 3, 2026
Works with
Security analysis
100/100npx -y skills add CyberStrikeus/CyberStrike --skill PW.8.1_pw81 --agent claude-codeAre you the author of PW.8.1 Pw81?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-pw-8-1-pw81)---
name: "PW.8.1_pw81"
description: "Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if"
category: "input-validation"
version: "1.1"
author: "cyberstrike-official"
tags:
- nist
- sp800-218
- ssdf
- pw-8-1
- pw
- secure-development
- task
tech_stack:
- any
cwe_ids:
- CWE-20
chains_with: []
prerequisites:
- Test Executable Code to Identify Vulnerabilities and Verify Compliance with Security Requirements (PW.8)
severity_boost: {}
---
# PW.8.1 PW.8.1
> **Task of practice:** Test Executable Code to Identify Vulnerabilities and Verify Compliance with Security Requirements (PW.8)
## High-Level Description
**Practice Group:** Produce Well-Secured Software (PW)
**Framework:** NIST SP 800-218 SSDF v1.1
Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if so, which types of testing should be used.
## What to Check
- [ ] Verify PW.8.1 PW.8.1 is integrated into SDLC
- [ ] Review CI/CD pipeline for PW.8.1 implementation
- [ ] Confirm automated tooling supports this practice
## How to Test
### Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PW.8.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.8.1 PW.8.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.8.1 PW.8.1 in the software development lifecycle:
Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if so, which types of testing should be used.
## Risk Assessment
| Finding | Severity | Impact |
| ----------------------------- | -------- | -------------------------------------------------- |
| PW.8.1 PW.8.1 not implemented | Medium | Secure Development - Produce Well-Secured Software |
## CWE Categories
| CWE ID | Title |
| ------ | ------------------------- |
| CWE-20 | Improper Input Validation |
## References
- [NIST SP 800-218 SSDF v1.1](https://csrc.nist.gov/pubs/sp/800/218/final)
- [NIST SSDF Practices](https://csrc.nist.gov/projects/ssdf)
- [NIST OSCAL Content](https://github.com/usnistgov/oscal-content)
## Checklist
- [ ] Practice documented in SDLC policy
- [ ] Tooling configured and operational
- [ ] Development team trained
- [ ] Evidence of consistent application
- [ ] Periodic review scheduled
Attribution
Related skills
View all in security →Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.