Learning paths › Security Engineer › 05. SIEM & Log Correlation
05. SIEM & Log Correlation
Getting logs in, making them mean the same thing, and correlating across sources without a clock skew quietly reversing cause and effect. The module spends its first half on the pipeline, because that is where detection estates actually fail — a learner who only ever writes rules spends a career lowering thresholds. Every lesson works a simulated correlation console over authored fixtures; no agent, manager or indexer runs.
Lessons
- Collection: What Reaches The Pipeline, And What Silently Does Not
- Normalization: One Field Name For One Idea
- Clock, Transport And Retention: Three Ways The Pipeline Lies
- Decoders: Extracting A Field Without Inventing One
- Writing A Detection Rule: Conditions, Grouping And Threshold
- The Contributing Set: What An Alert Is Actually Claiming
- Correlating Across Sources: The Join You Have To Make Yourself
- Tuning Against Benign Activity: The Service Account Problem
- Validating A Detection: Proving It Fires And Proving It Stops
- Work an alert queue with evidence, impact and explicit closure reasons
- The Alert Nobody Reads Any More
- Something Left The Building And Nobody Can Say What
- Nothing Fired, And Somebody Has Been Here For Four Hours
- Sixteen Alerts, One Intrusion, And A Rule Nobody Tested
More in Security Engineer
- 00. Prerequisites: Packets, Protocols & Log Reading
- 01. Security Fundamentals & SOC Workflow
- 02. Firewall & Perimeter Rule Logic
- 03. Network Traffic Analysis
- 04. Intrusion Detection
- 06. Vulnerability Management
- 07. Multi-Source Incident Response (Capstone)
- Cisco ASA
- Cisco Firepower (FTD)
- Fortinet FortiGate
- Splunk for Network & Security Operations
- Snort & Suricata IDS/IPS
- Security Scenarios & Capstone
- Zscaler: Secure Web & Private Access