Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill RV.2.1_rv21 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of RV.2.1 Rv21?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-rv-2-1-rv21)More formats (shields.io, HTML) on the badges page.
---
name: "RV.2.1_rv21"
description: "Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response."
category: "configuration"
version: "1.1"
author: "cyberstrike-official"
tags:
- nist
- sp800-218
- ssdf
- rv-2-1
- rv
- secure-development
- task
tech_stack:
- any
cwe_ids: []
chains_with: []
prerequisites:
- Assess, Prioritize, and Remediate Vulnerabilities (RV.2)
severity_boost: {}
---
# RV.2.1 RV.2.1
> **Task of practice:** Assess, Prioritize, and Remediate Vulnerabilities (RV.2)
## High-Level Description
**Practice Group:** Respond to Vulnerabilities (RV)
**Framework:** NIST SP 800-218 SSDF v1.1
Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response.
## What to Check
- [ ] Verify RV.2.1 RV.2.1 is integrated into SDLC
- [ ] Review CI/CD pipeline for RV.2.1 implementation
- [ ] Confirm automated tooling supports this practice
## How to Test
### Step 1: Review SDLC Documentation
Examine development lifecycle documentation for evidence of RV.2.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 RV.2.1 RV.2.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 RV.2.1 RV.2.1 in the software development lifecycle:
Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response.
## Risk Assessment
| Finding | Severity | Impact |
| ----------------------------- | -------- | ----------------------------------------------- |
| RV.2.1 RV.2.1 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!