CyberKit

SIEM

Also called Security Information and Event Management.

Central platform that aggregates logs to alert, search, and investigate.

What it is

A Security Information and Event Management system collects, normalizes, and stores logs and events from across an environment so they can be searched, correlated, and alerted on. It is the primary place analysts run detections and pivot through evidence.

Why it matters

A detection program is usually built around a SIEM. It holds the historical data hunts and investigations depend on, and a gap in what it ingests is a gap in what defenders can see.

In practice

Pivoting from a single endpoint alert to every authentication event for that account by querying months of logs in the SIEM.

What to look for

  • Log sources that stopped sending without anyone noticing.
  • Rules firing on data that is parsed wrong or missing fields.
  • Searches that analysts run by hand every day, which should be detections.

Common mistake

Buying it and expecting detection out of the box. A SIEM is only as good as the data fed in and the rules written for it.

Use it in CyberKit

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

  • Correlation: Combining multiple events into a single, higher-confidence signal.
  • Telemetry Gap: A blind spot where the data needed to detect activity isn't collected.
  • Detection Rule: Logic that defines the conditions under which an alert fires.

Sources