PW.1.2_pw12
ProductivityPW.1.2_pw12 is an Agent Skill for productivity published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Track and maintain the software’s security requirements, risks, and design decisions.
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.1.2_pw12/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/pw-1-2-pw12, 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.1.2 PW.1.2
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
Track and maintain the software’s security requirements, risks, and design decisions.
What to Check
- Verify PW.1.2 PW.1.2 is integrated into SDLC
- Review CI/CD pipeline for PW.1.2 implementation
- Confirm automated tooling supports this practice
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of PW.1.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.1.2 PW.1.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.1.2 PW.1.2 in the software development lifecycle:
Track and maintain the software’s security requirements, risks, and design decisions.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| PW.1.2 PW.1.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