> 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.md).

# Monitor & Deliver

Track your security posture over time and send results to your team.

This section covers how to track your organization's vulnerability landscape and get Konvu's results to the people who act on them.

* [**Dashboard & Overview**](/konvu/triage-and-remediation/monitor-and-deliver/dashboard-and-overview.md): Key security posture metrics at a glance: assessment progress, exploitability breakdown, backlog trends, and top CVEs to prioritize.
* [**Inventory**](/konvu/triage-and-remediation/monitor-and-deliver/inventory.md): Every repository and manifest Konvu has onboarded, with its detected stack, threat profile tier, and finding counts.
  * [**Threat Profiles**](/konvu/triage-and-remediation/monitor-and-deliver/inventory/threat-profiles.md): What each repository is, where it's exposed, what it holds, and who could reach it. Scored into a tier (Crown Jewel to Peripheral) that drives prioritization.
* [**Notifications**](/konvu/triage-and-remediation/monitor-and-deliver/notifications.md): A weekly email digest and a daily Slack recap of newly exploitable findings.
  * [**Weekly Email Digest**](/konvu/triage-and-remediation/monitor-and-deliver/notifications/weekly-email-digest.md)
  * [**Slack Daily Digest**](/konvu/triage-and-remediation/monitor-and-deliver/notifications/slack-daily-digest.md)
* [**Data Forwarding**](/konvu/triage-and-remediation/monitor-and-deliver/data-forwarding.md): Write Konvu's assessments onto findings in ArmorCode and Wiz, and check every delivery.


---

# 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.md?ask=<question>&goal=<user_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.