# False positive

GLOSSARY, read 10 Nov 2026

**Definition.** A false positive is a finding that reports a weakness that is not present on the asset, for example from a version-string match on a backported fix. Marking one needs a reason and a reviewer, so that the same finding does not return on the next scan. Rates vary by tool and scan type.

Programs track false positives by source to learn which tools to tune or trust. A tool with a high rate loses the owners' trust and slows every ticket.

Platforms commonly handle them as a request workflow that ends in suppression.

## A sourced example

On 2026-11-10 Brinqa's automation documentation named false positive requests, alongside exception requests, as a workflow its automation engine drives.

## Related terms

- [Vulnerability exception](/glossary/vulnerability-exception/)
- [Authenticated scanning](/glossary/authenticated-scanning/)
- [Finding](/glossary/finding/)
- [Risk acceptance](/glossary/risk-acceptance/)

## Sources

- Source for the example: False positive: https://docs.brinqa.com/docs/automation (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/false-positive/
