In information security, threat hunting is the process of proactively searching for threats against computer systems in order to protect them. This is in contrast to traditional threat management measures, such as firewalls, intrusion detection systems (IDS), malware sandbox (computer security) and SIEM systems, which typically involve an investigation of evidence-based data after there has been a warning of a potential threat. Threat analyst Lesley Carhart stated that there is no consensus amongst practitioners what threat hunting actually entails.
Recently, the world has seen a rise in the number and severity of cyber attacks, data breaches, malware infections, and online fraud incidents. According to cybersecurity and AI company SonicWall, the number of ransomware attacks grew by 105% globally. Major corporations around the world have fallen victim to high-profile data breaches, with the average cost of a data breach now estimated at $4.24 million, according to IBM.
Threat hunting has traditionally been a manual process, in which a security analyst sifts through various data information using their own knowledge and familiarity with the network to create hypotheses about potential threats, such as, but not limited to, lateral movement by threat actors. To be even more effective and efficient, however, threat hunting can be partially automated, or machine-assisted, as well. In this case, the analyst uses software that leverages machine learning and user and entity behavior analytics (UEBA) to inform the analyst of potential risks. The analyst then investigates these potential risks, tracking suspicious behavior in the network. Thus, hunting is an iterative process, meaning that it must be continuously carried out in a loop, beginning with a hypothesis.
The analysts research their hypothesis by going through vast amounts of data about the network. The results are then stored so that they can be used to improve the automated portion of the detection system and to serve as a foundation for future hypotheses.
The Detection Maturity Level (DML) model expresses threat indicators can be detected at different semantic levels. High semantic indicators such as goal and strategy or tactics, techniques and procedures (TTPs) are more valuable to identify than low semantic indicators such as network artifacts and atomic indicators such as IP addresses. SIEM tools typically only provide indicators at relatively low semantic levels. There is therefore a need to develop SIEM tools that can provide threat indicators at higher semantic levels.
There are two types of indicators:
The SANS Institute identifies a threat hunting maturity model as follows:
The dwell time either indicates the entire span of a security incident (initial compromise until detection and full cleanup) or the 'mean time to detect' (from initial compromise until detection). According to the 2022 Mandiant M-Trends Report, cyberattackers operate undetected for an average of 21 days (a 79% reduction, compared to 2016), but this varies greatly by region. Per Mandiant, the dwell time can be as low as 17 days (in the Americas) or as high as 48 days (in EMEA). The study also showed that 47% of attacks are discovered only after notification from an external party.
Inside the Network Perimeter
Outside the Network Perimeter
Regulatory frameworks increasingly emphasize proactive threat detection as part of comprehensive security programs. The Health Insurance Portability and Accountability Act (HIPAA) Security Rule requires covered entities to implement procedures for monitoring log-in attempts and reporting discrepancies (45 CFR 164.308(a)(5)(ii)(C)) and to maintain audit controls that record and examine activity in systems containing electronic protected health information (45 CFR 164.312(b)). The December 2024 HIPAA Security Rule NPRM proposed requiring regulated entities to deploy technology capable of detecting and responding to suspicious network activity, including continuous monitoring of information systems for unauthorized access attempts.
NIST Special Publication 800-53 addresses threat hunting through several control families, including SI-4 (System Monitoring), which recommends organizations monitor information systems to detect attacks, indicators of potential attacks, and unauthorized connections, and IR-6 (Incident Reporting), which establishes requirements for reporting suspected security incidents. The NIST Cybersecurity Framework 2.0 Detect function specifically addresses continuous monitoring and anomaly detection as foundational security activities.