What threat hunting involves
Proactive hunting isn't a random search through security data. At Huntress, our analysts follow a structured methodology built around two core concepts: HACK (the types of triggers that surface hidden threats) and PREVENT (the steps that make each hunt successful).
The HACK framework: Four ways hunters find hidden threats
Most security tools wait for a known bad thing to happen before firing an alert. Huntress hunters don't wait—they go looking. Our analysts use four distinct trigger types to find attacker activity that flies under the radar:
Hypothesis-driven hunting starts with a question: Is a threat actor using cloud service tokens to move laterally in our environment? Analysts form a theory based on emerging attacker tradecraft or threat intelligence, then gather the relevant telemetry—endpoint logs, DNS queries, cloud audit trails—to confirm or deny it.
Anomaly-driven hunting uses telemetry across a large number of systems to identify where activity falls outside a known baseline. A single off-hours login might mean nothing. The same pattern across dozens of endpoints is a different story.
Cluster-driven hunting looks at the full picture around a specific user or system. Individually, each action might look like routine admin behavior. Clustered together over a defined time window, the same activity can reveal an attacker who's been blending in plain sight.
Knowledge-driven hunting takes threat intelligence—an IoC from a feed, a known technique tied to a specific threat actor—and runs it retrospectively across historical data. This is how Huntress analysts catch intrusions that happened weeks before anyone noticed something was wrong.
The PREVENT framework: How a hunt actually runs
Once a trigger is identified, our analysts follow a repeatable process to take it from a hunch to a resolved incident:
Plan: Define a hypothesis, scope the hunt, and identify what data is needed. This keeps hunts focused rather than sprawling.
Research: Pull from blogs, threat feeds, intel reports, and social media chatter to sharpen the hypothesis and understand what "confirmed" looks like before searching.
Execute: Run queries across available telemetry using the scoped hypothesis. The goal is to confirm or deny—not to find everything, but to find the right thing.
Verify: Use live data to add context, recreate attack paths, and rule out false positives before escalating. This is where noisy alerts get filtered and real threats get confirmed.
Enact: On a true positive, response kicks off immediately: isolate systems, deploy host tasking, and open the incident report.
Notify: The partner is informed of what was found and what's being done. Internally, the SOC, Tactical Response, and Hunting teams are looped in so no one is working blind.
Transform: Every hunt ends with a feedback loop. Lessons learned become new product detectors, YARA and SIGMA rules, blog posts, or awareness shared across teams—so the next hunt starts smarter.