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

# Triage Overview

How Konvu triages findings: an exploitability assessment for every finding, and an exploit reproduction when you need proof.

Konvu triages each finding in two ways. **Exploitability Assessment** reads your code to decide whether the vulnerability can be exploited. **Exploit Reproduction** runs the exploit against your application in an isolated sandbox to prove it.

|                         | Exploitability Assessment                                               | Exploit Reproduction                                                                     |
| ----------------------- | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| **Question it answers** | Do the conditions for an exploit hold in your code?                     | Does the exploit fire?                                                                   |
| **How**                 | An agent checks each condition against your repository and environment. | Konvu deploys your application in an isolated sandbox and an agent attacks it.           |
| **Output**              | An assessment result with the evidence for each condition.              | Proof: requests, responses, and observed impact. Or the investigation that ruled it out. |
| **Runs on**             | Every finding in your assessment scope.                                 | Vulnerability reports by default. SAST and SCA findings in early access.                 |
| **Takes**               | Seconds to minutes.                                                     | Several minutes per run.                                                                 |

## Which method applies to which finding

| Finding type                                                                                  | Exploitability Assessment      | Exploit Reproduction      |
| --------------------------------------------------------------------------------------------- | ------------------------------ | ------------------------- |
| [Dependencies (SCA)](/konvu/triage-and-remediation/finding-types/dependencies.md)             | Yes                            | Early access              |
| [Code (SAST)](/konvu/triage-and-remediation/finding-types/code.md)                            | Yes                            | Early access, CodeQL only |
| [Containers](/konvu/triage-and-remediation/finding-types/containers.md)                       | Yes                            | No                        |
| [Secrets](/konvu/triage-and-remediation/finding-types/secrets.md)                             | Validity, impact, and exposure | No                        |
| [Vulnerability Reports](/konvu/triage-and-remediation/finding-types/vulnerability-reports.md) | Triage against program rules   | Yes                       |

## How the two combine

Assessment runs first, on every finding in scope. Reproduction adds proof on top of it:

* **A successful reproduction marks the finding Exploitable**, even when the assessment disagreed.
* **A reproduction that disproves the finding marks it False Positive.** The evidence appears on the **Reproduction** tab under **Not reproducible**.
* **A Hardening or Inconclusive reproduction never downgrades a finding.** A sandbox can miss a real vulnerability, so the assessment result stands.
* **For vulnerability reports**, the reproduction result replaces the triage result.

See [Exploit Reproduction](/konvu/triage-and-remediation/exploit-reproduction.md#how-reproduction-affects-the-result) for the details.

## In this section

* [**Exploitability Assessment**](/konvu/triage-and-remediation/exploitability-assessment.md): How assessments work, answering Konvu's questions, reading the evidence, and reviewing results.
* [**Exploit Reproduction**](/konvu/triage-and-remediation/exploit-reproduction.md): How reproduction works, reading a result, re-running, and reproducing scanner findings.
* [**Triage List View**](/konvu/triage-and-remediation/triage/triage-list-view.md): Filter, sort, and act on findings in bulk.
* [**Dismissing False Positives**](/konvu/triage-and-remediation/triage/dismissing-false-positives.md): Dismiss false positives in Konvu and in your scanner.

{% hint style="info" %}
Both methods read your code. [Connect your source code](/konvu/get-started/connect-your-environment/source-code.md) before triaging.
{% endhint %}


---

# 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/triage.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.