Microsoft Defender XDR Incidents
The Microsoft Defender XDR Incidents Input retrieves incidents formed based on the alerts generated by the services and applications that comes under Microsoft's unified Extended Detection and Response (XDR) platform.
Sync Type: Incremental
The input collects incidents by their last-update time, so an incident is collected again each time it is updated. Without a Backfill Start Time, the first sync starts from now and collects no earlier incidents.
Overview
Services and apps within the Microsoft Defender XDR suite create alerts when they detect a suspicious or malicious event or activity. Because piecing the individual alerts together to gain insight into an attack can be challenging and time-consuming, Microsoft Defender XDR automatically aggregates the alerts and their associated information into an incident. This input connects to the Microsoft Graph Security API to fetch a list of incidents.
Supported Security Services
The input retrieves incidents formed based on the alerts generated from the following Microsoft Defender services:
- Microsoft Defender for Endpoint - Endpoint detection and response alerts from workstations, servers, and mobile devices
- Microsoft Defender for Cloud - Cloud security posture management and threat protection alerts from Azure, AWS, and GCP resources
- Microsoft Defender for Identity - Identity-based threats and suspicious activities targeting Active Directory environments
- Microsoft Defender for Office 365 - Email and collaboration threats including phishing, malware, and safe attachments/links
- Microsoft Defender for Cloud Apps - Cloud application security alerts and anomalous user behavior detection
Prerequisites
- Register a new Application in App Registrations in the Microsoft Entra admin center.
- Give the application the Microsoft Graph Application permission
SecurityIncident.Read.All, and grant admin consent.
Setting up a new application for API Access
- Registering a new application
- Open the App Registration page in the Azure Entra ID portal.
- Select New Registration.
- Add a name to the new registration.
- Click Register.
- Save the applications
Application (client) IDandDirectory (tenant) ID. - Select Certificates and Secrets.
- Click link next to Client credentials.
- In "Client secrets" click "New client secret".
- Add a name and expiration to the new secret.
- Save the client secret value.
- Give application access to Microsoft Graph API
- Click "API Permissions" on left sidebar.
- Click "Add Permission".
- Select "Microsoft Graph API".
- Select "Application permissions", then select
SecurityIncident.Read.All.
- On the API permission page, click on "Grant admin consent for Default Directory".
Configuration
Settings
| Setting | Type | Required | Default | Description |
|---|---|---|---|---|
tenant_id | string | Yes | - | The tenant ID of the Entra ID directory associated with your Azure subscription. |
interval | int | Yes | 10 | Time (in seconds) to check for new alerts |
use_synthetic_data | bool | No | false | Generate synthetic data for testing, instead of connecting to a real data source. Defaults to an hourly cron schedule for cron-based inputs. |
backfill_start_time | date | No | - | The date to start fetching data from. If not specified, no past records will be fetched. |
Secrets
| Secret | Type | Required | Description |
|---|---|---|---|
client_id | secret | Yes | The client ID of the Entra ID application |
client_secret | secret | Yes | The client secret of the Entra ID application |
Related Articles
Sample Record
Code
Sync frequency
This input polls on a connector-specific interval. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.