> 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/dismissing-false-positives.md).

# Dismissing False Positives

When a finding is assessed as False Positive, dismiss it in your scanner to clean up your backlog.

When an assessment result is **False Positive**, Konvu has found strong evidence that the vulnerability is not exploitable in your environment. Dismissing these findings writes the result back to your scanner, cleaning up your backlog so your team can focus on real risks.

## Before you dismiss

Review the [evidence](/konvu/triage-and-remediation/exploitability-assessment/reading-an-assessment.md) to understand why Konvu determined the finding is a false positive. Common reasons include:

* The vulnerable function is not reachable from your application code.
* Your application's OS, runtime, or framework doesn't match the vulnerability's requirements.
* The code uses a safe API variant or applies input validation that prevents exploitation.
* Runtime data confirms the vulnerable code path is never executed.

If the evidence makes sense and the confidence is reasonable, proceed with dismissal. If something looks off, [rate the assessment](/konvu/triage-and-remediation/exploitability-assessment/reviewing-assessments.md#rating-an-assessment) as disagree and investigate further.

## Dismissing in the UI

### Individual dismissal

From the finding detail page:

1. Click on **SCA Findings** to see the linked scanner findings.
2. Click **"Dismiss in \[Scanner Name]"** to dismiss the finding in your SCA tool.

Konvu sends the dismissal to your scanner with the appropriate metadata (reason, reference link). The finding is also marked as closed in Konvu.

<figure><img src="https://4216786002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd2uS6kuROSFKDrT5HC1U%2Fuploads%2FGztZziw8juTkKrEI7cBI%2Fimage.png?alt=media&amp;token=ccd16314-2c99-4bc6-a4d1-2a20fae1c6c8" alt=""><figcaption></figcaption></figure>

### Bulk dismissal from the Triage page

Visit the [Triage page](https://app.konvu.com/sca_triage) to select and act on them in bulk. This is the most efficient way to clean up large backlogs. Dismiss an entire group of findings that share the same false positive reason in a single action.

<figure><img src="https://4216786002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd2uS6kuROSFKDrT5HC1U%2Fuploads%2FTSUX4FcCNXuUlpVgp3fH%2Fimage.png?alt=media&amp;token=cee5e363-5b1b-48b2-95d7-c6f77aff5424" alt=""><figcaption></figcaption></figure>

## What happens after dismissal

When you dismiss a finding:

1. **Konvu marks the finding as closed.**
2. **The dismissal writes back to your scanner** (where supported) with the following metadata:

<table><thead><tr><th width="220.66015625">Scanner</th><th>What Konvu sets</th></tr></thead><tbody><tr><td><strong>GitHub Dependabot</strong></td><td>Dismiss Reason: "Vulnerable code not in use." Dismiss Comment: "Dismissed by Konvu, more information at {finding link}"</td></tr><tr><td><strong>Snyk</strong></td><td>Ignore Type: "Not vulnerable." Ignore Reason: "Dismissed by {user} (through Konvu), more information at {finding link}"</td></tr><tr><td><strong>Semgrep</strong></td><td>Triage State: "Ignored." Triage Reason: "False Positive." Note: "Dismissed in Konvu"</td></tr></tbody></table>

For other scanners, the finding detail page links to the scanner dashboard where you can dismiss manually.

## Undoing a dismissal

If you dismissed a finding by mistake or your environment changed:

1. Open the finding in Konvu.
2. Re-open the finding from the finding detail page.

Re-opening in Konvu does not automatically re-open the alert in your scanner. You'll need to manually re-open it in the scanner dashboard if needed.

{% hint style="info" %}
Dismissing false positives is most impactful when done from the Overview page, where Konvu groups findings by dismiss reason. A single bulk action can clear dozens of findings from your backlog.
{% 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/dismissing-false-positives.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.