Microsoft Defender Advanced Threat Hunting

About the Device

Advanced hunting is a query-based threat-hunting tool that lets you explore up to 30 days of raw data. You can proactively inspect events in your network to locate threat indicators and entities. The flexible access to data enables unconstrained hunting for both known and potential threats.

You can use the threat-hunting queries to build custom detection rules. These rules run automatically to check for and then respond to suspected breach activity, misconfigured machines, and other findings.

Device Information

Collection Method

Device Configuration

Prerequisites

1. An Azure subscription that you can sign in to.

2. A user who's a Global Administrator or Microsoft Defender Advanced Threat Hunting Administrator 

3. Azure Storage Account to store the logs or an Event Hub to stream the logs. 

4. Log in to your Azure tenant, go to Subscriptions > Your subscription > Resource Providers > Register to Microsoft.insights.

Reference URLs

How to create storage account: https://docs.microsoft.com/en-us/azure/storage/common/storage-account-create?tabs=azure-portal

How to configure Event Hub: https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create

Enable raw data streaming

1. Log in to Microsoft Defender for Endpoint portal as a Global Administrator or Security Administrator.

2. Go to Data export settings page on Microsoft Defender Security Center.

3. Click on Add data export settings.

4. Choose a name for your new settings.

5. As per customer requirement, either you can store logs in Storage Account or stream the logs to Event Hub.

A. Archive to a storage account

1. Choose Forward events to Azure Storage.

2. Type your Storage Account Resource ID. In order to get your Storage Account Resource ID, go to your Storage account page on Azure portal > properties tab > copy the text under Storage account resource ID.

3. Choose the events you want to stream and click Save.

The schema of the events in the Storage account

1. A blob container will be created for each event type:

2. The schema of each row in a blob is the following JSON:

{
"time": "<The time WDATP received the event>"
"tenantId": "<Your tenant ID>"
"category": "<The Advanced Hunting table name with 'AdvancedHunting-' prefix>"
"properties": { <WDATP Advanced Hunting event as Json> }
}

Each blob contains multiple rows. Each row contains the event name, the time Defender for Endpoint received the event, the tenant it belongs (you will only get events from your tenant), and the event in JSON format in a property called "properties". For more information about the schema of Microsoft Defender for Endpoint events, see Advanced Hunting overview. In Advanced Hunting, the DeviceInfo table has a column named MachineGroup which contains the group of the device. Here every event will be decorated with this column as well. See Device Groups for more information.

B. Stream logs to an event hub

1. Choose Forward events to Azure Event Hubs.

2. Type your Event Hubs name and your Event Hubs resource ID.

3. In order to get your Event Hubs resource ID, go to your Azure Event Hubs namespace page on Azure > properties tab > copy the text under Resource ID:

4. Choose the events you want to stream and click Save.

The schema of the events in Azure Event Hubs

{
    "records": [
                    {
                        "time": "<The time WDATP received the event>"
                        "tenantId": "<The Id of the tenant that the event belongs to>"
                        "category": "<The Advanced Hunting table name with 'AdvancedHunting-' prefix>"
                        "properties": { <WDATP Advanced Hunting event as Json> }
                    }
                    ...
                ]
}

Each event hub message in Azure Event Hubs contains list of records. Each record contains the event name, the time Microsoft Defender for Endpoint received the event, the tenant it belongs (you will only get events from your tenant), and the event in JSON format in a property called "properties". For more information about the schema of Microsoft Defender for Endpoint events, see Advanced Hunting overview. In Advanced Hunting, the DeviceInfo table has a column named MachineGroup which contains the group of the device. Here every event will be decorated with this column as well. See Device Groups for more information.

Integration Parameters

Parameters required from customer for Integration.