Skip to main content
Version: 0.10

Vulnerabilities

The Vulnerabilities module shows what your vulnerability scanners found on the tenant's assets, open and fixed, read against the asset register: who owns each asset, its department, location and criticality. It tracks findings against a remediation SLA and rolls everything up into a security score from 0 to 100.

Open it from the sidebar: Modules → Vulnerabilities.

In this module a finding is one vulnerability on one asset, as the scanner reports it. It is not the same as the raw scan records that integrations upload during a scan.

Prerequisites​

The module reads the findings a vulnerability scanner integration stores, and the endpoints that scanner reports on. Today that is Tenable Security Center.

  • An endpoint is part of the module when the scanner has marked it as one it scans, whether or not it has findings.
  • Informational findings (no severity) are left out.
  • A finding whose host is not yet an asset of the tenant is counted separately, as not linked; the next sync of that integration links it.

Until a scanner integration has run and synced its hosts, the screen shows No vulnerability data yet.

The screen​

The page header shows when the data was last collected, how many assets the exclusion query leaves out, and how many findings are not linked to an asset yet. The Scope bar (Department, Location, Owner, Kind, Criticality) narrows every tab.

TabContents
OverviewTiles for the Security score, Open findings, Critical, Exploitable, Past SLA, Fixed, 30 days, Mean time to fix and Reopened. Charts for open findings by severity, open findings over time, how long open findings have been open, first seen and fixed, the remediation SLA, the security score by department, the lowest-scoring assets, and a Fix these first list.
Security scoreThe score for all assets in scope with its four parts and its weekly trend, the score grouped by Department, Owner, Location or Product, a drill-down into each group, and How the score works.
FindingsEvery finding with its vulnerability, asset, severity, CVSS 3, EPSS, exploit, port, state, first seen, fixed, SLA and how long it has been open. Filter by Severity, State, SLA, Exploit and Fixed. Click a finding for its full detail (summary, description, solution, evidence, references).
AssetsEvery asset with its score and grade, criticality, department, location, owner, OS, IP, open findings by severity, past-SLA count, oldest open finding, last credentialed scan and end-of-life flag.
VulnerabilitiesOne row per vulnerability (scanner check) with its CVEs, CVSS 3, exploit, the assets affected, open, past SLA and fixed counts. Opening one shows exactly its own findings.

Finding states​

A finding that comes back after being fixed or removed is reopened.

StateMeaning
OpenReported and not fixed.
ReopenedFixed once, then reported again. Counts as open.
FixedThe scanner reports it as patched.
RemovedThe scanner no longer reports it at all, neither open nor fixed. Only decided after a complete read of the scanner's data.

A finding the scanner marks as an accepted risk is never past its SLA and does not count towards exposure.

End of life​

An asset is flagged as end of life when its operating system is past its vendor's end of support, or when the scanner reports unsupported software on it (a finding titled "Unsupported ..." or mentioning SEoL). Operating systems counted as end of life: Windows XP, Vista, 7, 8, 8.1 and 10 (not the LTSC and LTSB editions), and Windows Server 2000, 2003, 2008 and 2012.

Settings​

Settings opens Vulnerabilities settings. A tenant that never saved settings uses the defaults.

Assets to leave out​

Exclusion query (optional): an asset search query, up to 2,000 characters. Matching endpoints, and their findings, are left out of every dashboard, list and score, for example fields.department: "Lab". The query is run once when you save; a query the asset search rejects is refused.

SLA: days to fix​

Each finding is due a number of days after it was first seen. The number depends on the finding's severity and the asset's criticality; an asset with no criticality is treated as Medium. Each value is 1 to 3,650 days.

Severity \ Asset criticalityCriticalHighMediumLow
Critical7141530
High14303060
Medium30609090
Low90120180180

A finding is past SLA when it is open, not an accepted risk, and its due date has passed.

Security score​

Choose one of four formulas:

FormulaWhat it scores
Balanced (default)The four parts below with the default weights, and assets without a recent credentialed scan capped at 69.
SLA complianceThe severity-weighted share of findings handled within their SLA. No parts, no cap.
Risk exposureThe exposure part alone: open findings by severity, counted double when an exploit is public. No cap.
Custom weightsThe four parts with your own weights (each 0 to 100%, adding up to 100%) and your own cap (0 to 100), or no cap (Cap assets without a credentialed scan in 30 days unticked). Defaults: 35 / 30 / 15 / 20 and 69.

Stored findings​

Clear vulnerability data permanently deletes every finding the module holds for the tenant, open and fixed, with its history. You must type DELETE to confirm. Assets are not touched. The scanners' next runs bring back what they still report; fixed findings older than a scanner keeps are gone for good, and the security score's trend starts again.

The security score​

The score runs from 0 to 100, higher is better, and carries a grade:

GradeScore
A90 and above
B80 to 89
C70 to 79
D60 to 69
FBelow 60

It is worked out per asset, then rolled up to any group (a department, an owner, a location, a product, all assets in scope) as an average weighted by asset criticality.

Severity weights​

Every part counts findings by severity:

SeverityWeight
Critical10
High5
Medium2
Low0.5

The four parts​

Each part is a number from 0 to 100. Two of them fall off smoothly with a penalty P: the part is 100 × e^(−P / scale), which is about 37 when P equals the scale and never quite reaches 0.

PartDefault weightHow it is worked out
SLA discipline35%P is the sum, over open findings past their SLA, of severity weight × lateness factor. The lateness factor is 1 + days late ÷ SLA days, capped at 3. Scale 12.
Exposure30%P is the sum, over open findings that are not accepted risks, of severity weight, doubled when an exploit is available. Scale 25.
Remediation pace15%Over the last 90 days: half speed, the average over findings fixed in that time of SLA days ÷ days to fix (capped at 1, with at least one day to fix), and half burn-down, findings fixed ÷ new findings (capped at 1). Either half is 1 when there is nothing to judge. The part is 100 × (0.5 × speed + 0.5 × burn-down).
Hygiene20%100, minus 40 without a credentialed scan in the last 30 days, minus 40 for end-of-life software, minus 10 without an owner, minus 10 without a criticality. Never below 0.

The asset's score is the weighted sum of the parts, rounded to a whole number:

score = 0.35 × SLA discipline + 0.30 × exposure + 0.15 × remediation pace + 0.20 × hygiene

The cap for unscanned assets​

Under Balanced (and Custom weights with a cap), an asset without a credentialed scan in the last 30 days cannot score above the cap, 69 by default: a D at best. Its findings are not known, not absent. The asset's score card says when a score is capped ("Capped at 69: no credentialed scan in 30 days").

SLA compliance​

Under SLA compliance the score is the share, weighted by severity, of the findings that are open now or were fixed in the last 90 days (accepted risks left out) that are within their SLA: open and not yet due, or fixed within their SLA days. An asset with nothing to judge scores 100.

Rolling up to a group​

A group's score, and each of its parts, is the average of its assets' values weighted by criticality:

Asset criticalityWeight
Critical4
High3
Medium (or not set)2
Low1

An asset that runs several products counts in each product's group. Assets with no value for the grouping field are grouped under Not set.

How the score is computed today

The score is calculated in the browser from the findings and assets the module loads, so it always reflects the current settings. The weekly trend is recalculated from each finding's history as it stood each week over the last 12 weeks; past scan dates are not stored, so each week uses the latest credentialed scan date.

Limits​

LimitValue
Findings loaded per viewThe 100,000 most recently seen; the screen says when older ones are left out
Exclusion query length2,000 characters
SLA values1 to 3,650 days

Permissions​

TaskPermission
View the module and its settingsAsset Management read
Save settings, clear vulnerability dataAsset Management write

The module must also be switched on for the tenant; see Modules.