Skip to main content

Vulnerability Management (Triage)

This is where you actually review and handle the vulnerabilities (findings) that were found. You cannot fix everything at once, so the key is to prioritize by severity, source, and KEV and deal with the highest-risk items first.

Finding list​

  • Displayed as a flat list ordered by severity.
  • Use the KEV chip to separately filter items under active exploitation.
  • Filterable by scanner type (code analysis / dependencies / web check, etc.).

Vulnerability management inbox

Two ways to handle​

Triage is simplified into two closing actions, so you can clean things up quickly without a complex workflow.

  • False Positive : not a real risk. Permanently suppressed by fingerprint so it does not reappear in the next scan.
  • Accepted Risk : the risk is acknowledged but you decide not to act on it now.

Items you do not handle remain in the Open state. If an unresolved item is found again on rescan, it is marked as Regression .

Detail drawer​

Click an item and the detail opens on the right.

  • Location (file / path), code snippet (code analysis), CVE / CWE references
  • Type-specific details
  • Activity log (who handled it, when, and how)

Finding detail drawer

Tracking by source​

Even the same vulnerability is tracked separately by source (source code / image / host, etc.). Because an item remaining in another source is managed separately even after you fix it in one place, you do not lose track of which path the risk came in through.

Next steps​

ComplianceHandling results reflected against standardsSecurity ScoreImpact of action on postureReports & VEXExport triage resultsDashboardIdentify the next risk to look at