> 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/reference/glossary.md). # Glossary The terms these docs use, and what each one means in Konvu. ## Findings and sources | Term | Meaning | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Finding** | Anything Konvu triages: a dependency, code, container, or secret finding, or a vulnerability report. See [Finding Types](/konvu/triage-and-remediation/finding-types.md). | | **Vulnerability report** | A finding that arrives as a document: a bug bounty submission, a pentest report, a scanner export, or the output of an AI code security tool. See [Vulnerability Reports](/konvu/triage-and-remediation/finding-types/vulnerability-reports.md). | | **Scanner** | A tool that produces findings, such as Snyk, Semgrep, or Wiz. | | **Integration** | A connection between Konvu and another tool, set up on the **Integrations** page. | | **Source** | Where a finding came from: a scanner, a bug bounty program, an upload, or the API. | | **Program** | The scope and rules a vulnerability report is triaged against. | ## Triage | Term | Meaning | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Triage** | Deciding which findings are real and exploitable. Konvu triages with two methods: exploitability assessment and exploit reproduction. See [Triage](/konvu/triage-and-remediation/triage.md). | | **Exploitability assessment** | The first triage method. An agent checks the conditions for an exploit against your code and environment. See [Exploitability Assessment](/konvu/triage-and-remediation/exploitability-assessment.md). | | **Assessment** | What an exploitability assessment produces: an assessment result and the evidence behind it. | | **Assessment result** | One of **Exploitable**, **False Positive**, **Needs input**, or **Inconclusive**. A finding Konvu has not assessed yet is **Not assessed**. | | **Exploitability checklist** | The conditions that must all hold for a vulnerability to be exploitable. See [Vulnerability Enrichment](/konvu/triage-and-remediation/finding-types/dependencies/vulnerability-enrichment.md). | | **Exploit reproduction** | The second triage method. Konvu deploys your application in an isolated sandbox and an agent runs the exploit. See [Exploit Reproduction](/konvu/triage-and-remediation/exploit-reproduction.md). | | **Reproduction result** | One of **Reproduced**, **Not Exploitable**, **Hardening**, or **Inconclusive**. See [Reading a Reproduction](/konvu/triage-and-remediation/exploit-reproduction/reading-a-reproduction.md). | | **Sandbox** | The isolated environment where Konvu deploys your application for an exploit reproduction. Nothing runs against your infrastructure. | | **Dismiss** | Close a finding as a false positive in Konvu. Konvu can write the dismissal back to your scanner. | | **Assessment scope** | The severities and repositories Konvu assesses automatically. | ## Remediation and delivery | Term | Meaning | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Remediation plan** | Konvu's plan to fix a finding: the target version or code change, and what it affects. | | **Fix pull request** | A pull request Konvu opens to fix an exploitable finding. See [Fix Pull Requests](/konvu/triage-and-remediation/remediate/fix-pull-requests.md). | | **Fix prompt** | A prompt you copy into your coding agent to fix a reproduced vulnerability report. | | **Forwarding** | Sending assessments automatically to another tool, such as ArmorCode or Wiz. See [Data Forwarding](/konvu/triage-and-remediation/monitor-and-deliver/data-forwarding.md). | | **Delivery** | One assessment sent to a destination, listed under **Delivery activity**. | | **Write-back** | Updating a finding's state in your scanner from Konvu, such as a dismissal. | ## Your account | Term | Meaning | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Organization** | Your company's Konvu tenant. Settings that apply to everyone live under **Organization Settings**. | | **Credits** | The budget that pays for assessments, split by finding type. See [Assessment Credits](/konvu/administration/assessment-credits.md). | | **Source code analysis** | How Konvu reads your repositories once connected, either managed by Konvu or self-hosted. See [Connect Your Environment](/konvu/get-started/connect-your-environment.md). | --- # 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/reference/glossary.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.