Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2)_review-the-software-design-to-verify-compliance-with-securit
Testing & QualityReview the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2)_review-the-software-design-to-verify-compliance-with-securit is an Agent Skill for testing & quality published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Help ensure that the software will meet the security requirements and satisfactorily address the identified risk information.
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/Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2)_review-the-software-design-to-verify-compliance-with-securit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/review-the-software-design-to-verify-compliance-with-security-requirements-and-risk-inform-43512153, 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.
Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) Review the Software Design to Verify Compliance with Security Requirements and Risk Information
High-Level Description
Practice Group: Produce Well-Secured Software (PW) Framework: NIST SP 800-218 SSDF v1.1
Help ensure that the software will meet the security requirements and satisfactorily address the identified risk information.
What to Check
- Verify Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) Review the Software Design to Verify Compliance with Security Requirements and Risk Information is integrated into SDLC
- Review CI/CD pipeline for Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) implementation
- Confirm automated tooling supports this practice
How to Test
Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.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 Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) Review the Software Design to Verify Compliance with Security Requirements and Risk Information 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 Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) Review the Software Design to Verify Compliance with Security Requirements and Risk Information in the software development lifecycle:
Help ensure that the software will meet the security requirements and satisfactorily address the identified risk information.
Risk Assessment
| Finding | Severity | Impact |
|---|---|---|
| Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2) Review the Software Design to Verify Compliance with Security Requirements and Risk Information 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