What is Threat Hunting? Complete Guide to Proactive Cyber Defense

  • Written by John Price
  • Reviewed by Kevin Schewe and Ratan Gupta
  • 29 min read
Threat hunting is the proactive and iterative process of searching through networks, endpoints, and datasets to detect and isolate advanced threats that evade existing security solutions. While traditional security operates reactively, responding to alerts generated by automated systems, threat hunting assumes that sophisticated attackers have already breached defenses and actively searches for evidence of their presence. With the average time to detect a breach at 204 days, threat hunting has become essential for organizations seeking to reduce dwell time and prevent catastrophic damage from undetected intrusions.

What is Threat Hunting?

Threat hunting is a proactive security practice where expert analysts search through enterprise environments to discover malicious actors that have bypassed automated security defenses. Unlike reactive security approaches that wait for alerts from security tools, threat hunters operate under the assumption that adversaries are already present within the network and actively seek evidence of their activities.

At its core, threat hunting combines human expertise with advanced analytics to identify subtle indicators of compromise (IOCs) and anomalous behaviors that automated systems miss. Threat hunters leverage threat intelligence, behavioral analytics, forensic techniques, and deep system knowledge to discover hidden threats before they can cause significant damage.

Key Characteristics of Threat Hunting

  • Proactive, Not Reactive: Hunters actively search for threats rather than waiting for alerts
  • Assume Breach: Operates with the mindset that adversaries have already compromised systems
  • Human-Driven: Relies on human expertise, creativity, and intuition beyond automated tools
  • Intelligence-Informed: Leverages threat intelligence and knowledge of attacker tactics
  • Iterative Process: Continuous cycle of hypothesis creation, investigation, and refinement
  • Creates Lasting Value: Discoveries lead to improved detections and hardened defenses

The Evolution of Threat Hunting

Threat hunting has evolved significantly as the cyber threat landscape has grown more sophisticated:

Pre-2010 (Reactive Security): Organizations relied primarily on signature-based antivirus and firewall alerts. Security teams responded to known threats but lacked proactive capabilities.

2010-2015 (Emergence of Hunting): Advanced persistent threats (APTs) demonstrated that patient, sophisticated adversaries could remain undetected for months or years. Forward-thinking organizations began proactive threat hunting using SIEM tools and manual log analysis.

2015-2020 (Hunting Maturation): Dedicated threat hunting teams emerged as distinct from SOC operations. Frameworks like MITRE ATT&CK provided structured approaches. EDR tools enhanced endpoint visibility for hunters.

2020-Present (Advanced Hunting): Modern threat hunting integrates AI/ML analytics, automated hunting playbooks, threat intelligence platforms, and behavioral analytics. Organizations recognize hunting as essential for detecting sophisticated threats.

Proactive Threat Hunting Services

subrosa's expert threat hunters proactively search your environment for hidden threats, reducing dwell time and preventing breaches before they escalate.

Learn About Our Threat Hunting Services

Why Threat Hunting Matters

Threat hunting has become critical as organizations face increasingly sophisticated adversaries and expanding attack surfaces:

1. Detection Gap in Automated Security

According to Verizon's Data Breach Investigations Report, 68% of breaches take months to discover. Automated security tools generate alerts for known threats but struggle with:

  • Novel attack techniques without signatures
  • Living-off-the-land attacks using legitimate tools
  • Slow-and-low attacks designed to evade detection thresholds
  • Insider threats with authorized access
  • Supply chain compromises through trusted channels

Threat hunting bridges this gap by actively searching for subtle indicators that automated systems miss.

2. Reducing Dwell Time

Dwell time, the period between initial compromise and detection, averages 204 days globally. Each day an attacker remains undetected increases potential damage:

  • Additional systems compromised
  • More data exfiltrated
  • Deeper persistence mechanisms installed
  • Greater lateral movement throughout the network
  • Higher remediation costs and business impact

Organizations with active threat hunting programs reduce dwell time by up to 75%, detecting intrusions in weeks or days rather than months.

3. Advanced Persistent Threats (APTs)

APT groups employ sophisticated techniques specifically designed to evade detection:

  • Custom malware without known signatures
  • Encrypted command and control channels
  • Credential theft and legitimate tool usage
  • Patient reconnaissance spanning months
  • Anti-forensic techniques covering tracks

Traditional security tools may generate no alerts during APT campaigns. Threat hunting provides the proactive investigation needed to discover these sophisticated intrusions.

4. Compliance and Due Diligence

Regulatory frameworks increasingly expect proactive security measures:

  • NIST Cybersecurity Framework: Emphasizes continuous monitoring and proactive threat detection
  • GDPR: Requires demonstrable security efforts and breach detection capabilities
  • PCI DSS: Mandates active threat detection and response capabilities
  • Cyber Insurance: Policies increasingly require evidence of proactive security practices

5. Creating Lasting Security Improvements

Unlike reactive incident response, threat hunting produces compounding benefits:

  • Improved Detections: Findings lead to new automated alerts and rules
  • Enhanced Visibility: Identifies monitoring gaps requiring additional data sources
  • Security Hardening: Discovers misconfigurations and vulnerabilities
  • Intelligence Development: Builds organizational knowledge of threats
  • Team Development: Hunters develop deep expertise benefiting all security operations

6. High-Value Asset Protection

Organizations with "crown jewels", intellectual property, customer data, financial systems, or critical infrastructure, cannot rely solely on perimeter defenses. Threat hunting provides focused protection for these high-value targets through:

  • Regular hunting campaigns focused on critical systems
  • Behavioral baseline establishment for sensitive assets
  • Heightened scrutiny of access to valuable resources
  • Proactive identification of reconnaissance activities
Real-World Impact: A global financial institution's threat hunting team discovered an APT group that had maintained access for 18 months while evading all automated security controls. The hunters identified the intrusion through subtle network anomalies and unusual authentication patterns. Early discovery prevented planned theft of customer financial data affecting millions of accounts, avoiding an estimated $500+ million in damages and regulatory penalties.

Threat Hunting vs. Traditional Detection

Understanding the distinction between threat hunting and traditional detection helps organizations implement both effectively:

Traditional Detection (Reactive)

Approach: Security tools continuously monitor for known attack patterns and generate alerts when detections occur.

Characteristics:

  • Automated and rule-based
  • Responds to predefined signatures and patterns
  • Covers known threats efficiently
  • Operates 24/7 without human intervention
  • Generates high alert volumes
  • Limited effectiveness against novel threats

Strengths:

  • Consistent monitoring without human fatigue
  • Fast detection of known threats
  • Scalable across large environments
  • Cost-effective for volume detection

Limitations:

  • Blind to unknown attack techniques
  • Cannot detect sophisticated evasion
  • Generates false positives requiring triage
  • Reactive rather than proactive

Threat Hunting (Proactive)

Approach: Security experts actively search for threats based on hypotheses, intelligence, and intuition, assuming adversaries are already present.

Characteristics:

  • Human-driven and analytical
  • Searches for unknown and sophisticated threats
  • Investigates anomalies and suspicious patterns
  • Requires specialized expertise and time
  • Creates new detection capabilities
  • Discovers threats before significant damage

Strengths:

  • Detects novel and sophisticated attacks
  • Reduces dwell time dramatically
  • Identifies detection gaps
  • Produces lasting security improvements
  • Adapts to evolving threat landscape

Limitations:

  • Resource-intensive requiring expert hunters
  • Cannot operate continuously on all assets
  • Requires significant data and tooling
  • Findings require validation and response
Aspect Traditional Detection Threat Hunting
Approach Reactive Proactive
Trigger Alert-driven Hypothesis-driven
Automation Highly automated Human-led with tool support
Threat Coverage Known threats Unknown and advanced threats
Frequency Continuous 24/7 Campaign-based or periodic
Assumption Defenses work Assume breach occurred
Outcome Incident detection Hidden threat discovery + improved detection

Complementary Approaches

Effective security programs implement both detection and hunting:

  • Detection Provides Baseline: Automated systems handle known threats efficiently at scale
  • Hunting Finds Gaps: Proactive hunting discovers what automated tools miss
  • Hunting Improves Detection: Discoveries create new automated rules
  • Detection Informs Hunting: Alert patterns suggest hypotheses for hunting

The most mature organizations maintain 24/7 detection through their SOC while conducting regular threat hunting campaigns focused on high-risk areas, new threat intelligence, or periodic comprehensive sweeps.

Threat Hunting Maturity Model

Organizations progress through maturity levels as they develop threat hunting capabilities:

HMM Level 0: Initial/Ad Hoc

Characteristics:

  • No formal threat hunting program
  • Occasional manual investigations
  • Relies primarily on automated alerts
  • Limited threat intelligence integration
  • Reactive incident response focus

Typical Organizations: Small businesses, organizations with limited security resources

HMM Level 1: Minimal/Beginning

Characteristics:

  • Threat hunting performed occasionally
  • Relies on automated hunting tools
  • Limited human analysis and hypothesis creation
  • Basic use of threat intelligence feeds
  • Hunters use simple searches and queries

Typical Organizations: Mid-sized companies beginning hunting initiatives

Key Capabilities to Develop:

  • Establish regular hunting cadence
  • Train analysts on hunting techniques
  • Implement core hunting technologies (SIEM, EDR)
  • Create initial hunting playbooks

HMM Level 2: Procedural

Characteristics:

  • Regular scheduled threat hunting campaigns
  • Documented hunting procedures and playbooks
  • Data collection processes established
  • Hunters follow structured methodologies
  • Some integration of threat intelligence
  • Creation of automated detections from findings

Typical Organizations: Enterprises with dedicated security teams

Key Capabilities to Develop:

  • Formalize hunting methodology
  • Expand data sources and visibility
  • Enhance threat intelligence utilization
  • Establish metrics and reporting

HMM Level 3: Innovative

Characteristics:

  • Hypothesis-driven hunting based on intelligence
  • Deep integration with threat intelligence
  • Advanced analytics and machine learning utilization
  • Proactive hunting for specific adversary TTPs
  • Continuous improvement of hunting techniques
  • Hunters create custom tools and scripts

Typical Organizations: Large enterprises, security-focused organizations

Key Capabilities to Develop:

  • Develop advanced analytical techniques
  • Create automated hunting workflows
  • Enhance cross-team collaboration
  • Contribute to security community

HMM Level 4: Leading

Characteristics:

  • Continuous threat hunting operations
  • Highly automated hunting with human oversight
  • Advanced behavioral analytics and AI integration
  • Comprehensive threat intelligence program
  • Hunting insights drive security architecture
  • Industry leadership and knowledge sharing
  • Predictive hunting based on threat trends

Typical Organizations: Fortune 500 companies, critical infrastructure, high-target organizations

Maturity Level Hunting Frequency Primary Approach Team Size
Level 0 (Initial) None Reactive only 0
Level 1 (Minimal) Quarterly Automated tools 1-2 hunters
Level 2 (Procedural) Monthly Playbook-driven 2-5 hunters
Level 3 (Innovative) Weekly Hypothesis-driven 5-10 hunters
Level 4 (Leading) Continuous Intelligence-driven + automated 10+ hunters
Maturity Progression: Most organizations should aim for Level 2 (Procedural) as a realistic initial goal, achieving regular hunting campaigns with documented processes. Progression to Level 3 and beyond requires significant investment in personnel, technology, and organizational commitment but delivers substantial security improvements.

The Threat Hunting Methodology

Effective threat hunting follows a structured, iterative process:

Phase 1: Hypothesis Generation

Hunters create testable theories about how adversaries might compromise the environment.

Hypothesis Sources:

  • Threat Intelligence: Reports of campaigns targeting your industry
  • Historical Incidents: Previous attack patterns in your organization
  • Security Assessments: Penetration test findings or security gaps
  • MITRE ATT&CK: Specific tactics and techniques to investigate
  • Anomaly Identification: Unusual patterns observed during monitoring
  • Crown Jewel Analysis: Likely attack paths to critical assets

Example Hypotheses:

  • "Attackers are using PowerShell for lateral movement between servers"
  • "Credentials are being exfiltrated via DNS tunneling"
  • "Malware is communicating with C2 servers using encrypted channels on non-standard ports"
  • "Insider threat is accessing financial data outside normal business hours"
  • "Supply chain compromise introduced backdoors in third-party software"

Phase 2: Investigation Planning

Hunters determine what data and tools they need to test their hypothesis.

Planning Activities:

  • Identify required data sources (logs, telemetry, network traffic)
  • Determine investigation timeframe (days, weeks, months of data)
  • Select appropriate tools and techniques
  • Define success criteria (what confirms or refutes hypothesis)
  • Establish baseline behavior for comparison
  • Plan query strategies and analysis approaches

Phase 3: Data Collection

Gather relevant data from appropriate sources for analysis.

Common Data Sources:

  • SIEM logs and event data
  • EDR telemetry and endpoint logs
  • Network traffic captures (full packet or metadata)
  • Firewall and proxy logs
  • DNS query logs
  • Authentication and directory services logs
  • Cloud platform logs (AWS CloudTrail, Azure logs, etc.)
  • Application logs
  • Threat intelligence feeds

Phase 4: Analysis and Investigation

Hunters analyze collected data searching for evidence supporting their hypothesis.

Analysis Techniques:

  • Query-Based Searching: Using SPL, KQL, or SQL to find specific patterns
  • Statistical Analysis: Identifying outliers and anomalies
  • Timeline Analysis: Reconstructing event sequences
  • Correlation Analysis: Connecting related events across data sources
  • Pattern Matching: Using IOCs, YARA rules, or regex patterns
  • Behavioral Analysis: Comparing activity to established baselines
  • Visualization: Using graphs and charts to identify patterns

Phase 5: Pattern Discovery

Identify significant findings: confirmed threats, false positives, or interesting patterns requiring deeper investigation.

Potential Outcomes:

  • Confirmed Threat: Evidence of actual malicious activity
  • Benign Activity: Legitimate behavior that appeared suspicious
  • Security Gap: Monitoring blind spot or misconfiguration
  • New Hypothesis: Unexpected patterns suggesting additional investigation
  • False Positive: Alert or pattern with innocent explanation

Phase 6: Response and Remediation

If threats are confirmed, initiate incident response procedures.

Response Actions:

  • Escalate to incident response team
  • Isolate affected systems
  • Collect forensic evidence
  • Eradicate malicious presence
  • Recover and restore systems
  • Conduct root cause analysis

Phase 7: Automation and Improvement

Create lasting value from hunt findings through detection engineering and process improvement.

Improvement Activities:

  • Create automated detections for discovered threats
  • Update SIEM rules and correlation logic
  • Document new attack techniques and TTPs
  • Enhance threat intelligence with findings
  • Identify and remediate security gaps
  • Share findings with security community
  • Update hunting playbooks and procedures

Phase 8: Documentation and Reporting

Document the hunting process, findings, and outcomes.

Documentation Elements:

  • Hypothesis and investigation approach
  • Data sources and queries used
  • Findings and analysis results
  • Threats discovered (if any)
  • Automated detections created
  • Recommendations and next steps
  • Metrics and hunt effectiveness

Expert Threat Hunting from subrosa

Our certified threat hunters follow proven methodologies to discover hidden threats in your environment, reducing risk and improving your security posture.

Get Started with Threat Hunting

Hypothesis-Driven Threat Hunting

Hypothesis-driven hunting is the most mature and effective approach to threat hunting, focusing investigation efforts on specific, testable theories:

What is a Good Threat Hunting Hypothesis?

Effective hypotheses share common characteristics:

  • Specific and Testable: Clear enough to guide investigation with defined success criteria
  • Intelligence-Informed: Based on real threat actor TTPs or security gaps
  • Relevant to Environment: Applicable to your organization's assets and threat landscape
  • Actionable: Findings will drive security improvements
  • Scope-Appropriate: Not so broad as to be unwieldy, not so narrow as to miss threats

Hypothesis Creation Framework

Who: Which threat actor or insider might attack?

  • Nation-state APT groups
  • Cybercriminal organizations
  • Hacktivists
  • Malicious insiders

What: What are they trying to accomplish?

  • Data theft or espionage
  • Ransomware deployment
  • System disruption or sabotage
  • Financial fraud
  • Persistence for future access

How: What techniques might they use?

  • Initial access method (phishing, exploits, credentials)
  • Persistence mechanisms
  • Lateral movement techniques
  • Privilege escalation methods
  • Exfiltration channels

Where: What systems or data are they targeting?

  • Critical servers and databases
  • Executive workstations
  • Development environments
  • Financial systems
  • Intellectual property repositories

When: What time patterns might indicate malicious activity?

  • After-hours access to sensitive systems
  • Weekend data transfers
  • Holiday period reconnaissance
  • Following public disclosure of vulnerabilities

Example Hypotheses by Category

Initial Access Hypotheses

  • "Attackers gained access through phishing emails containing malicious Office documents with macros"
  • "Compromised VPN credentials are being used for remote access from unusual geographic locations"
  • "Public-facing web applications are being exploited to gain initial foothold"
  • "Supply chain compromise introduced backdoors through software updates"

Persistence Hypotheses

  • "Attackers created scheduled tasks on servers for persistent access"
  • "Malware modified registry run keys for automatic startup"
  • "Adversaries created unauthorized service accounts with high privileges"
  • "Web shells were planted on internet-facing servers"

Lateral Movement Hypotheses

  • "Attackers are using PowerShell remoting to move between servers"
  • "Pass-the-hash attacks are being used with stolen credentials"
  • "RDP connections between workstations indicate lateral movement"
  • "Attackers are leveraging administrative shares for file transfers"

Exfiltration Hypotheses

  • "Data is being exfiltrated through DNS tunneling"
  • "Large file uploads to cloud storage indicate data theft"
  • "Encrypted traffic on non-standard ports masks exfiltration"
  • "Email is being used to send sensitive data to external addresses"

Impact Hypotheses

  • "Ransomware is being staged for deployment across the network"
  • "Attackers are modifying financial transaction data"
  • "System configurations are being altered to cause disruptions"
  • "Backup systems are being targeted to prevent recovery"

Testing and Refining Hypotheses

As investigations proceed, hunters refine hypotheses based on findings:

  • Hypothesis Confirmed: Evidence supports theory, proceed with response
  • Hypothesis Refuted: No evidence found, document and move to next hypothesis
  • Hypothesis Refined: Partial evidence suggests modified theory
  • New Hypothesis Generated: Unexpected findings suggest new investigation paths

Essential Threat Hunting Techniques

Experienced threat hunters employ diverse techniques to discover hidden threats:

1. Baseline Analysis

Establish normal behavior patterns, then hunt for deviations indicating malicious activity.

Application:

  • Baseline normal authentication patterns (times, locations, frequencies)
  • Typical network traffic volumes and destinations
  • Standard process execution behaviors on endpoints
  • Regular data transfer patterns
  • Expected user behavior for roles

Detection Approach: Statistical analysis identifies anomalies significantly outside normal parameters

2. Stack Counting

Group similar events together and focus on rare or unique occurrences that stand out from common patterns.

Example Queries:

  • Processes running on only 1-2 hosts (potential malware)
  • Rare PowerShell command-line arguments
  • Uncommon network connections destinations
  • Unusual parent-child process relationships
  • Rare user agent strings in web traffic

3. Timeline Analysis

Reconstruct events chronologically to identify suspicious sequences and attack chains.

Hunting Focus:

  • Initial compromise indicators
  • Privilege escalation sequences
  • Lateral movement patterns
  • Exfiltration preparation and execution
  • Correlation of events across systems

4. Clustering and Grouping

Group related activities to identify campaigns or coordinated attacks.

Clustering Methods:

  • IP addresses and domains contacted
  • File hashes and malware families
  • TTP patterns consistent with specific threat actors
  • Compromised accounts and affected systems
  • Temporal correlation of events

5. Volume Analysis

Search for unusual data transfer volumes indicating exfiltration or other malicious activity.

Investigation Areas:

  • Unexpectedly large outbound network transfers
  • Unusual database query result sizes
  • Excessive file downloads or exports
  • Abnormal DNS query volumes
  • Unusual email attachment sizes or frequencies

6. Frequency Analysis

Identify activities occurring at suspicious frequencies suggesting automated or malicious behavior.

Examples:

  • Beaconing traffic with regular intervals (C2 communication)
  • Failed authentication attempts at high frequency (brute force)
  • Rapid sequential file access (automated data collection)
  • Periodic scheduled task execution at odd hours

7. IOC Searching (Indicator Hunting)

Leverage threat intelligence to search for known indicators of compromise.

IOC Types:

  • File hashes (MD5, SHA1, SHA256)
  • IP addresses and domains
  • URLs and URI patterns
  • Mutex names and registry keys
  • File names and paths
  • Certificate serial numbers

8. TTP-Based Hunting (Technique Hunting)

Search for evidence of specific attacker techniques rather than indicators, using frameworks like MITRE ATT&CK.

Example Techniques to Hunt:

  • T1059: Command and Scripting Interpreter
  • T1021: Remote Services
  • T1003: OS Credential Dumping
  • T1071: Application Layer Protocol (C2)
  • T1053: Scheduled Task/Job

9. Living-off-the-Land Detection

Hunt for abuse of legitimate system tools and commands.

Commonly Abused Tools:

  • PowerShell and Windows Management Instrumentation (WMI)
  • PsExec and other Sysinternals tools
  • Certutil for file downloads
  • BITSAdmin for data transfers
  • Regsvr32 for code execution

10. Anomaly-Focused Hunting

Investigate unusual patterns or outliers that don't fit expected behavior.

Anomaly Categories:

  • Temporal anomalies (after-hours activity)
  • Geographic anomalies (access from unusual locations)
  • Behavioral anomalies (user acting outside normal patterns)
  • Contextual anomalies (inappropriate tool usage for role)
  • Statistical anomalies (significant deviations from baselines)
Technique Best For Skill Level Required
IOC Searching Known threats Beginner
Stack Counting Finding outliers Intermediate
Baseline Analysis Behavioral anomalies Intermediate
TTP Hunting Sophisticated threats Advanced
Timeline Analysis Attack chain reconstruction Advanced

Critical Threat Hunting Tools

Effective threat hunting requires an integrated toolset providing visibility, analysis capabilities, and investigation workflows:

1. SIEM Platforms

Central repository for log data enabling hunting queries across the environment.

Leading Solutions: Splunk, Microsoft Sentinel, Elastic Security, IBM QRadar, Chronicle

Hunting Capabilities:

  • Search Processing Language (SPL) or Kusto Query Language (KQL)
  • Long-term data retention for historical analysis
  • Dashboard creation for hunt findings
  • Alert rule development from discoveries

2. Endpoint Detection and Response (EDR)

Deep visibility into endpoint activities for hunting host-based threats.

Leading Solutions: CrowdStrike Falcon, Microsoft Defender for Endpoint, SentinelOne, Carbon Black, Cortex XDR

Hunting Capabilities:

  • Real-time and historical endpoint telemetry
  • Process execution chains and relationships
  • File and registry modifications
  • Network connections from endpoints
  • Memory analysis and forensics
  • IOC searching across endpoints

3. Network Traffic Analysis (NTA)

Visibility into network communications for hunting network-based threats.

Leading Solutions: Zeek (Bro), Wireshark, Darktrace, ExtraHop, Moloch/Arkime

Hunting Capabilities:

  • Full packet capture and analysis
  • Network metadata extraction
  • Protocol analysis and decoding
  • Beaconing detection
  • Lateral movement identification
  • Data exfiltration discovery

4. Threat Intelligence Platforms (TIP)

Aggregate and enrich threat intelligence for hunting campaigns.

Leading Solutions: MISP, Anomali, ThreatConnect, Recorded Future, ThreatQuotient

Hunting Capabilities:

  • IOC feed aggregation and management
  • Threat actor TTP documentation
  • Campaign tracking and correlation
  • Intelligence-driven hunt hypotheses
  • Automated IOC searching

5. Data Analysis and Visualization

Tools for analyzing large datasets and identifying patterns.

Common Tools:

  • Jupyter Notebooks: Interactive data analysis with Python
  • ELK Stack: Elasticsearch, Logstash, Kibana for log analysis
  • Apache Spark: Big data processing and analysis
  • Pandas: Python data manipulation library
  • Matplotlib/Seaborn: Data visualization libraries

6. Memory Forensics Tools

Analyze system memory for malware and attacker artifacts.

Common Tools:

  • Volatility: Advanced memory forensics framework
  • Rekall: Memory analysis framework
  • WinDbg: Windows debugger for memory analysis

7. Malware Analysis Tools

Analyze suspicious files and executables discovered during hunts.

Common Tools:

  • IDA Pro / Ghidra: Disassemblers for reverse engineering
  • YARA: Pattern matching tool for malware identification
  • VirusTotal: Multi-engine malware scanning
  • Cuckoo Sandbox: Automated malware analysis

8. Scripting and Automation

Custom scripts for data mining and analysis.

Common Languages and Tools:

  • Python: General-purpose scripting for data analysis
  • PowerShell: Windows system automation and analysis
  • Bash: Linux/Unix system analysis
  • SQL: Database queries for structured data

9. Specialized Hunting Platforms

Purpose-built threat hunting solutions.

Examples:

  • Microsoft Defender Threat Hunting: Integrated hunting in Microsoft 365 Defender
  • Elastic SIEM: Open-source security analytics
  • Falcon X: CrowdStrike's threat hunting interface

Building a Threat Hunting Program

Organizations can establish effective threat hunting programs by following a structured approach:

Phase 1: Assessment and Planning (1-2 Months)

Activities:

  • Assess current security capabilities and maturity
  • Define threat hunting program objectives
  • Identify available resources (people, budget, technology)
  • Determine initial scope and focus areas
  • Secure executive support and budget
  • Develop program charter and roadmap

Phase 2: Foundation Building (2-4 Months)

People:

  • Hire or identify threat hunters from existing security team
  • Provide initial training on hunting techniques
  • Define roles and responsibilities
  • Establish reporting structure (usually within SOC or security operations)

Technology:

  • Ensure adequate logging and data collection
  • Deploy or enhance SIEM platform
  • Implement EDR across endpoints
  • Establish threat intelligence feeds
  • Set up hunting workstations and tools

Process:

  • Document hunting methodology
  • Create initial hunting playbooks
  • Establish metrics and reporting templates
  • Define escalation and response procedures

Phase 3: Initial Hunts (Months 3-6)

Activities:

  • Conduct first hunting campaigns (start quarterly)
  • Focus on specific, well-defined hypotheses
  • Document findings and learnings
  • Create automated detections from discoveries
  • Refine processes based on experience

Phase 4: Maturation (Months 6-12)

Expansion Activities:

  • Increase hunting frequency (quarterly → monthly)
  • Expand coverage across additional systems and data sources
  • Develop more sophisticated hunting techniques
  • Enhance threat intelligence integration
  • Build playbook library
  • Implement hunting automation

Phase 5: Optimization (Year 2+)

Advanced Capabilities:

  • Continuous or weekly hunting operations
  • Advanced analytics and machine learning
  • Hypothesis-driven hunting based on intelligence
  • Proactive threat actor tracking
  • Integration with broader security program
  • Contribution to security community

Key Success Factors

1. Executive Support

  • Secure budget and resources
  • Communicate value through metrics and case studies
  • Regular briefings on findings and impact

2. Data Quality and Visibility

  • Comprehensive logging across environment
  • Sufficient data retention (90+ days minimum)
  • Fast query performance for analysis
  • Integration of diverse data sources

3. Skilled Personnel

  • Hire experienced hunters or develop internal talent
  • Provide ongoing training and development
  • Foster collaboration and knowledge sharing
  • Retention through challenging work and career growth

4. Integration with SOC

  • Seamless escalation for confirmed threats
  • Feedback loop from SOC alerts to hunting hypotheses
  • Shared tools and technologies
  • Collaboration on detection engineering

5. Continuous Improvement

  • Regular program reviews and adjustments
  • Lessons learned from each hunt
  • Metrics-driven optimization
  • Stay current with evolving threat landscape
Program Phase Timeline Key Milestones
Assessment & Planning 1-2 months Program charter, executive buy-in
Foundation Building 2-4 months Team, tools, initial processes
Initial Hunts 3-6 months First campaigns, findings
Maturation 6-12 months Regular cadence, expanded coverage
Optimization 12+ months Advanced techniques, continuous hunting

Jumpstart Your Threat Hunting Program

subrosa provides expert threat hunting services and can help establish your internal threat hunting capabilities with training, tools, and guidance.

Contact Our Threat Hunting Team

Talk to a SubRosa security engineer

Get a straight answer on where your defenses actually stand. No pitch, no obligation.

Book a consultation

Skills and Qualifications for Threat Hunters

Effective threat hunters possess a unique combination of technical skills, analytical abilities, and security expertise:

Core Technical Skills

1. Network Security and Protocols

  • TCP/IP networking fundamentals
  • Common protocols (HTTP, DNS, SMB, RDP, SSH)
  • Network traffic analysis and packet inspection
  • Firewall and IDS/IPS operation
  • VPN and remote access technologies

2. Operating Systems Internals

  • Windows internals (processes, services, registry, event logs)
  • Linux/Unix system administration and forensics
  • macOS security architecture
  • System hardening and security configurations
  • Authentication and authorization mechanisms

3. Endpoint Security and Forensics

  • EDR platform operation and analysis
  • Process behavior analysis
  • File system forensics
  • Memory forensics and dump analysis
  • Artifact collection and evidence handling

4. Log Analysis and SIEM

  • SIEM platform operation (Splunk, Sentinel, Elastic)
  • Query languages (SPL, KQL, SQL)
  • Log parsing and normalization
  • Correlation rule development
  • Dashboard and visualization creation

5. Scripting and Automation

  • Python for data analysis and automation
  • PowerShell for Windows analysis
  • Bash scripting for Linux investigation
  • Regular expressions for pattern matching
  • API integration and data collection

Security Domain Knowledge

1. Attacker Tactics, Techniques, and Procedures

  • MITRE ATT&CK framework comprehensive knowledge
  • Understanding of common attack patterns
  • APT group tactics and campaigns
  • Ransomware behaviors and indicators
  • Insider threat methodologies

2. Malware Analysis

  • Static and dynamic malware analysis
  • Understanding of malware families
  • Indicator extraction and creation
  • Basic reverse engineering skills
  • Sandbox and detonation analysis

3. Threat Intelligence

  • Intelligence collection and analysis
  • IOC validation and enrichment
  • Threat actor profiling
  • Intelligence platform operation
  • STIX/TAXII understanding

4. Incident Response

  • IR methodologies (NIST, SANS)
  • Containment and eradication strategies
  • Evidence collection and chain of custody
  • Root cause analysis
  • Post-incident reporting

Analytical and Soft Skills

Critical Thinking and Problem-Solving

  • Hypothesis formulation and testing
  • Pattern recognition and anomaly identification
  • Complex problem decomposition
  • Creative investigation approaches
  • Attention to detail

Communication Skills

  • Technical writing and documentation
  • Presentation skills for stakeholders
  • Collaborative teamwork
  • Clear escalation communication
  • Findings translation for non-technical audiences

Continuous Learning Mindset

  • Staying current with emerging threats
  • Learning new tools and techniques
  • Participating in security community
  • Reading research and threat reports
  • Experimenting with new approaches
Certification Focus Area Value for Hunters
GCIH (GIAC Certified Incident Handler) Incident response IR methodology and tactics
GCFA (GIAC Certified Forensic Analyst) Digital forensics Deep forensic investigation
GCIA (GIAC Certified Intrusion Analyst) Network forensics Network analysis skills
OSCP (Offensive Security Certified Professional) Penetration testing Attacker perspective
SANS FOR508 Advanced forensics Advanced investigation techniques
CCTHP (Certified Cyber Threat Hunting Professional) Threat hunting Specialized hunting knowledge

Building Hunter Skills

For Organizations:

  • Provide training budget and time for development
  • Send hunters to conferences (RSA, Black Hat, SANS)
  • Support certification pursuit
  • Enable hands-on learning through capture-the-flag competitions
  • Cross-train with penetration testing and IR teams

For Aspiring Hunters:

  • Start with SOC analyst role to gain foundational experience
  • Build home lab for hands-on practice
  • Participate in CTF competitions and challenges
  • Follow threat intelligence blogs and reports
  • Contribute to open-source security projects
  • Pursue relevant certifications progressively

Measuring Threat Hunting Effectiveness

Effective threat hunting programs track metrics demonstrating value and identifying improvement opportunities:

Primary Effectiveness Metrics

1. Threats Discovered Per Hunt

  • Number of confirmed threats found
  • Severity distribution of discoveries
  • Threat types identified (malware, insider, APT, etc.)
  • Dwell time reduction compared to industry average

2. Detection Improvements Generated

  • New automated detections created
  • SIEM rules developed from findings
  • EDR policies enhanced
  • Alert quality improvements

3. Coverage Metrics

  • Percentage of MITRE ATT&CK techniques investigated
  • Asset coverage (% of critical assets hunted)
  • Data source utilization
  • Hunt frequency by asset class

4. Time Metrics

  • Mean time from compromise to discovery (hunt-driven)
  • Time spent per hunting campaign
  • Investigation efficiency trends

Secondary Metrics

Program Health Indicators

  • Number of hunts conducted (monthly/quarterly)
  • Hypothesis quality (confirmed vs. refuted)
  • False positive rate of new detections
  • Intelligence integration effectiveness
  • Team skill development and certifications

Business Impact Metrics

  • Prevented data breaches
  • Estimated cost avoidance
  • Compliance demonstration
  • Risk reduction quantification

Reporting Threat Hunting Value

Executive Reporting:

  • High-level threat landscape overview
  • Key discoveries and their business impact
  • Risk reduction achievements
  • Program maturity progress
  • Resource needs and recommendations

Technical Reporting:

  • Detailed findings and TTPs observed
  • Technical recommendations
  • Detection engineering outputs
  • Intelligence developed
  • Methodology and tools used
Metric Category Example KPIs Target/Benchmark
Threat Discovery Threats found per hunt 2-5 per campaign (maturity dependent)
Detection Engineering New rules created 3-10 per hunt
Coverage ATT&CK technique coverage 80%+ of relevant techniques
Efficiency Investigation time Decreasing trend over time
Hunt Frequency Campaigns per quarter 4+ for mature programs

Common Threat Hunting Scenarios

Practical hunting scenarios illustrate how hunters discover real threats:

Scenario 1: PowerShell Empire Detection

Hypothesis: "Attackers are using PowerShell-based post-exploitation frameworks for lateral movement and command execution."

Investigation:

  1. Query EDR logs for PowerShell executions with suspicious characteristics:
    • Base64-encoded command lines
    • Download cradles (IEX, Net.WebClient)
    • Unusual parent processes
    • Executions from unexpected locations
  2. Stack count PowerShell arguments to find rare/unique patterns
  3. Analyze network connections from PowerShell processes
  4. Investigate systems with highest PowerShell activity

Potential Findings:

  • Identify PowerShell Empire agent on compromised systems
  • Discover C2 communication channels
  • Map lateral movement path through network
  • Identify compromised credentials used

Scenario 2: DNS Tunneling Exfiltration

Hypothesis: "Data is being exfiltrated through DNS tunneling to bypass network monitoring."

Investigation:

  1. Analyze DNS query logs for anomalies:
    • Unusually long domain names
    • High volume of queries from single hosts
    • Requests to suspicious TLDs
    • Encoded data patterns in subdomains
  2. Baseline normal DNS behavior per host
  3. Investigate outliers with statistical analysis
  4. Correlate with network traffic and endpoint activity

Potential Findings:

  • Discover malware using DNS for C2 or exfiltration
  • Identify compromised systems and data at risk
  • Create detection rules for DNS tunneling patterns
  • Implement DNS security controls

Scenario 3: Credential Theft and Pass-the-Hash

Hypothesis: "Attackers compromised credentials and are using pass-the-hash for lateral movement."

Investigation:

  1. Review authentication logs for anomalies:
    • Unusual authentication patterns
    • Same credentials used across many systems
    • Privileged account usage from unexpected hosts
    • NTLM authentication from rare sources
  2. Analyze Windows security event logs (4624, 4672, 4768)
  3. Investigate process execution following authentications
  4. Map credential usage across the network

Potential Findings:

  • Identify stolen credentials in use
  • Discover lateral movement paths
  • Determine initial compromise point
  • Find additional compromised accounts

Scenario 4: Insider Threat Data Access

Hypothesis: "An insider is accessing sensitive data outside their job responsibilities or normal patterns."

Investigation:

  1. Establish baseline access patterns for users
  2. Identify deviations from normal behavior:
    • Access to unusual file shares or databases
    • Large data downloads or exports
    • After-hours or weekend access
    • Access to data outside job function
  3. Analyze DLP alerts and file access logs
  4. Correlate with HR data (terminations, performance issues)

Potential Findings:

  • Discover unauthorized data access
  • Identify potential data theft
  • Enable timely intervention
  • Strengthen access controls

Conclusion: The Essential Role of Threat Hunting

Threat hunting has evolved from a nice-to-have capability to an essential component of comprehensive cybersecurity programs. As adversaries employ increasingly sophisticated techniques specifically designed to evade automated detection systems, organizations cannot rely solely on reactive security approaches. The average dwell time of 204 days demonstrates that traditional defenses often fail to detect sophisticated intrusions, patient adversaries spend months or years quietly gathering intelligence, moving laterally, and preparing for their ultimate objectives.

Proactive threat hunting addresses this detection gap by assuming that defenses have been breached and actively searching for evidence of adversary presence. Skilled hunters leverage threat intelligence, behavioral analytics, forensic techniques, and deep system knowledge to discover hidden threats that automated tools miss. This proactive approach reduces dwell time by up to 75%, detecting intrusions in days or weeks rather than months.

Beyond immediate threat discovery, hunting creates lasting security improvements. Each campaign produces automated detections, identifies monitoring gaps, discovers misconfigurations, builds organizational threat intelligence, and develops team expertise. These compounding benefits make threat hunting one of the highest-value security investments organizations can make.

Organizations should start threat hunting programs by establishing realistic maturity goals (Level 2 Procedural for most), securing executive support, building foundational capabilities (people, technology, process), and conducting initial quarterly campaigns. As programs mature, increase frequency, expand coverage, develop advanced techniques, and integrate threat intelligence more deeply.

Whether implementing internal capabilities or leveraging managed hunting services, the key is to begin proactively searching for threats rather than waiting for alerts that may never come. The adversaries are already hunting your organization, it's time to hunt them back.

subrosa's threat hunting team combines expert hunters, advanced analytics, and proven methodologies to discover hidden threats in your environment. Our hunters proactively search for sophisticated adversaries, reduce dwell time, and create lasting security improvements through automated detections and strategic recommendations.

Start Hunting Threats Today

Don't wait for sophisticated threats to announce themselves. subrosa's expert threat hunters proactively discover hidden adversaries before they can cause damage.

Schedule a Threat Hunting Consultation

Frequently Asked Questions

What is threat hunting in cybersecurity?
Threat hunting is the proactive process of iteratively searching through networks, endpoints, and datasets to detect advanced threats that evade existing security solutions. Unlike reactive approaches waiting for alerts, threat hunters actively search for indicators of compromise, anomalous behaviors, and signs of attacker activity using hypotheses, threat intelligence, and analytics. Hunters assume that sophisticated adversaries have already breached defenses and search for evidence of their presence before significant damage occurs.
How is threat hunting different from SOC monitoring?
SOC monitoring is primarily reactive, responding to alerts generated by security tools based on known threat signatures and rules. Threat hunting is proactive, actively searching for unknown and sophisticated threats that automated systems miss. While SOC analysts wait for alerts and investigate when triggered, threat hunters assume breach and look for hidden threats using hypotheses and analytics. Both are complementary: SOC provides baseline automated detection while threat hunting finds what those systems miss. The best security programs implement both.
What skills do threat hunters need?
Effective threat hunters need deep understanding of attacker tactics (especially MITRE ATT&CK framework), network and endpoint forensics expertise, advanced log analysis skills, knowledge of operating systems and protocols, scripting abilities (Python, PowerShell), understanding of malware behaviors and analysis techniques, analytical thinking and pattern recognition, threat intelligence analysis capabilities, and experience with security tools like SIEM, EDR, and network analysis platforms. Strong communication skills for documenting findings and hypothesis development abilities are also critical.
What tools are used for threat hunting?
Core threat hunting tools include SIEM platforms (Splunk, Microsoft Sentinel, Elastic) for log analysis and queries, EDR/XDR solutions (CrowdStrike, Microsoft Defender, SentinelOne) for endpoint visibility, network traffic analysis tools (Wireshark, Zeek/Bro, Moloch), threat intelligence platforms (MISP, Anomali, ThreatConnect), query languages (Kusto, SPL, SQL), data analysis tools (Jupyter, Pandas, Elasticsearch), memory forensics tools (Volatility), YARA for pattern matching, Sysinternals for Windows analysis, and custom scripts for data mining and investigation.
How often should threat hunting be performed?
Mature security programs conduct threat hunting continuously or at least weekly with dedicated hunters. Organizations should aim for quarterly structured hunting campaigns at minimum, with monthly being a good intermediate goal. Frequency depends on threat landscape, industry risk, available resources, and organizational size. High-value targets or highly regulated industries (finance, healthcare, critical infrastructure) should hunt more frequently, potentially daily. Start with quarterly campaigns and increase frequency as capabilities, tools, and team expertise mature.
What is the threat hunting methodology?
Common threat hunting methodology includes: 1) Hypothesis creation based on intelligence, experience, or anomalies, 2) Investigation planning to determine required data and tools, 3) Data collection from relevant sources (logs, telemetry, traffic), 4) Analysis and investigation using queries, analytics, and forensics, 5) Pattern identification and discovery of threats or confirmation of security, 6) Response and remediation for confirmed threats, 7) Automation through creating detection rules from findings, and 8) Documentation of process, findings, and recommendations for continuous improvement.
Can threat hunting prevent zero-day attacks?
While threat hunting cannot prevent zero-day attacks from initially occurring, it can detect them significantly faster than signature-based tools which have no signatures for unknown exploits. Hunters look for behavioral patterns, anomalies, and tactics consistent with attack techniques rather than specific malware signatures. This approach enables detection of novel attacks, zero-day exploits, and custom malware that completely evade traditional security controls. Hunting reduces dwell time even for the most sophisticated zero-day campaigns.
What is hypothesis-driven threat hunting?
Hypothesis-driven hunting starts with a specific, testable theory about how adversaries might compromise your environment rather than random searching. Hunters create hypotheses like "Attackers are using PowerShell for lateral movement" or "Credentials are being exfiltrated via DNS tunneling" based on threat intelligence, security gaps, or experience. They then systematically search for evidence supporting or refuting the hypothesis. This focused approach makes hunting more efficient and effective than unfocused data exploration, producing actionable results faster.
How do you measure threat hunting effectiveness?
Key threat hunting metrics include number of hunts conducted per period, threats discovered per hunt (with severity breakdown), time to detection improvement (reduced dwell time), coverage of MITRE ATT&CK techniques investigated, automated detections created from findings, false positive rate of new detections, hunter productivity and efficiency trends, mean time from compromise to discovery, asset coverage percentages, and organizational risk reduction. Track both quantitative metrics (threats found, detections created) and qualitative improvements (security gaps identified, team expertise developed).
What is the difference between threat hunting and threat intelligence?
Threat intelligence is the collection, analysis, and dissemination of information about threats, adversaries, their tactics, and campaigns, it answers "who, what, how, and why" about threats. Threat hunting is the proactive application of that intelligence (and other techniques) to search for active threats in your specific environment, it answers "are we compromised?" Intelligence provides the knowledge; hunting uses that knowledge to find actual threats. They are highly complementary: intelligence informs hunting hypotheses while hunting discoveries enrich organizational intelligence. Both are essential for mature security programs.
Do small organizations need threat hunting?
While large enterprises with dedicated security teams can build robust threat hunting programs, small organizations still benefit from hunting but should scale appropriately. Small organizations can start with quarterly hunts focused on highest-risk areas, leverage managed hunting services to access expertise without hiring full teams, implement simpler hunting techniques using existing tools, focus on crown jewel asset protection, or integrate basic hunting into SOC analyst duties. Even quarterly hypothesis-driven hunts provide significant security value above reactive-only approaches.
What data do you need for threat hunting?
Essential threat hunting data includes endpoint telemetry (process execution, file modifications, registry changes, network connections), network traffic data (flows, full packets, or metadata), authentication and directory services logs, DNS query logs, SIEM aggregated security events, firewall and proxy logs, cloud platform logs (AWS CloudTrail, Azure logs), application logs from critical systems, threat intelligence feeds, and vulnerability scan data. Data should be retained for 90+ days minimum (180+ days preferred) to enable historical analysis. More comprehensive data coverage enables more effective hunting.
How long does a threat hunting campaign take?
Threat hunting campaign duration varies by scope and hypothesis complexity. Simple hypothesis-driven hunts may take 1-3 days, focused hunts on specific systems or techniques typically take 3-7 days, comprehensive environment-wide campaigns may take 2-4 weeks, and targeted APT hunts based on specific intelligence can take weeks to months. Initial hunts often take longer as teams establish baselines and develop techniques. Experienced hunters working with good data and tools become more efficient, conducting multiple focused hunts weekly or even daily.
Should threat hunting be done internally or outsourced?
The decision depends on resources, expertise, and requirements. Internal hunting provides deep organizational knowledge, continuous availability, and builds internal capabilities but requires significant investment in personnel, training, and tools. Managed hunting services (like those from subrosa) offer immediate access to expert hunters, proven methodologies, advanced tools, and cost-effectiveness but less organizational familiarity. Many organizations use hybrid approaches: managed services for regular comprehensive hunts while building internal capabilities, or internal hunting augmented by external expertise for specialized campaigns. Both can be effective depending on organizational context.
What is the MITRE ATT&CK framework's role in threat hunting?
MITRE ATT&CK provides a comprehensive knowledge base of adversary tactics and techniques that serves multiple hunting purposes: as a framework for developing hunting hypotheses based on specific techniques, for mapping detection coverage and identifying gaps, as common language for communicating findings, for intelligence-driven hunting based on threat actor TTPs, and for organizing hunting playbooks by technique. Mature hunting programs systematically hunt across ATT&CK techniques, tracking coverage metrics (e.g., "we've investigated 80% of relevant ATT&CK techniques"). The framework transforms hunting from random searches to systematic, coverage-focused campaigns.