Hunting-Queries-Detection-Rules

KQL Sentinel & Defender queries

██   ██  ██████  ██                                                                                     
██  ██  ██    ██ ██                                                                                     
█████   ██    ██ ██                                                                                     
██  ██  ██ ▄▄ ██ ██                                                                                     
██   ██  ██████  ███████                                                                                
            ▀▀                                                                                          
                                                                                                        
█  ██████  ██████  ██ ███    ██ ████████   ██  ██     ██ ███████ ██       ██████  ██████  ███    ███ ███████ ██
█  ██   ██ ██   ██ ██ ████   ██    ██          ██     ██ ██      ██      ██      ██    ██ ████  ████ ██      
█  ██████  ██████  ██ ██ ██  ██    ██          ██  █  ██ █████   ██      ██      ██    ██ ██ ████ ██ █████   
█  ██      ██   ██ ██ ██  ██ ██    ██          ██ ███ ██ ██      ██      ██      ██    ██ ██  ██  ██ ██      
█  ██      ██   ██ ██ ██   ████    ██           ███ ███  ███████ ███████  ██████  ██████  ██      ██ ███████ 

KQL for Defender For Endpoint & Microsoft Sentinel

The purpose of this repository is to share KQL queries that can be used by anyone and are understandable. These queries are intended to increase detection coverage through the logs of Microsoft Security products. Not all suspicious activities generate an alert by default, but many of those activities can be made detectable through the logs. These queries include Detection Rules, Hunting Queries and Visualisations. Anyone is free to use the queries. If you have any questions feel free to reach out to me on Twitter @BertJanCyber.

Presenting this material as your own is illegal and forbidden. A reference to Twitter @BertJanCyber or Github @Bert-JanP is much appreciated when sharing or using the content.

KQL Blogs

More detailed KQL information can be found on my blog page: https://kqlquery.com. Some KQL related blogs:

• KQL Functions For Security Operations
• KQL Functions For Network Operations
• Incident Response Part 1: IR on Microsoft Security Incidents (KQL edition)
• Incident Response Part 2: What about the other logs?
• From Threat Report to (KQL) Hunting Query
• Prioritize Vulnerabilities Using The CISA Known Exploited Vulnerabilities Catalog
• KQL Security Sources - 2024 Update
• Detecting Post-Exploitation Behaviour
• Investigating Microsoft Graph Activity Logs
• Audit Defender XDR Activities
• Use Cases For Sentinel Summary Rules
• Unleash The Power Of DeviceTvmInfoGathering

For Sentinel Automations see the Repository Sentinel-Automation.

KQL Categories

The queries in this repository are split into different categories. The MITRE ATT&CK category contains a list of queries mapped to the tactics of the MITRE Framework. The product section contains queries specific to Microsoft security products. The Processes section contains several queries that can be used in common cyber processes to make things easier for security analysts. In addition, there is a special category for Zero Day detections. Lastly, there is an informational section that explains the use of KQL using examples.

MITRE ATT&CK

• MITRE ATT&CK Mapping

Products

• Defender For Endpoint detection rules
• Defender For Identity detection rules
• Defender For Cloud Apps detection rules
• Defender For Office 365
• Defender XDR
• Azure Active Directory
• Microsoft Sentinel
• MISP
• Windows Security Events
• Graph API
• Windows Security Events

Security Processes

• Digital Forensics and Incident Response
• Threat Hunting
• Full Threat Hunting Cases
• Vulnerability Management

Informational

• KQL helpful functions
• KQL Regex Example List
• Azure Resource Graph

Contributions

Everyone can submit contributions to this repository via a Pull Request. If you want to contribute the Detection Template needs to be used. Besides that the query needs to be able to run and be readable. To give credit where credit is due the top contributors are listed in the Top Contributors section.

Top contributors

Name	Queries added	GitHub	Twitter	Query Links
Gavin Knapp	10	@m4nbat	@knappresearchlb	NetSupport running from unexpected directory (FIN7)
				Abusing PowerShell to disable Defender components
				Suspicious network connection from MSBuild
				PowerShell Encoded Command
				PowerShell Launching Scripts From WindowsApps Directory (FIN7)
				Azure ARC Related Persistence Detection
				Scattered Spider Defense Evasion via Conditional Access Policies Detection
				Check for Phishing Emails Using IPFS in Phishing Campaigns
				Kerberos attacks
				PowerShell Creating LNK Files within a Startup Directory Detection
				Ransomware Leaksite Monitoring
Alex Teixeira	4	@inodee	@ateixei	Rare_Outgoing_IPv4_Connections
				Detect Known RAT RMM Process Patterns
				NTDS.DIT File Modifications
				Custom Detection Report
Babak Mahmoodizadeh	2	@babakmhz	@Babakmhz	WebShell Detection
				List AD Delegations
Deepak Kumar Ray	1		@roydeepakku	CEF MultiSource IP
Guy Sukerman	1	@guys1444		Anomalous Amount of URLClickEvents
ch4meleon	1	-		PowerShell Executions From Clipboard

Detection Template

The Detection Template can be used to standardize the detections in your own repository. This could help others to easily parse the content of the repository to collect the query and the metadata. The following repositories have already been standardized in this manner:

• https://github.com/alexverboon/Hunting-Queries-Detection-Rules - By Alex Verboon
• https://github.com/KustoKing/Hunting-Queries-Detection-Rules - By Gianni Castaldi
• https://github.com/SlimKQL/Hunting-Queries-Detection-Rules - By Steven Lim
• https://github.com/SecurityAura/DE-TH-Aura - By SecurityAura
• https://github.com/m4nbat/KustQueryLanguage_kql - By m4nbat

If your repository is not yet listed, feel free to create a pull request (PR) or reach out via message to have it added.

Where to use KQL in Defender For Endpoint & Sentinel?

Defender XDR

• Open security.microsoft.com
• Hunting
• Advanced Hunting

Sentinel

• Open portal.azure.com
• Search for Sentinel
• Open Sentinel
• Logs

KQL Defender For Endpoint vs Sentinel

KQL queries can be used in both Defender For Endpoint and Azure Sentinel. The syntax is almost the same. The main difference is the field that indicates the time. It must be adjusted according to the product used. In Sentinel, the ‘TimeGenerated’ field is used. In DFE it is ‘Timestamp’. The queries below show both in DFE and in Azure Sentinel 10 DeviceEvents of the last 7 days.

Quickstart Defender For Endpoint

DeviceEvents
| where Timestamp > ago(7d)
| take 10

Quickstart Azure Sentinel

DeviceEvents
| where TimeGenerated > ago(7d)
| take 10

KQL Sources

Documentation

Link	Description
KQL Quick Reference Guide	KQL Quick Reference Guide
KQL Tutorial	KQL Tutorial
KQL Cheat Sheet PDF	KQL Cheat Sheet

Respostiories

The community respostiories are available here

Other

Link	Description
kqlsearch.com	KQL Search Engine
Kusto Insights Newsletter	Kusto Insights newsletter
The Definitive Guide to KQL	Using Kusto Query Language for Operations, Defending, and Threat Hunting
Kusto Query Internals	Hunting TTPs with Azure Sentinel
Microsoft Sentinel Analytics Rules	Microsoft Sentinel Analytics Rules
KQL Internals	Kusto Query Internals: Hunting TTPs with Azure Sentinel
Advanced Hunting Expert Training	Advanced Hunting Expert Training