PW.4.2_pw42
DevelopmentPW.4.2_pw42 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.
Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/NIST/SP800-218_SSDF/PW_produce-well-secured-software/PW.4.2_pw42/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/pw-4-2-pw42, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
| CWE ID | Title |
|---|---|
| CWE-20 | Improper Input Validation |
References
Checklist
- Practice documented in SDLC policy
- Tooling configured and operational
- Development team trained
- Evidence of consistent application
- Periodic review scheduled