05.06 Working the Vulnerabilities List
The Vulnerabilities page lists each vulnerability once, with the assets it affects behind it, its EPSS score and CISA KEV status, and where it came from. Here's how to read it, filter it by source and triage status, expand a row to its assets, and triage, attach or hide vulnerabilities one at a time or in bulk.
Why this matters
A scanner reports findings per asset. The same missing patch on forty servers is forty rows in the export, and nobody can prioritize forty rows that all say the same thing. The Vulnerabilities page turns that around: one row per vulnerability, the asset count beside it, and the forty servers one click away. That's the shape a triage conversation actually needs. The question in the meeting is "do we treat this one as a risk," not "what about server 31."
The list is also the one place every vulnerability lands, however it arrived. Findings from a scanner export you imported and findings synced by the Vulnerability Management Extra appear side by side, with a Source column saying which is which, and you triage them the same way. There's no separate queue for scanner findings.
Two numbers on the page are worth more attention than CVSS for deciding what to look at first. EPSS (the Exploit Prediction Scoring System, published by FIRST.org) estimates how likely a CVE is to be exploited in the wild over the next 30 days. KEV marks CVEs on the CISA Known Exploited Vulnerabilities catalog, meaning someone has already exploited them. We'd start every triage session with Known exploited only ticked. A CVSS 9.8 nobody has ever exploited can usually wait a day; a CVSS 6.5 that's on the KEV list usually shouldn't.
Before you start
What you can do on the page depends on what you hold. (See Permission Reference.)
- See the page and its list: Allow Access to Vulnerability Management "Vulnerabilities" Menu
- Turn a vulnerability into a new risk: Able to Approve Vulnerability Triage to Risk, plus Able to Submit New Risks and Able to Modify Risk Details
- Attach a vulnerability to an existing risk: All of the above, plus Allow Access to "Risk Management" Menu (the risk picker needs it)
- Hide a vulnerability, or return a hidden one to triage: Able to Reject Vulnerability Triage to Risk
- Import a scanner export: Able to Import Vulnerabilities
- See which SimpleRisk asset each affected asset is: Allow Access to "Asset Management" Menu
None of this needs the Vulnerability Management Extra. Without it, the list holds what you've imported. With it, it also holds what the Extra's scanner integrations sync.
Step-by-step
-
Open the page. Sidebar: Vulnerabilities → Vulnerabilities. When the Vulnerability Management Extra is active, the page has two tabs: Vulnerabilities (this list) and View Risks, which lists the Extra's scanner findings that already have a risk. Imported vulnerabilities that have been triaged don't move there; find them on the list with Triage status set to Triaged. Without the Extra there are no tabs, just the list. An empty list says No vulnerabilities yet and, if you can import, offers Import Vulnerabilities.
-
Read the columns. Each row shows the Vulnerability title, its Severity, CVSS score, EPSS score as a percentage, KEV status, how many Assets it affects, its Source, and its Risk. A KEV value of Yes means the CVE is known to be exploited; hover over it for CISA's due date. The Risk column links to the risk the vulnerability was triaged into. If it was triaged into a risk you aren't allowed to see, the column says Triaged and links nothing.
EPSS and KEV come from two places. Your import file may carry them (Tenable.io exports do), and SimpleRisk also looks them up once a day for the CVEs of imported vulnerabilities. A vulnerability is shown as known exploited when either the file or the CISA catalog says so, and a looked-up EPSS score replaces the one from the file. Rows synced by the Extra's scanner integrations show a dash in both columns, because those findings don't carry CVE IDs to look up. Your administrator can turn the lookups off, and then only the values from your files are shown.
- Narrow the list. Above the list, a chip for each source shows how many vulnerabilities that source has. Sources with none don't get a chip. Select a chip to show only that source; the Source dropdown does the same thing alongside the other filters. Then: - Triage status starts on Untriaged, the vulnerabilities still waiting for a decision. Switch to Triaged, Hidden or All to see the rest. - Known exploited only keeps the KEV-listed vulnerabilities. - The search box (Search by title, ID or platform) searches the whole list, not just the page in front of you.
A chip's count is every vulnerability from that source, whatever the other filters say, so it won't match the filtered total. On a narrow screen the filters fold behind the Filters button. Select a column heading to sort by Severity, CVSS or Assets; the list opens sorted by CVSS, highest first.
-
Expand a row to see its assets. Select the arrow at the start of a row. The row opens to list the CVEs the vulnerability carries and each affected asset, with its Name, IP Address, FQDN, Operating system and NetBIOS name as the scanner reported them. If Team Separation hides some of the assets from you, you see only the ones you're allowed to see.
-
Triage one vulnerability into a new risk. Use the row's Create risk action. (On a narrower screen, the row's actions sit behind its actions menu.) A notice confirms the risk ID, and the row leaves the Untriaged view with the risk now in its Risk column. If a risk you can modify already has exactly the vulnerability's title as its subject, the vulnerability is attached to that risk instead of creating a second one. What the new risk contains, and how it's scored, is in From Vulnerability to Risk.
-
Or attach it to a risk you already have. Use the row's Attach to existing risk action. In the dialog, type at least 2 characters of a risk ID or subject, pick the risk, and select Attach. The picker offers open risks you're allowed to modify. As the dialog says, the vulnerability's assets and tags are added to the risk, and the risk's score and text don't change.
-
Triage several at once. Tick the checkboxes of the rows you want, or tick the header checkbox for the whole page. A bar replaces the toolbar showing how many are selected, with Create risks and Attach to existing risk. You can triage up to 50 at a time. When the run finishes, Triage results lists each vulnerability and what happened to it: Triaged with a link to its risk, or the reason it wasn't. A partial success is normal and worth reading; the usual reasons are a vulnerability someone else triaged a moment earlier, or one linked to an asset you can't see.
-
Hide what doesn't need a decision. Use the row's Hide action for a vulnerability you've decided not to track as a risk, such as an informational finding or one the patch cycle will take care of. Hidden vulnerabilities leave the Untriaged view but aren't deleted. To bring one back, set Triage status to Hidden and use the row's Unhide action. Hide works one row at a time; there's no bulk hide. A vulnerability that's already been triaged into a risk can't be hidden.
Common pitfalls
- Treating an empty Untriaged view as a clean environment. It means every vulnerability in SimpleRisk has had a decision. It says nothing about what the scanner found since the last import, and an imported vulnerability never leaves the list because a newer file didn't mention it. The scanner is still the source of truth for what's open right now.
- Expecting the same CVE from two scanners to be one row. Each source keeps its own vulnerabilities, matched by that scanner's own finding ID, not by CVE. Tenable.io and Qualys reporting the same CVE are two rows, and an imported Tenable.io file plus the Extra's Tenable.io sync are two rows as well. Triage one and attach the other to the same risk.
- Expecting attach to rescore the risk. It never does. Neither does triaging a vulnerability into a risk that already has its title. If the vulnerability you just attached is worse than the risk's current score suggests, rescore the risk yourself.
- Removing assets by triage. Triage only ever adds assets to a risk. When a server is patched or retired, remove it from the risk on the risk itself; nothing on this page will.
- Hiding to clear the queue. Hidden is a decision, not a snooze. If you mean "not yet," leave the vulnerability in Untriaged.
- Paging deep into all sources at once. On a very large list, paging far into every source together stops with "This page is too far into the list of all sources." Pick a source or add a filter and the paging works at any depth.
- A row you can't triage. Under Team Separation, triage and hide are refused for a vulnerability linked to any asset you can't see, because triage would link that asset to the risk. Someone whose teams cover all of its assets has to make the call.