Explore creation and management of Azure Sentinel threat-hunting queries
Azure Sentinel contains powerful query tools that can help you, as part of the Security Operations Center team, find and isolate security threats and unwanted activity in Contoso's environment.
Hunt by using built-in queries
You can use the search and query tools in Azure Sentinel to hunt for security threats and tactics throughout your environment. Hunting queries enable you to filter through large amounts of events and security data sources to identify potential threats or track down known or expected threats.
The Hunting page in Azure Sentinel has built-in queries. These queries can guide your hunting process and help you pursue the appropriate hunting paths to uncover issues in your environment. Hunting queries can expose issues that aren't significant enough on their own to generate an alert but have happened often enough over time to warrant investigation.
The Hunting page provides a list all hunting queries. You can filter and sort queries by name, provider, data source, results, and tactics. You can save queries by selecting the Favorites star icon for the query in the list.
When a query is selected as a favorite, it runs automatically each time you open the Hunting page.
Manage hunting queries
When you select a query from the list, the query details appear on a new pane. The query details pane contains a description, code, and other information about the query. That information includes related entities and identified tactics. You can run a query interactively by selecting Run Query on the details pane.
Hunt for threats y using the MITRE ATT&CK framework
Azure Sentinel uses the MITRE ATT&CK framework to categorize and order queries by tactics. ATT&CK is a knowledge base of tactics and techniques that are used and observed in the global threat landscape. You can use MITRE ATT&CK to develop and inform your threat-hunting models and methods in Azure Sentinel. When you're threat hunting in Azure Sentinel, you can use the ATT&CK framework to categorize and run queries by using the MITRE ATT&CK tactics timeline.
You can select individual MITRE ATT&CK tactics from the timeline on the Hunting page.
Selecting any tactic will filter the available queries by the selected tactic. Tactics include:
- Initial access. Tactics that the adversary uses to gain entry to a network, by exploiting vulnerabilities or configuration weaknesses in public-facing systems. An example is targeted spear-phishing.
- Execution. Tactics that result in an adversary running their code on a target system. For example, a malicious hacker might run a PowerShell script to download more attacker tools and/or scan other systems.
- Persistence. Tactics that allow an adversary to maintain access to a target system, even after restarts and credential changes. An example of a persistence technique is an attacker who creates a scheduled task that runs their code at a specific time or on restart.
- Privilege escalation. Tactics that an adversary uses to gain higher-level privileges on a system, such as local administrator or root.
- Defense evasion. Tactics that attackers use to avoid detection. Evasion tactics include hiding malicious code within trusted processes and folders, encrypting or obfuscating adversary code, or disabling security software.
- Credential access. Tactics deployed on systems and networks to steal usernames and credentials for reuse.
- Discovery. Tactics that adversaries use to obtain information about systems and networks that they want to exploit or use for their tactical advantage.
- Lateral movement. Tactics that allow an attacker to move from one system to another within a network. Common techniques include pass-the-hash methods of authenticating users and abuse of the Remote Desktop Protocol.
- Collection. Tactics that an adversary uses to gather and consolidate the information they were targeting as part of their objectives.
- Command and control. Tactics that an attacker uses to communicate with a system under their control. One example is an attacker communicating with a system over an uncommon or high-numbered port to evade detection by security appliances or proxies.
- Exfiltration. Tactics used to move data from the compromised network to a system or network that's fully under control of the attacker.
- Impact. Tactics that an attacker uses to affect the availability of systems, networks, and data. Methods in this category include denial-of-service attacks and disk-wiping or data-wiping software.
Create custom queries to refine threat hunting
All Azure Sentinel hunting queries use Kusto Query Language (KQL) syntax used in Log Analytics. You can modify a query in the details pane and run the new query. Or you can save it as a new query that can be reused in your Azure Sentinel workspace.
You can also create your own custom queries by using KQL code to hunt for threats.
Custom queries enable you to define the following:
|Name||Provide a name for the custom query.|
|Description||Provide a description of your query's functionality.|
|Entity mapping||Map entity types to columns from your query result to populate your query results with more actionable information. You can also map entities by using code in your KQL query.|
|Tactics||Specify the tactics that your query is designed to expose.|
Custom queries are listed alongside built-in queries for management.
Explore the Azure Sentinel repository on GitHub
The Azure Sentinel repository contains out-of-the-box detections, exploration queries, hunting queries, workbooks, playbooks, and much more to help you secure your environment and hunt for threats. Microsoft and the Azure Sentinel community contribute to this repo.
The repo contains folders with contributed content for several areas of Azure Sentinel functionality, including hunting queries. You can use the code from these queries to create custom queries in your Azure Sentinel workspace.
Choose the best response for the following question. Then select Check your answers.