Theory · 8 min · The SOC and your job
True positive, false positive, benign positive
Close an alert with the right classification, and know why it matters for tuning.
Every alert ends with a verdict. A true positive means the rule caught what it was built to catch, and it was malicious. A false positive means the rule was wrong: bad logic, bad data, or a match on something it should not match.
There is a third answer that beginners forget: the rule was right, the activity was real, and it was allowed. A penetration test, an admin script, a backup job. Microsoft Defender calls this "Informational, expected activity"; many teams say benign positive or benign true positive.
The difference matters. A false positive is a reason to fix the rule. A benign positive is usually a reason to document an exception for that exact activity, not to switch the rule off, because the same behaviour from someone else would be an attack.
A false negative is the one you never see: an attack no rule caught. You find those by hunting and by reviewing incidents afterwards.
- True positive
- Real malicious activity, correctly detected.
- Benign positive
- Correctly detected, real, but authorised or expected.
- False positive
- The detection was wrong about what happened.
- False negative
- Malicious activity that no detection flagged.
Your turn: sort the evidence. Classify each closed alert.
Do the interactive check Free, in the browser.
Sources
- Manage incidents in the Microsoft Defender portal: classification Microsoft Learn
- Investigate Microsoft Sentinel incidents in depth Microsoft Learn