Learning paths › Security Engineer › 04. Intrusion Detection
04. Intrusion Detection
Where the sensor has to sit before any rule can work, what a rule header can possibly see, writing a signature that matches what you meant, and the tuning decisions — threshold, detection filter, suppress, or rewrite the rule — that decide whether anyone is still reading its alerts next month. Two labs are live: rules are parsed by idstools, the real library, and replayed against synthetic fixtures.
Lessons
- What A Sensor Is Actually Claiming When It Alerts
- Where You Put The Sensor Decides What It Can Possibly Detect
- Reading A Rule Header Before You Write One
- Lab: Catch The Beacon Without Catching The Browser
- Threshold, Detection Filter And Suppress Answer Three Different Questions
- Four Alerts, One Analyst, One Hour
- Release an IDS ruleset with controls, dependencies and rollback
- Lab: Write A Rule That Fires On The Marker And Nothing Else
More in Security Engineer
- 00. Prerequisites: Packets, Protocols & Log Reading
- 01. Security Fundamentals & SOC Workflow
- 02. Firewall & Perimeter Rule Logic
- 03. Network Traffic Analysis
- 05. SIEM & Log Correlation
- 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