> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/dashboard-and-overview.md).
# Dashboard & Overview
Key security posture metrics at a glance: assessment progress, exploitability breakdown, backlog trends, and top CVEs to prioritize.
The Overview page is your starting point in Konvu. It shows how your assessment is progressing, what the results look like, and where to focus next.
## Exploitability breakdown
Once assessments complete, the Sankey diagram shows how your findings break down:
* **Total assessed findings**: The count of findings with a completed assessment.
* **False Positives**: Findings where the vulnerability is not exploitable in your environment. These are safe to [dismiss](/konvu/triage-and-remediation/triage/dismissing-false-positives.md).
* **Exploitable**: Findings where Konvu found evidence the vulnerability can be exploited. These need remediation.
* **Inconclusive**: Findings where the available evidence was not enough to make a definitive call. [Answering Konvu's questions](/konvu/triage-and-remediation/exploitability-assessment/answering-konvus-questions.md) can resolve these.
The diagram also breaks these counts down by severity (Critical, High, Medium, Low), so you can see where exploitable findings concentrate.
{% hint style="info" %}
Use the time period selector (7 days, 30 days, 90 days, or all time) to focus the breakdown on recently discovered findings versus your full historical backlog.
{% endhint %}
## Backlog trends
The overview includes trend charts that track your backlog over time:
* **Open backlog**: Total open findings per week (or day). A declining trend means you're closing findings faster than new ones appear.
* **New vs. Closed**: How many findings were opened versus closed in each period. This tells you whether your backlog is growing or shrinking.
* **To Dismiss**: Open findings that Konvu recommends dismissing as false positives. A large number here means there's low-hanging fruit to clean up.
* **To Fix**: Open findings that Konvu recommends remediating. These are your priority backlog.
Trends are aggregated weekly by default (averaging daily counts within each week) and show up to 10 weeks of history. Switch to daily view for a more granular look at the last 7 days.
## Top CVEs to prioritize
The dashboard surfaces up to three CVEs recommended for remediation, sorted by severity. These are your highest-priority open findings where Konvu's assessment result is "Exploitable", the ones to address first.
Each entry shows the CVE identifier, the affected dependency, and a link to the finding detail page where you can review the [evidence](/konvu/triage-and-remediation/exploitability-assessment/reading-an-assessment.md) and take action.
## Setup checklist
If you're still onboarding, the dashboard shows a setup checklist tracking your integration progress:
* Connect a scanner (Snyk, Semgrep, Dependabot, Endor Labs, or Arnica)
* Connect your source code for stack analysis
Once all steps are complete and assessments finish, the checklist collapses automatically.
## From the CLI
Get the same metrics from your terminal:
```bash
# Summary metrics (total findings, assessment counts, exploitability breakdown)
konvu metrics
# Include backlog trends and top CVEs
konvu metrics --include top_cves,new_vs_closed
# Scope to the last 90 days with monthly intervals
konvu metrics --since 90d --interval month
```
The CLI outputs a table by default. Pipe to `jq` or use `--output json` for scripting:
```bash
# Get exploitable count for a CI dashboard
konvu metrics --output json | jq '.exploitable'
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.konvu.com/konvu/triage-and-remediation/monitor-and-deliver/dashboard-and-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
