CyberKit

False Negative

Also called FN.

Malicious activity that no detection caught.

What it is

A false negative is real malicious activity that fails to generate an alert: the threat occurred but the detection missed it, whether through a gap in logic, telemetry, or coverage. By nature, false negatives are invisible until uncovered later.

Why it matters

False negatives are the most dangerous detection failure because nobody is alerted to them; finding and closing them is much of why threat hunting and coverage analysis exist.

In practice

Discovering during an incident that the attacker's initial access went unalerted for weeks because no rule covered that technique.

What to look for

  • Incidents found by users or third parties instead of alerts.
  • Red team or purple team actions that did not trigger anything.
  • Rules that silently broke after a log format change.

Common mistake

Assuming no alerts means no attacks. Test detections regularly to find what they miss.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Sigma Open source

    A vendor neutral rule format that converts into queries for most SIEMs. Our notes.

  • YARA Open source

    Matches byte and string patterns in files or memory, the standard for malware rules. Our notes.

  • Suricata Open source

    Runs network rules against live traffic or captures and logs every match. Our notes.

  • Splunk Enterprise Security Commercial

    Where many teams run, tune and schedule detection searches in production.

Read next

  • False Positive: An alert that flags benign activity as malicious.
  • Telemetry Gap: A blind spot where the data needed to detect activity isn't collected.
  • Detection Coverage: How much of relevant adversary behavior your detections actually catch.

Sources