CyberKit

Common Event Format

Also called CEF.

A standardized, key-value log format for interoperable event sharing.

What it is

Common Event Format is a standardized log message format that pairs a fixed header (device vendor, product, version, event class, and severity) with an extensible set of key-value attributes. It is designed so that disparate devices can emit events a collector parses consistently.

Why it matters

Adopting a shared format like CEF reduces the parsing and normalization burden when onboarding many products, because fields arrive in a predictable structure. It illustrates the broader value of interoperable formats: less custom parser maintenance and fewer silent breakages as sources change.

In practice

A network appliance emitting CEF so its events drop into the pipeline with their fields already keyed, needing no bespoke parser.

What to look for

  • CEF headers with vendor, product and severity.
  • Extension fields mapped to your schema.
  • Vendors using custom fields in different ways.

Common mistake

Assuming CEF means consistent. Each vendor fills the fields its own way.

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

Sources