Baselining
Also called Known-Good Baseline.
Establishing what 'normal' looks like so deviations stand out.
What it is
Baselining is the process of characterizing normal activity (for a host, account, network, or system image), so that deviations from it can be recognized. A known-good baseline captures the expected state to compare future observations against.
Why it matters
Without a baseline, analysts cannot tell unusual from routine; a sound baseline is the foundation that makes anomaly detection and hunting feasible and is itself a reference for verifying a clean rebuild.
In practice
Comparing a suspect server's running services against a known-good baseline to spot the one that does not belong.
What to look for
- Normal ranges for logins, processes and traffic per host or role.
- Baselines built during a quiet period that miss busy seasons.
- An attacker already present when the baseline was taken.
Common mistake
Building a baseline once. Normal changes, so refresh it on a schedule.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Hunt Query Builder
Build a hunting query in KQL, SPL, LogScale or PowerQuery against documented field names, or start from a prebuilt hunt.
- Rule Range
Write a regex, a Sigma rule, a YARA rule and a query pipeline, each graded live against samples, some of which you never see.
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
- Anomaly Detection: Flagging activity that deviates from an established normal baseline.
- Recovery: Restoring systems to normal, trusted operation after an incident.
- UEBA: Analytics that profile users and entities to flag risky deviations.