Correlation
Combining multiple events into a single, higher-confidence signal.
What it is
Correlation is the linking of multiple events or alerts (across time, hosts, or data sources) to identify a pattern that no single event reveals on its own. It turns scattered observations into one coherent picture.
Why it matters
Many attacks only become visible through correlation, because each individual step looks ordinary; relating them is how defenders reconstruct an attack chain from disparate logs.
In practice
Correlating a failed-logon burst, a successful logon, and a new admin account into one account-compromise narrative.
What to look for
- Several low-severity events on one host or user in a short window.
- Sequences that match an attack path, such as phish, then logon, then discovery.
- Correlation rules that never fire because field names differ across sources.
Common mistake
Correlating on fields that are not normalized. Mismatched names make the rule miss every 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
- SIEM: Central platform that aggregates logs to alert, search, and investigate.
- Enrichment: Adding context to an alert to speed up and sharpen decisions.
- XDR: Detection and response correlated across endpoint, network, and cloud.