> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/invalid-findings-and-false-positives.md).

# Invalid findings and false positives

How to handle invalid findings and false positives in Snyk API and Web

In security scans, Snyk API & Web avoids false positives because they bring a costly overhead of manual analysis and resolution of vulnerabilities.

When Snyk finds a vulnerability, it creates a finding with a **Not fixed** state. This state can change automatically or manually, as explained in [Finding states](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/finding-states.md).

When a user manually changes the state to **Invalid**, the vulnerability does not exist and is a candidate for a false positive.

This triggers Snyk to investigate further to confirm it:

* If it is a false positive, Snyk improves the identification of vulnerabilities so that it no longer reports the vulnerability.
* If not, Snyk contacts the user to explain how the vulnerability can be exploited.

## Accept risk instead of marking as invalid

In some situations, a finding is not a false positive (that is, **Invalid**) and is accepted in the specific context instead.

For example, if a target uses Cloudflare with Transport Layer Security (TLS) 1.2 with the default configuration, the scanner reports the weak cipher suites enabled vulnerability because of the Cipher Block Chaining (CBC) weak cipher.

However, using TLS 1.2 is acceptable to support a broader range of users for business reasons.

In this case, change the state of the finding to **Accept risk**.

Visit [Manage findings](/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/manage-findings.md) to learn how to change the state.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/review-and-fix/invalid-findings-and-false-positives.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.