Vulnerabilities
The Vulnerabilities view (Inventory → Vulnerabilities, /vulnerabilities)
is the environment-wide roll-up of known CVEs and the scans that produced them.
The Vulnerabilities screen
Four stat cards summarize the picture: Total Vulnerabilities, Critical, High, and Scans run. Below them are two tables:
- Recent Vulnerability Scans — one row per scan (application, version, date,
total vulnerabilities, Critical/High counts, and status). Clicking a row opens
the scan detail at
/vulnerabilities/scans/<id>. - All Vulnerabilities — every discovered CVE with its application, severity,
CVSS score, an Exploited flag, and description. A search box filters by CVE
id, and each row links to the CVE detail at
/vulnerabilities/cve/<cve>.
Where findings come from
Vulnerability data flows in from three places, and each surfaces both here and on the relevant asset detail tabs:
| Source | What it contributes | Where it shows |
|---|---|---|
| Rapid7 InsightVM | Per-asset findings and the asset’s risk score / Critical-Severe counts. | Asset detail → Findings and Rapid7 tabs. |
| SentinelOne | Agent-reported threats and application vulnerability status. | Asset detail → SentinelOne tab (KPIs count active threats). |
| Per-application CVE scans | On-demand scans of an app + version against CVE data (optionally enriched). | Asset detail → Vulnerabilities tab, and the application detail. |
Running scans
CVE scans are launched on demand:
- From the application detail — select one or more
versions and click Scan (
POST /vulnerabilities/scan). - From an asset detail — the Run scan button scans the
machine’s installed applications (
POST /vulnerabilities/scan-device); results land on that asset’s Vulnerabilities tab.
Researching a finding
On an asset’s Findings tab, each Rapid7 CVE offers a Research action that enriches the finding with additional CVE intelligence, marking it researched when complete.
Related
- Assets · Software inventory
- Integrations: Rapid7 · SentinelOne