DocumentaciónHelp

Review findings

Filter the vulnerabilities found, understand their risk and what to do, and decide whether to create an exception or send them to a security case.

On this page

A finding is a vulnerability or exposure on a specific asset. The list is sorted by Risk, a score that combines severity (CVSS), the likelihood of exploitation (EPSS), whether it is in the KEV catalog and where it is visible from.

Before you start

  • View permission on Vulnerabilities to review; Operate to create exceptions or send to a case.

Filter

  1. Go to Security (SIEM) → Vulnerabilities → Findings.

  2. Choose the status (Open, With exception, Resolved or All), the minimum severity, the vantage point (Perimeter (external), Private connection (tunnel) or Local) and the confidence.

  3. Check KEV only to see only the actively exploited ones.

Confidence

Meaning

Confirmed

Verified with a direct test against the service

Authenticated

Seen by signing in to the host with credentials (gray or white box): packages, patches or firmware

Probable

Inferred only from the version the service advertises; it's best to confirm it

Some Linux distributions fix a vulnerability without changing the version they show externally. That's why a Probable finding may not apply. A gray or white box scope on that host clears it up: authenticated data takes precedence over probable data for the same CVE.

Read a finding

Click a row to open its detail:

  • Risk, the CVEs, CVSS · EPSS and the Status.

  • Asset, Vantage point, Confidence and, if available, the Quality of detection.

  • Package and installed version, and Where it was seen (port or URL).

  • First · last, and whether it was Reopened or Resolved.

  • Notification: whether it generated a notification for KEV (critical), Critical vulnerability or New exposure on the perimeter.

  • What to do: the recommended solution.

  • References and the Asset exposure by vantage point.

Decide what to do

  • Fix it: apply the solution on the host. On the next scan, if it's no longer seen, the finding changes to Resolved by itself.

  • Create exception: if it's a risk the company accepts for a time, or a false positive. See Create and review vulnerability exceptions.

  • Send to a case: if you have the SIEM, open a security case with the finding to work it with your team.

Titles, references and addresses come from the scanned target and third-party sources: they are shown as data.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close