Skip to main content

What is log normalization?

Log normalization converts fields from different log formats into one consistent representation so events can be searched and correlated together.

Glossary
Updated 1 min read

Definition

Log normalization

Also called Log parsing, Data normalization, Event normalization

Log normalization is the process of converting each field in log data from many different sources into a consistent name, format, and data type, so events can be searched, correlated, and analyzed together.

How it works

NIST SP 800-92 defines log normalization as converting each log data field to a particular data representation and categorizing it consistently. Its example is time: one system stores the event time in twelve-hour format as "Timestamp," another uses twenty-four-hour format as "Event Time" with the time zone in a separate field, and normalization stores both in a single format.

In practice, a pipeline parses each raw event into fields, renames them to a common schema, converts types (strings to IP addresses, epoch seconds to timestamps), and categorizes the event. Common target schemas include the Elastic Common Schema, the Open Cybersecurity Schema Framework (OCSF), and each SIEM's own data model.

Example

Okta calls the user actor.alternateId, AWS CloudTrail puts it under userIdentity, and a firewall logs src_user. After normalization all three land in one user field, so a single query, "show everything this user did in the last day," works across identity, cloud, and network logs. Without it, every query and detection has to know every source's field names.

Why it matters for a SOC

Correlation and portable detections depend on it. A Sigma rule or a hunting query only runs across sources if their fields mean the same thing. NIST also warns that normalization can be very resource-intensive, especially for complex entries such as intrusion detection logs, and every new or custom source needs a parser that someone maintains. Broken parsing is a quiet failure: the logs arrive, but detections keyed on missing fields never fire.

Some platforms now automate the parser work. Cotool's SIEM, for example, detects the schema of custom and in-house log sources, parses every field automatically, and validates the result on real events before the source goes live.

Go deeper

Sources

  1. NIST SP 800-92: Guide to Computer Security Log Management · accessed November 16, 2026
  2. Elastic Common Schema (ECS) reference · accessed November 16, 2026
  3. AI-Native SIEM Built for Agents | Cotool · accessed November 16, 2026

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo