By default, Tenable Web App Scanning uses CVSSv2 scores to calculate severity for individual vulnerability instances. If you want Tenable Web App Scanning to calculate the severity of vulnerabilities using CVSSv3 scores (when available), you can configure your severity metric setting.
Tip: A vulnerability instance is a single instance of a vulnerability appearing on an asset, identified uniquely by plugin ID, port, and protocol.
For information about severity and the ranges for CVSSv2 and CVSSv3, see CVSS Scores vs. VPR.
Note: This setting does not affect the following:
- Tenable Web App Scanning vulnerabilities.
- Tenable Container Security vulnerabilities.
- The calculations displayed in the SLA Progress: Vulnerability Age widget. To modify your SLA severity, navigate to the Service-Level Agreement (SLA) tab on the General page.
Caution: When changing your CVSS severity metric setting, the new setting is only reflected in new findings that come into your system. Any existing findings only reflect the previous severity setting (unless otherwise recasted). For more information on recast rules, see Recast/Accept Rules.
To configure your severity setting:
-
On the Severity tab, select the metric that you want Tenable Web App Scanning to use for severity calculations.
-
CVSSv2 — Use CVSSv2 scores for all severity calculations.
-
CVSSv3 — Use CVSSv3 scores, when available, for all severity calculations. Use CVSSv2 only if a CVSSv3 score is not available.
- Click Save.
-
The system saves your change and begins calculating severity based on your selection.
All vulnerabilities seen before the change retain their severity. After the change, all vulnerabilities seen during scans receive severities based on your new selection. Because of this, you could see two sightings of the same vulnerability have two different CVSS scores and severities.
Tip: A vulnerability instance is a single instance of a vulnerability appearing on an asset, identified uniquely by plugin ID, port, and protocol.