prioritizing-vulnerabilities-with-cvss-scoring
The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (r
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- prioritizing-vulnerabilities-with-cvss-scoring
- tags
- [ "vulnerability-management", "cve", "cvss", "risk", "prioritization", "nist" ]
- author
- mahipal
- domain
- cybersecurity
- license
- Apache-2.0
- version
- 1.0
- nist_csf
- [ "ID.RA-01", "ID.RA-02", "ID.IM-02", "ID.RA-06" ]
- subdomain
- vulnerability-management
- description
- The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (r
- mitre_attack
- [ "T1190", "T1203", "T1068" ]
02 资源文件 7
- 资产文件assets/template.md1.4 KB
- 许可证LICENSE11.0 KB
- 参考文档references/api-reference.md1.9 KB
- 参考文档references/standards.md1.7 KB
- 参考文档references/workflows.md2.8 KB
- 脚本scripts/agent.py5.9 KB
- 脚本scripts/process.py15.0 KB
03 SKILL.md 正文
Prioritizing Vulnerabilities with CVSS Scoring
Overview
The Common Vulnerability Scoring System (CVSS) is the industry standard framework maintained by FIRST (Forum of Incident Response and Security Teams) for assessing vulnerability severity. CVSS v4.0 (released November 2023) introduces refined metrics for more accurate scoring. This skill covers calculating CVSS scores, interpreting vector strings, and using CVSS alongside contextual factors like EPSS and CISA KEV for effective vulnerability prioritization.
When to Use
- When managing security operations that require prioritizing vulnerabilities with cvss scoring
- When improving security program maturity and operational processes
- When establishing standardized procedures for security team workflows
- When integrating threat intelligence or vulnerability data into operations
Prerequisites
- Understanding of common vulnerability types (buffer overflow, injection, XSS, etc.)
- Familiarity with networking concepts (attack vectors, protocols)
- Access to NVD (National Vulnerability Database) for CVE lookups
- Vulnerability scan results requiring prioritization
Core Concepts
CVSS v4.0 Metric Groups
1. Base Metrics (Intrinsic Severity)
Represent the inherent characteristics of a vulnerability:
Exploitability Metrics:
- Attack Vector (AV): Network (N), Adjacent (A), Local (L), Physical (P)
- Attack Complexity (AC): Low (L), High (H)
- Attack Requirements (AT): None (N), Present (P) - NEW in v4.0
- Privileges Required (PR): None (N), Low (L), High (H)
- User Interaction (UI): None (N), Passive (P), Active (A) - Expanded in v4.0
Impact Metrics (Vulnerable System):
- Confidentiality (VC): None (N), Low (L), High (H)
- Integrity (VI): None (N), Low (L), High (H)
- Availability (VA): None (N), Low (L), High (H)
Impact Metrics (Subsequent System):
- Confidentiality (SC): None (N), Low (L), High (H)
- Integrity (SI): None (N), Low (L), High (H)
- Availability (SA): None (N), Low (L), High (H)
2. Threat Metrics (Dynamic Context)
- Exploit Maturity (E): Attacked (A), POC (P), Unreported (U)
3. Environmental Metrics (Organization-Specific)
Modified versions of base metrics reflecting local deployment context, plus:
- Confidentiality Requirement (CR): High (H), Medium (M), Low (L)
- Integrity Requirement (IR): High (H), Medium (M), Low (L)
- Availability Requirement (AR): High (H), Medium (M), Low (L)
4. Supplemental Metrics (Advisory Information)
- Safety (S): Present (P), Negligible (X)
- Automatable (AU): Yes (Y), No (N)
- Recovery (R): Automatic (A), User (U), Irrecoverable (I)
- Value Density (V): Diffuse (D), Concentrated (C)
- Vulnerability Response Effort (RE): Low (L), Moderate (M), High (H)
- Provider Urgency (U): Red, Amber, Green, Clear
CVSS v4.0 Severity Ratings
| Score Range | Severity |
|---|---|
| 0.0 | None |
| 0.1 - 3.9 | Low |
| 4.0 - 6.9 | Medium |
| 7.0 - 8.9 | High |
| 9.0 - 10.0 | Critical |
CVSS v4.0 Vector String Format
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
This example represents a network-exploitable vulnerability requiring no privileges, no user interaction, no attack requirements, with high impact on confidentiality, integrity, and availability of the vulnerable system.
Workflow
Step 1: Assess Base Metrics
For each vulnerability, evaluate:
Example: CVE-2024-3094 (XZ Utils Backdoor)
Attack Vector: Network (N) - Exploitable over network
Attack Complexity: High (H) - Specific conditions required
Attack Requirements: Present (P) - Specific build/config needed
Privileges Required: None (N) - No authentication needed
User Interaction: None (N) - No victim action needed
Vulnerable System Impact:
Confidentiality: High (H) - Complete access to SSH keys
Integrity: High (H) - Arbitrary code execution
Availability: High (H) - Full system compromise
Subsequent System Impact:
Confidentiality: High (H) - Lateral movement possible
Integrity: High (H) - Network-wide compromise
Availability: None (N) - No downstream availability impact
Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N
Step 2: Apply Threat Intelligence Context
Enrich CVSS with real-world threat data:
Exploit Maturity: Attacked (A) - Active exploitation in the wild
EPSS Score: 0.94 - 94% probability of exploitation in 30 days
CISA KEV: Listed - Mandatory remediation for federal agencies
Step 3: Calculate Environmental Score
Adjust for organizational context:
Confidentiality Req: High (H) - Handles PII/financial data
Integrity Req: High (H) - Critical business process
Availability Req: Medium (M) - Has DR/failover capability
Modified Attack Vector: Network (N) - Internet-facing deployment
Step 4: Multi-Factor Prioritization Matrix
Combine CVSS with additional prioritization factors:
| Factor | Weight | Source |
|---|---|---|
| CVSS Base Score | 25% | NVD/Scanner |
| EPSS Score | 25% | FIRST EPSS API |
| Asset Criticality | 20% | Asset inventory/CMDB |
| CISA KEV Listed | 15% | CISA catalog |
| Network Exposure | 15% | Network segmentation data |
Step 5: Define Remediation SLAs
| Priority Level | CVSS Range | EPSS | Asset Tier | SLA |
|---|---|---|---|---|
| P1 - Emergency | 9.0-10.0 | >0.5 | Tier 1 | 24-48 hours |
| P2 - Critical | 7.0-8.9 | >0.3 | Tier 1-2 | 7 days |
| P3 - High | 7.0-8.9 | <0.3 | Tier 2-3 | 14 days |
| P4 - Medium | 4.0-6.9 | Any | Any | 30 days |
| P5 - Low | 0.1-3.9 | Any | Any | 90 days |
Best Practices
- Never rely solely on CVSS base score for prioritization
- Always incorporate threat intelligence (EPSS, KEV, exploit databases)
- Maintain accurate asset criticality ratings in your CMDB
- Adjust environmental metrics for your specific deployment context
- Use CVSS v4.0 vector strings for precise communication between teams
- Document scoring rationale for audit trail and consistency
- Re-evaluate scores when new threat intelligence becomes available
- Train remediation teams on interpreting CVSS metrics and vector strings
Common Pitfalls
- Treating CVSS base score as the sole prioritization factor
- Ignoring environmental metrics that reflect organizational risk
- Not updating threat metrics when exploit maturity changes
- Confusing CVSS severity with actual organizational risk
- Using outdated CVSS v2.0 scores instead of v3.1/v4.0
- Over-relying on scanner-provided scores without validation
Related Skills
- prioritizing-patches-with-exploit-prediction-scoring
- implementing-risk-based-vulnerability-management
- implementing-vulnerability-remediation-sla
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.
grants
NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.