Dashboard

Overview

The Dashboard is the first page you see after logging in. It provides an at-a-glance view of your application security posture, summarizing key metrics from all connected security tools in one place. Use the Dashboard to quickly assess the current state of your security findings, identify trends, and take immediate action where needed.

Summary Cards

At the top of the Dashboard you will find six metric cards that give you a real-time snapshot of your security landscape:

Total Findings — The total number of security findings currently ingested across all connected tools. This is your overall volume indicator and helps you understand the breadth of issues that need attention.
Critical Severity — The count of findings rated as critical. These represent the most severe vulnerabilities that could lead to significant impact if exploited. Critical findings should be prioritized for immediate remediation.
High Severity — The count of findings rated as high. These are serious vulnerabilities that should be addressed promptly, typically within your defined SLA window.
Medium Severity — The count of findings rated as medium. These represent moderate risk and should be scheduled for remediation as part of regular development cycles.
Low Severity — The count of findings rated as low. These are minor issues or informational findings that carry lower risk but should still be tracked and addressed over time.
Total Jira Issues — The total number of Jira tickets that have been created from security findings, either automatically during sync or manually by an analyst. This metric helps you gauge how many findings have been formally escalated into your issue tracking workflow.

Recent Findings

Below the summary cards, a table displays the 10 most recent findings ingested into the platform. The table includes the following columns:

Title — The name or summary of the vulnerability.
Source Tool — The security tool that detected the finding (Snyk, Cycode, Wiz, or Tenable).
Severity — A color-coded badge indicating the severity level (critical, high, medium, or low).
Status — The current triage status of the finding (e.g., open, in_progress, resolved).
Asset / Repository — The repository or asset where the vulnerability was detected.
Last Seen — The timestamp of when the finding was last observed during a sync.

You can click on any row or use the link at the bottom of the table to navigate to the full Findings page, where you can browse, filter, and triage all findings.

Quick Actions

The Dashboard provides two quick-action buttons for common tasks:

Trigger Sync — Starts a manual ingestion from all configured security tools. This is useful when you have just added a new tool integration or want to pull in the latest findings without waiting for the next scheduled sync. This action requires the analyst or admin role.
View All Findings — Navigates directly to the full Findings page where you can search, filter, and drill into individual findings. Use this when you want to move beyond the summary view and work with the complete dataset.

Interpreting Your Dashboard

Here are some tips for getting the most out of your Dashboard:

Rising critical/high counts — If your critical or high severity counts are growing over time, prioritize remediation efforts. Focus on findings with the highest EPSS exploitability scores first, as these represent the most likely attack vectors.
Low Jira issue count relative to findings — If the total Jira issues count is significantly lower than your total findings, check your severity filter configuration. Your auto-escalation threshold may be set too high, causing findings that should be tracked in Jira to be missed. See the Configuration guide for details on adjusting the severity filter.
Stale last-seen timestamps — If the most recent findings in the table have old timestamps, your sync schedule may not be running as expected. Check the sync status and logs to ensure ingestion is functioning properly.

For more details on working with individual findings, see the Findings guide.