New

The executive guide to generative AI

Read more
Loading

Microsoft Defender for Endpoint integration

Version 2.33.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, and Machine Action 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.

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
  • You can install only one Elastic Agent per host.
  • Elastic Agent is required to stream data from the GCP Pub/Sub or REST API and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines.

You have a few options for installing and managing an Elastic Agent:

With this approach, you install Elastic Agent and use Fleet in Kibana to define, configure, and manage your agents in a central location. We recommend using Fleet management because it makes the management and upgrade of your agents considerably easier.

With this approach, you install Elastic Agent and manually configure the agent locally on the system where it is installed. You are responsible for managing and upgrading the agents. This approach is reserved for advanced users only.

You can run Elastic Agent inside a container, either with Fleet Server or standalone. Docker images for all versions of Elastic Agent are available from the Elastic Docker registry and we provide deployment manifests for running on Kubernetes.

There are some minimum requirements for running Elastic Agent and for more information, refer to the link here.

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

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 "Search for integrations" top bar, search for Microsoft Defender for Endpoint.
  3. Select the "Microsoft Defender for Endpoint" integration from the search results.
  4. Select "Add Microsoft Defender for Endpoint" to add the integration.
  5. Add all the required integration configuration parameters, including the Client ID, Client Secret, Tenant ID to enable data collection.
  6. Select "Save and continue" to save the integration.
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

This is the log dataset.

This is the machine dataset.

This is the machine action dataset.