Practical Threat Hunting: Straight Facts and Substantial Impacts
summary
Threat hunting means doing incident response before alerts arrive, human-driven and hypothesis-led, not a vendor box; focus on collecting logs, full packet capture, endpoint telemetry and network metadata, then run daily reports (example: an 8:00am 24‑hour window outlier-process list) to spot anomalies, build allow‑lists, and escalate when investigations convert to IR. Use MITRE ATT&CK and red‑team emulation to validate coverage, inspect bash history for CLI traces, leverage JA3 and session metadata for encrypted traffic, and prioritize reducing attacker dwell time.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 3:30What is threat hunting?
- 10:11Why threat hunting matters
- 17:36Starting with situational awareness
- 22:32Hypothesis-driven hunting
- 27:20Red teaming and practical hunting
- 33:23Process and behavioral analysis
- 40:02Encrypted traffic and closing
related talks
31mThreat Hunting — Demystified
34mFormulating An Intelligence-Driven Threat Hunting Methodology
36mSo You Want to Build a Threat Hunt Program
40mHunt and Gather: Developing Effective Threat Hunting Techniques
48mPractical Learnings for Threat Hunting and Improving Your Security Posture
31mDon't Boil the Ocean: Using MITRE ATT&CK to Guide Hunting Activity
38mAdversary Detection Pipelines: Finally Making Your Threat Intel Useful
50mI Screwed Up Threat Hunting a Decade Ago and Now We're Fixing it With PEAK
