M2: Data Connectors
Last updated
Last updated
In this module you will learn how to enable Data Connectors in Microsoft Sentinel to bring alerts and/or telemtry from different sources.
This module assumes that you have completed Module 1, as you will need an Microsoft Sentinel workspace provisioned.
Some of the data connectors that will be used in this lab, require some specific permissions on the workspace or your azure subscription. If you don't have the appropriate permissions, you can still continue doing the rest of the labs.
This exercise shows you how to enable the Azure Activity data connector. This connector will bring into your Microsoft Sentinel workspace all the audit events for actions performed in your Azure subscription.
NOTE: To do this exercise, your user must have Reader permissions to any subscription which logs you want to stream into Microsoft Sentinel.
Go to you Microsoft Sentinel workspace and select Data Connectors under Configuration section.
In the data connectors screen, type actvity in the search bar, select the Azure Activity connector and click on Open connector page.
In the Azure Activity connector page, go to option number 2 Connect your subscriptions through diagnostic settings new pipeline. This method leverages Azure Policy and it brings many improvements compared to the old method (more details about these improvements can be found here).
Click on the Launch Azure Policy Assignment wizard, this will redirect you to the policy creation page.
On the Scope selection select your relevant subscription.
NOTE: Please note that if you have owner permission on a management group level, you can assign this policy to configure collection of Azure Activity logs form all the subscriptions under the management group.
Go to the Parameters tab. On the Primary Log Analytics workspace select the Microsoft Sentinel workspace:
Press Review and Create to save this policy and Create.
Click on Next Steps. Here you see what content is available for the telemetry that is brought into Sentinel by this connector, like Workbooks, Query samples and Analytics Rules.
It is normal if you don't immediately see the connector showing as connected and in green. Also, each subscription has a maximum of 5 destinations for its activity logs. If this limit is already reached, the policy created as part of this exercise won't be able to add an additional destination to your Microsoft Sentinel workspace.
This exercise shows you how to enable the Microsoft Defender for Cloud data connector. This connector allows you to stream your security alerts from Microsoft Defender for Cloud into Microsoft Sentinel, so you can view Defender data in workbooks, query it to produce alerts, and investigate and respond to incidents.
NOTE: To do this exercise, your user must have the Security Reader role in the subscription of the logs you stream. If not done already, you will need to enable any of the Defender plans in Microsoft Defender for Cloud.
Go to you Microsoft Sentinel workspace and select Data Connectors under Configuration section.
In the data connectors screen, type defender in the search bar, select the Microsoft Defender for Cloud connector and click on Open connector page.
In the Microsoft Defender for Cloud connector page, check that your permissions are enough at the top. If you don't have the required permissions, you can continue to the next exercise.
From the list of subscriptions at the bottom of the page, select the desired subscription an click on Connect. Wait for the operation to complete.
Click on Next Steps at the top of the page and explore what content is available for this connector.
Connecting Microsoft Sentinel to Pulsedive TAXII Server
Go to you Microsoft Sentinel workspace and select Data Connectors under Configuration section.
In the data connectors screen, type taxii in the search bar, select the Threat intelligence - TAXII connector and click on Open connector page.
In the Threat Intelligence - TAXII connector page, add the following information under Configuration menu:
To connect Microsoft Sentinel to Pulsedive’s TAXII Server, obtain the API Root, Collection ID, Username and Password from Pulsedive.
Obtain access to Pulsedive via Microsoft Sentinel by following these steps:
Create a free Pulsedive account at pulsedive.com/register
Configure the TAXII client in Sentinel with the following information:
API root: https://pulsedive.com/taxii2/api/
Indicator collection ID: a5cffbfe-c0ff-4842-a235-cb3a7a040a37
Username: taxii2
Password: your API key, which can be found on your account page
Visit Pulsedive’s TAXII documentation to learn more
Sample Screenshot
Click Add and wait until the operation completes.
Click on Next Steps at the top of the page and explore what content is available for this connector. In a few seconds, the ThreatIntelligenceIndicator will be populated with IOCs from Pulsedive's feed.
You can now continue to Module 3 - Analytics Rules
