Loading

Microsoft Defender for Endpoint integration

<div class="condensed-table">
| | |
| --- | --- |
| Version | 2.27.1 (View all) |
| Compatible Kibana version(s) | 8.13.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 |

</div>
This integration is for Microsoft Defender for Endpoint logs.

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.

Note

When giving the application the API permissions described in the documentation (Windows Defender ATP Alert.Read.All), it will only grant access to read alerts from ATP and nothing else in the Azure Domain

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
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