Log Normalization
Also called Field Normalization.
Mapping diverse log formats onto a single common schema.
What it is
Log normalization transforms records from many different sources and formats into a consistent schema, so that equivalent concepts (a source IP, a username, an action) share the same field names and value conventions regardless of origin. It typically follows parsing in a log pipeline.
Why it matters
Normalized data is what makes cross-source correlation and detection rules possible, letting a single query span firewalls, endpoints, and cloud logs without per-source special-casing. Without it, analysts waste investigation time reconciling that source_ip, src, and ClientAddress all mean the same thing.
In practice
Mapping a firewall's src field, a proxy's c-ip field, and a cloud log's sourceIPAddress all to one normalized source.ip field for unified searching.
What to look for
- Field names mapped to one schema across sources.
- Parsing errors that drop or mangle fields.
- Timestamps converted to one time zone.
Common mistake
Normalizing once and forgetting it. Vendors change formats, and parsers silently break.
Use it in CyberKit
- Hunt Query Builder
Build a hunting query in KQL, SPL, LogScale or PowerQuery against documented field names, or start from a prebuilt hunt.
- Regex Tester
A live regex playground, with a library of common DFIR patterns.
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
- Structured Logging: Emitting logs as well-defined fields rather than free-form text.
- Log Enrichment: Adding external context to log events to make them more useful.
- Common Event Format: A standardized, key-value log format for interoperable event sharing.