Threat Hunting enables security teams to proactively investigate endpoint event logs by querying collected data for suspicious or unusual behavior. Administrators can search endpoint event logs using query syntax, identify threats, and create alerts to receive notifications when the same activity recurs in the environment.
Threat Hunting supports two query-building modes: Syntax mode for writing queries directly and Classic mode for building queries through a guided filter interface. Once suspicious activity is identified, administrators can respond in two ways:
When an alert is raised, a corresponding incident is automatically created under the Incidents menu for further investigation.
Syntax mode lets you write query statements directly to search endpoint event logs. Use this mode when you need precise control over search conditions using supported operators and field names.
For complete syntax reference and all supported operators, see Query Syntax Documentation.
Example:
logtype="edrevents"You can chain multiple conditions to refine results further:
logtype="edrevents" AND action="FileCreate" AND filepath CONTAINS "temp"
Classic mode provides a guided filter interface for building queries without writing syntax manually. This mode is ideal for administrators who prefer a visual, point-and-click approach.
When you identify a specific suspicious event in the hunting results, you can immediately raise an alert for it directly from the Hunting Details panel.
An alert is immediately raised for the selected event and a corresponding incident is created under the Incidents menu.

In addition to raising alerts for individual events, you can schedule a recurring alert that automatically runs a query at a set frequency. This is useful for continuously monitoring for specific patterns of activity across all managed endpoints — for example, detecting when a process renames an unusually high number of files within a short time window.
| Field | Description |
|---|---|
| Alert Name | A descriptive name for the alert. Use a name that clearly identifies the threat or activity being monitored. |
| Run Frequency | How often the query runs automatically (for example, every 15 minutes, hourly, or daily). |
| Severity | The severity level assigned to the alert (for example, Low, Medium, High, or Critical). |
| Query | The validated threat hunting query. This field is auto-populated from your current query. |
| Alert When Results | The condition that triggers the alert based on the result count (for example, “greater than 0”). |

Whenever an alert is raised — either directly from the Hunting Details panel or through a scheduled alert — a corresponding incident is automatically created under the Incidents menu. This provides a centralized view for tracking and investigating all suspicious activities detected through threat hunting.
From the Incidents page, each incident displays the following information:
| Column | Description |
|---|---|
| Detection Source | The origin of the detection (for example, Threat Hunting alert). |
| Detected Time | The date and time when the activity was detected. |
| Severity | The severity level inherited from the alert configuration. |
| Alerts | The number of alerts associated with the incident. |
| Infected Devices | The endpoints where the suspicious activity was detected. |
| Incident Status | The current status of the incident (for example, New, In Progress, Resolved). |
| Detection Status | Whether the detection is confirmed, under review, or dismissed. |