# PW.5.1_pw51

> PW.5.1_pw51 is an Agent Skill for development published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization’s requirements.

- Skill name: `PW.5.1_pw51`
- Category: [Development](https://www.openparable.com/skill/development/1)
- Source: https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-218_SSDF/PW_produce-well-secured-software/PW.5.1_pw51/SKILL.md
- Repository: CyberStrikeus/CyberStrike (1,211 GitHub stars when collected)

## SKILL.md

# PW.5.1 PW.5.1

> **Task of practice:** Create Source Code by Adhering to Secure Coding Practices (PW.5)

## High-Level Description

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

Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization’s requirements.

## What to Check

- [ ] Verify PW.5.1 PW.5.1 is integrated into SDLC
- [ ] Review CI/CD pipeline for PW.5.1 implementation
- [ ] Confirm automated tooling supports this practice

## How to Test

### Step 1: Review SDLC Documentation

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

Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization’s requirements.

## Risk Assessment

| Finding                       | Severity | Impact                                             |
| ----------------------------- | -------- | -------------------------------------------------- |
| PW.5.1 PW.5.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

---

Source: https://www.openparable.com/skill/development/pw-5-1-pw51 (OpenParable). Cite the canonical URL above.
