Skip to main content

What is a false positive in cybersecurity?

A false positive is an alert that flags benign activity as malicious. They waste analyst time and are the main driver of alert fatigue.

Glossary
Updated 2 min read

Definition

False positive

Also called FP, False alarm, False positive alert

A false positive is a security alert that incorrectly classifies benign activity as malicious, such as a detection firing on an approved admin script or a legitimate login from a new location.

How it works

NIST's glossary gives several definitions, including "an instance in which a security tool incorrectly classifies benign content as malicious" and simply "incorrectly classifying benign activity as malicious." False positives come from rules that match too broadly, from missing context (the rule doesn't know a host is a build server), from stale baselines, and from noisy or mis-parsed data.

NIST SP 800-61r3 notes that the volume of potentially adverse events is generally high and that anomalies may have benign or malicious foundations, which is why it recommends tools that filter large event sets down to what humans can review. Tuning is the main remedy: adding exclusions, tightening thresholds, joining context such as asset owners or approved-app lists, and retiring rules that never catch anything real.

Example

A detection flags any OAuth app granted access to sensitive Google Workspace scopes. Most hits are apps the security team already approved, so analysts close them one by one. Cotool's detection page shows the fix as a tuning change proposed after a run of false positives closed in triage: exclude client IDs listed in the security team's register of approved OAuth apps, then confirm in a backtest that the true positives still fire.

Why it matters for a SOC

Every false positive costs an analyst investigation time, and a high rate teaches people to skim, which is how alert fatigue leads to real alerts being missed. It also discourages teams from writing new detections at all. Tracking the outcome of each alert, feeding it back to the detection engineer, and testing tuning changes against known attacks so they don't create false negatives is the core loop of a healthy SOC.

Go deeper

FAQ

What is the difference between a false positive and a false negative?
A false positive is an alert on activity that turns out to be benign. A false negative is a real attack that produced no alert. Tuning a detection to cut false positives can create false negatives if it excludes too much, so changes should be tested against known attacks.
What is a benign true positive?
A benign true positive is an alert where the detection worked as designed and the activity really happened, but it was authorized, such as a penetration test or an approved change. Many SOCs track it separately from false positives because the fix is different.

Sources

  1. False Positive - Glossary | CSRC · accessed November 16, 2026
  2. NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management · accessed November 16, 2026
  3. AI Detection Engineering with Python Detections | Cotool · accessed November 16, 2026

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo