> 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/exploitability-assessment.md). # Exploitability Assessment The first triage method: Konvu reads your code to decide whether each finding can be exploited. Exploitability Assessment is the first of Konvu's two [triage](/konvu/triage-and-remediation/triage.md) methods. For every finding in your assessment scope, an agent checks the conditions for an exploit against your code and environment, and returns an assessment result with the evidence behind it. When you need proof beyond the assessment, use [Exploit Reproduction](/konvu/triage-and-remediation/exploit-reproduction.md). **What you'll find here:** * [**How Assessments Work**](/konvu/triage-and-remediation/exploitability-assessment/how-assessments-work.md): Assessment statuses, results, and lifecycle. Start here. * [**Answering Konvu's Questions**](/konvu/triage-and-remediation/exploitability-assessment/answering-konvus-questions.md): When Konvu needs your input to complete an assessment. * [**Reading an Assessment**](/konvu/triage-and-remediation/exploitability-assessment/reading-an-assessment.md): Understanding the evidence behind each assessment result. * [**Reviewing Assessments**](/konvu/triage-and-remediation/exploitability-assessment/reviewing-assessments.md): Evaluating results, providing feedback, and re-triggering assessments. Secrets are assessed differently (validity, impact, exposure). See [Secrets](/konvu/triage-and-remediation/finding-types/secrets.md). {% hint style="info" %} Before triaging, make sure you've [connected your source code](/konvu/get-started/connect-your-environment/source-code.md). Assessments need code context to produce useful results. {% endhint %} ## Next steps * [**Exploit Reproduction**](/konvu/triage-and-remediation/exploit-reproduction.md): Get proof that a finding is exploitable by running the exploit in an isolated sandbox. * [**Triage List View**](/konvu/triage-and-remediation/triage/triage-list-view.md) and [**Dismissing False Positives**](/konvu/triage-and-remediation/triage/dismissing-false-positives.md): Act on results in bulk and dismiss false positives in your scanner. * [**Remediate**](/konvu/triage-and-remediation/remediate.md): Remediation plans and fix pull requests for exploitable findings. * [**Monitor & Deliver**](/konvu/triage-and-remediation/monitor-and-deliver.md): Track your security posture over time and send results to your team. --- # 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/exploitability-assessment.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.