Telemetry Gap
Also called Visibility Gap.
A blind spot where the data needed to detect activity isn't collected.
What it is
A telemetry gap is an area where the data needed to detect or investigate activity is not being collected or retained, leaving defenders blind regardless of how good their detection logic is. It is a gap in evidence, not in rules.
Why it matters
You cannot detect or investigate what you cannot see. Telemetry gaps quietly cap the entire program's effectiveness and are a common reason an incident goes unnoticed or cannot be fully reconstructed.
In practice
Realizing during an investigation that command-line logging was never enabled, so there is no record of what the attacker ran.
What to look for
- Hosts, cloud services or apps with no logs in the SIEM.
- Log levels set too low to capture key events.
- Retention shorter than typical dwell time.
Common mistake
Finding gaps during an incident. Map data sources to techniques ahead of time.
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.
-
Splunk Enterprise Security Commercial
A SIEM where these logs are searched with SPL and turned into correlation searches.
-
Microsoft Sentinel Commercial
Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.
-
Elastic Security Commercial
A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.
-
Wazuh Open source
An open source platform that collects, decodes and alerts on host and log data.
Read next
- Detection Coverage: How much of relevant adversary behavior your detections actually catch.
- SIEM: Central platform that aggregates logs to alert, search, and investigate.
- False Negative: Malicious activity that no detection caught.