Compute CISA SSVC (Stakeholder-Specific Vulnerability Categorization) for a CVE.
## What this tool does
Calculates the SSVC decision (Track, Track*, Attend, Act) using:
- exploitation status
- technical impact
- automatable exploitation
- mission prevalence (user-provided)
- public well-being impact (user-provided)
This reflects CISA's official SSVC prioritization model.
## When to use this tool
Use this tool when the user asks about:
- how urgently a CVE should be remediated
- CISA SSVC priority or risk category
- a structured decision model for remediation
## Inputs
- **cve_id**: the vulnerability to evaluate (`CVE-YYYY-NNNNN`)
- **mission_prevalence**: `M`, `S`, or `E` (must be provided by the user)
- **public_well_being_impact**: `M`, `A`, or `I` (must be provided by the user)
## Outputs
- `decision`: one of **Track**, **Track\***, **Attend**, **Act**
- `exploitation`
- `technical_impact`
- `automatable`
- `mission_prevalence`
- `public_well_being_impact`
- `mission_and_well_being_impact_value`
- `vector_string`
- `summary`: Markdown explanation of the outcome
## LLM usage guidelines
- Always ask the user for **mission_prevalence** (M/S/E) and **public_well_being_impact** (M/A/I) before calling.
- Never guess these values—SSVC depends on user context.
- Use the `summary` to explain clearly why the decision was returned.
- Combine with `vulnerability_score` or `sightings_search` if the user needs additional context.
Connector