# KEV Watch

The Resolve Platform's known-exploited vulnerability workbench: the CISA, ENISA, Vulnesis and VulnCheck catalogues, your exposure to them, and how they compare.

**Threat Intel › KEV Watch** (`/resolve/kev`) answers two questions: which vulnerabilities are known to be exploited, and which of them your scanners have already found. Use it to pick the findings that need action before their due dates.

## The four catalogues

KEV Watch combines four known-exploited lists: **CISA**, **ENISA**, **Vulnesis** and **VulnCheck**. The bar at the top shows how many CVEs are tracked and how the catalogues split them. Each CVE is counted once, under the first list that carries it, in that order. Press a source to filter the catalogue to every CVE it lists, which can be more than its bar where lists overlap. Press it again to clear it.

A Vulnesis record whose CVE an authority catalogue already lists is withheld, so the Vulnesis list and CISA never overlap in what you see.

## Views

| View | Shows |
|---|---|
| **Your exposure** | Known-exploited CVEs that your scanners have already reported |
| **Catalog** | Every known-exploited CVE, 25 to a page |
| **Trends and sources** | Additions over 12, 26 or 52 weeks, recent additions, how many days each catalogue lags CISA on the CVEs they share, and the shared and unique split per catalogue |

### Catalog filters

- **Search CVE, vendor, product**.
- Source: one of the four catalogues, or all.
- **Ransomware use**: only CVEs with known ransomware campaign use.

Shortcuts jump to the next row **with ransomware use**, the next **due within 14 days**, or the next **past its due date**.

## Rows and the inspector

Each row leads with its state: **Ransomware use**, **Past due** (when you have findings on it), **Due** with the date in words, or **Listed**. Selecting a row opens the inspector beside the queue. It starts with the date added, the due date, vendor, product, ransomware use and your finding count, then:

| Section | Content |
|---|---|
| **What it is** | The catalogue's description of the vulnerability |
| **Required action** | The action the catalogue requires |
| **Notes** | The catalogue's notes |
| **Listed by** | Which catalogues list the CVE |
| **Why Vulnesis lists it** | The Vulnesis reasoning, when the Vulnesis KEV lists it |
| **Exploit prediction (EPSS)** | The EPSS score, fetched when the row opens |

**Open full detail** opens the CVE on its own page (`/resolve/kev-detail?cveId=`), with each catalogue's own record side by side. **Look up CVE** opens it in Search Console.

The search, filters, page and open CVE are kept in the address bar, so a copied link opens a colleague on the same CVE.

## Plan

The catalogue, trends and the detail page are open to everyone, signed in or not. **Your exposure** needs **Pro** or above, because it reads your organisation's findings. Below Pro it shows sample data behind an upgrade prompt.

## Related

- [SSVC decisions](/vulnerability-management/prioritisation/ssvc.md) and [risk strategies](/vulnerability-management/prioritisation/risk-strategies.md) use known-exploited status when they rank findings.
- [Remediation policy](/vulnerability-management/prioritisation/remediation-policy.md) sets your own deadlines.
