A Structured Three-Phase Workflow for Threat Hunting

· Original article ↗

Summary

A guide to structured threat hunting outlines planning, execution, and reporting, from gathering intelligence and forming hypotheses to investigating data and creating detections.

Key points

  • Structured hunts start by gathering threat intelligence, defining a hypothesis, and identifying relevant data sources such as logs, network traffic, and endpoint telemetry.
  • During execution, hunters query and analyze data, follow relevant clues, and test or refine their hypotheses.
  • The reporting phase documents findings, including when a hypothesis could not be validated.
  • Hunt findings can inform new or modified detection rules and help improve future hunts and security posture.
  • The article distinguishes structured hunts, which follow hypotheses and procedures, from less-guided, curiosity-driven hunts.

Article Details

Defense Focus
Use a structured, hypothesis-driven threat-hunting process to find overlooked malicious activity, reduce dwell time, improve detections, and strengthen security posture.
Detection Methods
  • Gather threat intelligence and historical data to identify risks, patterns, and potential threats.
  • Formulate and test hypotheses about potential adversaries, tactics, and techniques.
  • Query databases and analyze system logs, network traffic, and endpoint telemetry; investigate relevant TTPs and other clues.
  • Document findings and convert identifiable patterns or signatures into detection rules or rule improvements.
Data Sources
  • System logs
  • Network traffic
  • Endpoint telemetry
  • Historical data
  • Open-source intelligence
  • Social media feeds
Rule Types
  • Detection rules based on identifiable patterns or signatures
Defensive Actions
  • Define the activity being investigated, available data, and tools and techniques before starting a hunt.
  • Use a repeatable structured workflow with planning, execution, and reporting phases.
  • Continuously assess evidence against the hypothesis and refine the hunt or create new hypotheses as information emerges.
  • Summarize and document findings, including when the initial hypothesis cannot be validated.
  • Share relevant findings with the SOC or security team to build or update detections.
  • Use hunt results to improve the hunting process and the organization's security posture.

Vendors

Related Articles