Elastic Security 🟦

Elastic Security provides SIEM capabilities built on the Elasticsearch/Logstash/Kibana (ELK) stack.

Components

  • Elasticsearch β€” Security events storage and search
  • Beats/Fleet β€” Lightweight agents for log collection
  • Elastic Defend β€” Endpoint security integration (replacement for Endpoint Integrations)
  • Kibana Security β€” Dashboards, detection rules, case management

Architecture

Agents (Elastic Defend, Filebeat)
    β”‚
    β–Ό
Logstash / Fleet Server
    β”‚
    β–Ό
Elasticsearch Indexer
    β”‚
    β–Ό
Kibana (Security App)
  β”œβ”€β”€ Detection Rules
  β”œβ”€β”€ Cases
  β”œβ”€β”€ Timelines
  └── Dashboards

Detection Rules

Built-in rules mapped to MITRE ATT&CK. Custom rules written in KQL (Kibana Query Language).

event.category: process and process.name: "powershell.exe" and
process.args: "-enc" and not user.name: "SYSTEM"

Your Context

If you’re using Wazuh as primary SIEM, Elastic Security is a potential migration target for:

  • Large-scale environments (Elastic scales better at 10B+ events/day)
  • Teams already on the ELK stack
  • When you need advanced ML anomaly detection (Elastic SIEM has built-in ML jobs)