CyberKit

Threat Hunting

Proactively searching for threats that evaded detection.

What it is

Threat hunting is the proactive, hypothesis-driven search through data for adversary activity that automated alerts missed, rather than waiting for a tool to fire.

Why it matters

It catches stealthy intrusions early, reduces dwell time, and feeds new detections back into monitoring. Good hunts target behaviors (TTPs), not just known indicators.

In practice

Hypothesizing an attacker used a built-in tool, then hunting its command-line usage fleet-wide.

What to look for

  • A written hypothesis before the search starts.
  • Queries that look for behavior, not only known indicators.
  • Findings that turn into new detections.

Common mistake

Hunting without a hypothesis. Browsing logs feels productive and rarely finds anything; start from a technique you can test.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Splunk Enterprise Security Commercial

    A SIEM where these logs are searched with SPL and turned into correlation searches.

  • Microsoft Sentinel Commercial

    Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.

  • Elastic Security Commercial

    A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.

  • Wazuh Open source

    An open source platform that collects, decodes and alerts on host and log data.

Tools practitioners use

  • Velociraptor: Endpoint visibility & remote collection at scale

Read next

  • Pyramid of Pain: Ranks indicators by how much they hurt attackers to lose.
  • Dwell Time: How long an attacker goes undetected in a network.
  • MITRE ATT&CK: A public knowledge base of real adversary tactics and techniques.

Sources