Loading

Microsoft Defender for Endpoint integration

Version 2.38.0 (View all)
Compatible Kibana version(s) 8.18.0 or higher
9.0.0 or higher
Supported Serverless project types
What's this?
Security
Observability
Subscription level
What's this?
Basic
Level of support
What's this?
Elastic

This integration is for Microsoft Defender for Endpoint logs.

Microsoft Defender for Endpoint integration collects data for Alert, Machine, Machine Action, and Vulnerability logs using REST API.

This integration collects the following logs:

  • Alert - Retrieves alerts generated by Microsoft Defender for Endpoint.
  • Machine - Retrieves machines that have communicated with Microsoft Defender for Endpoint.
  • Machine Action - Retrieves logs of actions carried out on machines.
  • Vulnerability - Retrieves logs of Vulnerability.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

To allow the integration to ingest data from the Microsoft Defender API, you need to create a new application on your Azure domain. The procedure to create an application is found on the Create a new Azure Application documentation page.

When the application is granted the API permissions listed in the table below, it will receive only the necessary access to collect logs nothing more within the Azure domain.

Data stream API Permissions
Alert Alert.Read.All
Machine Machine.Read.All
Machine Action Machine.Read.All
Vulnerability Vulnerability.Read.All, Machine.Read.All

After the application has been created, it should contain 3 values that you need to apply to the module configuration.

These values are:

  • Client ID
  • Client Secret
  • Tenant ID
  1. In Kibana navigate to Management > Integrations.
  2. In the search bar, type Microsoft Defender for Endpoint.
  3. Select the Microsoft Defender for Endpoint integration and add it.
  4. Add all the required integration configuration parameters, including the Client ID, Client Secret, Tenant ID to enable data collection.
  5. Select "Save and continue" to save the integration.

A full sync pulls in a large volume of data, which can lead to storage issues or index overflow over time. To avoid this, we’ve set up an Index Lifecycle Management (ILM) policy that automatically deletes data older than 7 days. This helps keep storage usage under control.

Note

The user or service account associated with the integration must have the following index privileges on the relevant index have the following permissions delete, delete_index

Defender for Endpoint fields ECS Fields
alertCreationTime @timestamp
aadTenantId cloud.account.id
category threat.technique.name
computerDnsName host.hostname
description rule.description
detectionSource observer.name
evidence.fileName file.name
evidence.filePath file.path
evidence.processId process.pid
evidence.processCommandLine process.command_line
evidence.processCreationTime process.start
evidence.parentProcessId process.parent.pid
evidence.parentProcessCreationTime process.parent.start
evidence.sha1 file.hash.sha1
evidence.sha256 file.hash.sha256
evidence.url url.full
firstEventTime event.start
id event.id
lastEventTime event.end
machineId cloud.instance.id
title message
severity event.severity

The values used in event.severity are consistent with Elastic Detection Rules.

Severity Name event.severity
Low (or Informational) 21
Medium 47
High 73
Critical 99

This is the log dataset.

This is the machine dataset.

This is the machine action dataset.

This is the vulnerability dataset.