Help reduce the frequency of vulnerabilities in the future.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill analyze-vulnerabilities-to-identify --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Analyze Vulnerabilities To Identify?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-analyze-vulnerabilities-to-identify)More formats (shields.io, HTML) on the badges page.
---
name: "Analyze Vulnerabilities to Identify Their Root Causes (RV.3)_analyze-vulnerabilities-to-identify-their-root-causes"
description: "Help reduce the frequency of vulnerabilities in the future."
category: "configuration"
version: "1.1"
author: "cyberstrike-official"
tags:
- nist
- sp800-218
- ssdf
- analyze vulnerabilities to identify their root causes (rv-3)
- rv
- secure-development
- practice
tech_stack:
- any
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# Analyze Vulnerabilities to Identify Their Root Causes (RV.3) Analyze Vulnerabilities to Identify Their Root Causes
## High-Level Description
**Practice Group:** Respond to Vulnerabilities (RV)
**Framework:** NIST SP 800-218 SSDF v1.1
Help reduce the frequency of vulnerabilities in the future.
## What to Check
- [ ] Verify Analyze Vulnerabilities to Identify Their Root Causes (RV.3) Analyze Vulnerabilities to Identify Their Root Causes is integrated into SDLC
- [ ] Review CI/CD pipeline for Analyze Vulnerabilities to Identify Their Root Causes (RV.3) implementation
- [ ] Confirm automated tooling supports this practice
## How to Test
### Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of Analyze Vulnerabilities to Identify Their Root Causes (RV.3) 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 Analyze Vulnerabilities to Identify Their Root Causes (RV.3) Analyze Vulnerabilities to Identify Their Root Causes 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 Analyze Vulnerabilities to Identify Their Root Causes (RV.3) Analyze Vulnerabilities to Identify Their Root Causes in the software development lifecycle:
Help reduce the frequency of vulnerabilities in the future.
## Risk Assessment
| Finding | Severity | Impact |
| ---------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------- |
| Analyze Vulnerabilities to Identify Their Root Causes (RV.3) Analyze Vulnerabilities to Identify Their Root Causes not implemented | Medium | Secure Development - Respond to Vulnerabilities |
## CWE Categories
| CWE ID | Title |
| ------ | --------------------- |
| N/A | No direct CWE mapping |
## 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!