Threat hunting

In [[information security]], '''threat hunting''' is the process of proactively searching for [[Threat (computer security)|threats]] against computer systems in order to protect them.<ref>{{Cite web|url=http://www.techrepublic.com/article/cyber-threat-hunting-why-this-active-strategy-gives-analysts-an-edge/|title=Cyber threat hunting: How this vulnerability detection strategy gives analysts an edge - TechRepublic|website=TechRepublic|access-date=2016-06-07}}</ref> This is in contrast to traditional threat management measures, such as [[Firewall (computing)|firewalls]], [[intrusion detection system]]s (IDS), malware [[sandbox (computer security)]] and [[Security information and event management|SIEM]] systems, which typically involve an investigation of evidence-based data ''after'' there has been a warning of a potential threat.<ref>{{Cite web|url=http://techtalk.comodo.com/2020/08/27/comodo-mitre-kill-chain/ |title= MITRE Kill Chain|access-date=2020-08-27}}</ref><ref>{{Cite web|url=https://www.techworm.net/2018/06/threat-intelligence-platform-on-war-against-cybercriminals.html |title=Threat Intelligence Platform on War Against Cybercriminals |date=23 June 2018 |access-date=2019-02-17}}</ref> Threat analyst [[Lesley Carhart]] stated that there is no consensus amongst practitioners what threat hunting actually entails.<ref>{{Cite web |last=Carhart |first=Lesley |author-link=Lesley Carhart |title=OT Threat Hunting: More Critical Than Ever |url=https://www.sans.org/blog/ot-threat-hunting-more-critical-than-ever/ |access-date=2024-11-22 |website=[[SANS Institute]]}}</ref>

== Methodologies ==

=== Overview === 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]].<ref>{{Cite web |title=The Future of Cyber Security and AI: Protecting Your Digital World |url=https://bluebigdata.com/cyber-security/cyber-security-and-ai/ |access-date=October 13, 2023 |website=Blue Big Data|date=23 August 2023 }}</ref>

=== Cyber threat hunting methodologies === 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, [[Network Lateral Movement|lateral movement]] by [[threat actor]]s.<ref>{{Cite web|url=https://medium.com/swlh/cyber-threat-intelligence-cti-in-a-nutshell-1-71a03916fd92 |title= Cyber Threat Intelligence (CTI) in a Nutshell|website=Medium.com|access-date=2020-07-27}}</ref> 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 behavior analytics|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.

* Analytics-Driven: "Machine-learning and UEBA, used to develop aggregated risk scores that can also serve as hunting hypotheses" * Situational-Awareness Driven: "Crown Jewel analysis, enterprise risk assessments, company- or employee-level trends" * Intelligence-Driven: "Threat intelligence reports, threat intelligence feeds, [[malware analysis]], vulnerability scans" 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 <ref>{{Cite web|url=http://ryanstillions.blogspot.no/2014/04/the-dml-model_21.html|title=The DML Model|last=Stillions|first=Ryan|date=2014|website=Ryan Stillions security blog|access-date=}}</ref> expresses threat indicators can be detected at different semantic levels. High semantic indicators such as goal and strategy or [[Terrorist Tactics, Techniques, and Procedures|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.<ref>{{Cite web|url=http://detect-respond.blogspot.com/2013/03/the-pyramid-of-pain.html?m=1|title=The Pyramid of Pain|last=Bianco|first=David|date=2014-01-17|website=detect-respond.blogspot.com|access-date=2023-07-01}}</ref><ref>{{Cite web|title=The Pyramid of Pain|last=Bianco|first=David|url=https://www.sans.org/tools/the-pyramid-of-pain/|publisher=SANS Institute|access-date=2023-07-01}}</ref> 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.<ref>{{Cite web|url=http://folk.uio.no/josang/papers/BJE2016-STIDS.pdf|title=Semantic Cyberthreat Modelling|last=Bromander|first=Siri|date=2016|publisher=Semantic Technology for Intelligence, Defense and Security (STIDS 2016)|access-date=}}</ref>

== Indicators == There are two types of indicators:

# [[Indicator of compromise]] - An indicator of compromise (IOC) tells you that an action has happened and you are in a reactive mode. This type of IOC is done by looking inward at your own data from transaction logs and or SIEM data. Examples of IOC include unusual network traffic, unusual privileged user account activity, login anomalies, increases in database read volumes, suspicious registry or system file changes, unusual DNS requests and [[Web traffic]] showing non-human behavior. These types of unusual activities allow security administration teams to spot malicious actors earlier in the [[cyberattack]] process. # Indicator of Concern - Using [[Open-source intelligence]] (OSINT), data can be collected from publicly available sources to be used for cyberattack detection and threat hunting.

== Tactics, Techniques and Procedures (TTPs) == The SANS Institute identifies a threat hunting maturity model as follows:<ref>{{cite web|last1=Lee|first1=Robert|title=The Who, What, Where, When and How of Effective Threat Hunting|url=https://www.sans.org/reading-room/whitepapers/analyst/who-what-where-when-effective-threat-hunting-36785|website=SANS Institute|accessdate=29 May 2018}}</ref>

* Initial – At Level 0 maturity, an organization relies primarily on automated reporting and does little or no routine [[data collection]]. * Minimal – At Level 1 maturity, an organization incorporates threat intelligence indicator searches. It has a moderate or high level of routine data collection. * Procedural – At Level 2 maturity, an organization follows analysis procedures created by others. It has a high or very high level of routine data collection. * Innovative – At Level 3 maturity, an organization creates new [[data analysis]] procedures. It has a high or very high level of routine data collection. * Leading – At Level 4 maturity, automates the majority of successful data analysis procedures. It has a high or very high level of routine data collection.

==Dwell time== The dwell time either indicates the entire span of a security incident ([[Computer security#Vulnerabilities and attacks|initial compromise]] until [[Computer security incident management|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.<ref name="Mandiant M-Trends Report">{{cite web |orig-date=2022-04-19 |title=Mandian M-Trends 2022 |url=https://www.mandiant.com/media/15671 |url-status=live |archive-url=https://web.archive.org/web/20220513065702/https://www.mandiant.com/media/15671 |archive-date=2022-05-13 |access-date=2022-05-16 |publisher=[[Mandiant]] |pages=7, 9, 12, 16 |format=PDF}}</ref> Per Mandiant, the dwell time<ref>In the Mandiant M-Trends report, dwell time ''"is calculated as the number of days an attacker is present in a victim environment before they are detected"'', which corresponds to the 'mean time to detect'.</ref> can be as low as 17 days (in the [[Americas]]) or as high as 48 days (in [[Europe, the Middle East and Africa|EMEA]]).<ref name="Mandiant M-Trends Report" /> The study also showed that 47% of attacks are discovered only after notification from an external party.

==Example reports== *[https://symantec-enterprise-blogs.security.com/blogs/threat-intelligence/seedworm-espionage-group Seedworm: Group Compromises Government Agencies, Oil & Gas, NGOs, Telecoms, and IT Firms]

==Example threat hunting== * [https://blog.redteam.pl/2019/08/threat-hunting-dns-firewall.html Threat hunting using DNS firewalls and data enrichment]

==Threat hunting methodologies== '''Inside the network perimeter''' * Reactive Threat Hunting - This method is triggered by a malicious event, typically after a data breach or theft is discovered. Efforts are typically focused on forensics and remediation. * Proactive Threat Hunting - This method actively seeks out ongoing malicious events and activities inside the network, the goal is to detect an in progress cyber attack. Efforts are typically focused on detection and remediation.

'''Outside the network perimeter''' * External Threat Hunting - This method proactively seeks out malicious threat actor infrastructure to map and predict where cyber attacks are likely to emerge to prepare defensive strategies. Efforts are typically focused on Cyber Threat Reconnaissance, Threat Surface Mapping and monitoring of third-party risks. In a Team Cymru blog,<ref>{{cite web |url=https://www.team-cymru.com/post/team-cymru-s-threat-hunting-maturity-model-explained |title=Team Cymru's Threat Hunting Maturity Model Explained |website=Team Cymru |date= |access-date=2025-02-14}}</ref> they explain that unlike internal threat hunting, the threat actors themselves are proactively tracked, traced, and monitored as they shift infrastructure and claim victims. [[Indicator of compromise|Indicators of compromise]] (IOCs), typically used to inform of a breach, become signals intelligence beyond the network perimeter.

== Regulatory context == 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)).{{cite web |title=45 CFR § 164.308 - Administrative safeguards |url=https://www.law.cornell.edu/cfr/text/45/part-164/subpart-C |publisher=Legal Information Institute |access-date=April 1, 2026}} The December 2024 HIPAA Security Rule [[Notice of proposed rulemaking|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.{{cite web |title=HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information |url=https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information |publisher=Federal Register |date=January 6, 2025 |access-date=April 1, 2026}}

[[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.{{cite web |title=NIST SP 800-53 Rev. 5: Security and Privacy Controls |url=https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final |publisher=National Institute of Standards and Technology |date=September 2020 |access-date=April 1, 2026}} The [[NIST Cybersecurity Framework]] 2.0 Detect function specifically addresses continuous monitoring and anomaly detection as foundational security activities.{{cite web |title=NIST Cybersecurity Framework 2.0 |url=https://www.nist.gov/cyberframework |publisher=National Institute of Standards and Technology |date=February 2024 |access-date=April 1, 2026}}

== See also == * [[Bug bounty program]] * [[Proactive cyber defense]]

==References== {{reflist}}

[[Category:Computer security procedures]]