Skip to content

Commit 2b07660

Browse files
committed
xdr note added
1 parent 39603f7 commit 2b07660

File tree

1 file changed

+36
-26
lines changed

1 file changed

+36
-26
lines changed

articles/defender-for-cloud/export-to-siem.md

Lines changed: 36 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to stream your security alerts to Microsoft Sentinel, SIE
44
ms.topic: how-to
55
ms.author: dacurwin
66
author: dcurwin
7-
ms.date: 01/10/2024
7+
ms.date: 01/11/2024
88
---
99

1010
# Stream alerts to monitoring solutions
@@ -14,13 +14,13 @@ Microsoft Defender for Cloud has the ability to stream security alerts into vari
1414
There are built-in Azure tools that are available that ensure you can view your alert data in the following solutions:
1515

1616
- **Microsoft Sentinel**
17-
- **Defender XDR**
17+
- **Microsoft Defender XDR**
1818
- **Splunk Enterprise and Splunk Cloud**
19-
- **IBM's QRadar**
20-
- **ServiceNow**
21-
- **ArcSight**
2219
- **Power BI**
20+
- **ServiceNow**
21+
- **IBM's QRadar**
2322
- **Palo Alto Networks**
23+
- **ArcSight**
2424

2525
## Stream alerts to Microsoft Sentinel
2626

@@ -55,11 +55,15 @@ Another alternative for investigating Defender for Cloud alerts in Microsoft Sen
5555
> [!TIP]
5656
> Microsoft Sentinel is billed based on the volume of data that it ingests for analysis in Microsoft Sentinel and stores in the Azure Monitor Log Analytics workspace. Microsoft Sentinel offers a flexible and predictable pricing model. [Learn more at the Microsoft Sentinel pricing page](https://azure.microsoft.com/pricing/details/azure-sentinel/).
5757
58+
## Stream alerts to Defender XDR
59+
60+
Defender for Cloud natively integrates with [Microsoft Defender XDR](/microsoft-365/security/defender/microsoft-365-defender?view=o365-worldwide) allows you to use Defender XDR's incidents and alerts API to stream alerts and incidents into non-Microsoft solutions. Customers who have both [Microsoft Office 365 E5](https://www.microsoft.com/microsoft-365/enterprise/office-365-e5#overview) and Defender for Cloud can access one API for all Microsoft security products. Defender for Cloud customers can use this integration as an easier way to export alerts and incidents.
61+
62+
Learn how to [integrate SIEM tools with Defender XDR](/microsoft-365/security/defender/configure-siem-defender?view=o365-worldwide).
63+
5864
## Stream alerts to QRadar and Splunk
5965

60-
The export of security alerts to Splunk and QRadar uses Event Hubs and a built-in connector.
61-
You can either use a PowerShell script or the Azure portal to set up the requirements for exporting security alerts for your subscription or tenant.
62-
Then you need to use the procedure specific to each SIEM to install the solution in the SIEM platform.
66+
To export security alerts to Splunk and QRadar you will need to use Event Hubs and a built-in connector. You can either use a PowerShell script or the Azure portal to set up the requirements for exporting security alerts for your subscription or tenant. Once the requirements are in place, you need to use the procedure specific to each SIEM to install the solution in the SIEM platform.
6367

6468
### Prerequisites
6569

@@ -68,37 +72,43 @@ Before you set up the Azure services for exporting alerts, make sure you have:
6872
- Azure subscription ([Create a free account](https://azure.microsoft.com/free/))
6973
- Azure resource group ([Create a resource group](../azure-resource-manager/management/manage-resource-groups-portal.md))
7074
- **Owner** role on the alerts scope (subscription, management group or tenant), or these specific permissions:
71-
- Write permissions for event hubs and the Event Hub Policy
75+
- Write permissions for event hubs and the Event Hubs Policy
7276
- Create permissions for [Microsoft Entra applications](../active-directory/develop/howto-create-service-principal-portal.md#permissions-required-for-registering-an-app), if you aren't using an existing Microsoft Entra application
7377
- Assign permissions for policies, if you're using the Azure Policy 'DeployIfNotExist'
7478
<!-- - To export to a Log Analytics workspace:
7579
- if it **has the SecurityCenterFree solution**, you'll need a minimum of read permissions for the workspace solution: `Microsoft.OperationsManagement/solutions/read`
7680
- if it **doesn't have the SecurityCenterFree solution**, you'll need write permissions for the workspace solution: `Microsoft.OperationsManagement/solutions/action` -->
7781

78-
### Step 1: Set up the Azure services
82+
### Set up the Azure services
7983

8084
You can set up your Azure environment to support continuous export using either:
8185

82-
- A PowerShell script (Recommended)
86+
#### PowerShell script (Recommended)
87+
88+
Download and run [the PowerShell script](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Powershell%20scripts/3rd%20party%20SIEM%20integration).
89+
Enter the required parameters and the script performs all of the steps for you.
90+
When the script finishes, use the output to install the solution in the SIEM platform.
91+
92+
#### Azure portal
93+
94+
Here's an overview of the steps you'll do in the Azure portal:
95+
96+
1. Sign in to the [Azure portal](https://portal.azure.com).
8397

84-
Download and run [the PowerShell script](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Powershell%20scripts/3rd%20party%20SIEM%20integration).
85-
Enter the required parameters and the script performs all of the steps for you.
86-
When the script finishes, it outputs the information you’ll use to install the solution in the SIEM platform.
98+
1. Search for and select `Event Hubs`.
8799

88-
- The Azure portal
100+
1. [Create an Event Hubs namespace and event hub](../event-hubs/event-hubs-create.md).
89101

90-
Here's an overview of the steps you'll do in the Azure portal:
102+
1. Define a policy for the event hub with `Send` permissions.
91103

92-
1. Create an Event Hubs namespace and event hub.
93-
2. Define a policy for the event hub with “Send” permissions.
94-
3. **If you're streaming alerts to QRadar** - Create an event hub "Listen" policy, then copy and save the connection string of the policy that you’ll use in QRadar.
95-
4. Create a consumer group, then copy and save the name that you’ll use in the SIEM platform.
96-
5. Enable continuous export of security alerts to the defined event hub.
97-
6. **If you're streaming alerts to QRadar** - Create a storage account, then copy and save the connection string to the account that you’ll use in QRadar.
98-
7. **If you're streaming alerts to Splunk**:
99-
1. Create a Microsoft Entra application.
100-
2. Save the Tenant, App ID, and App password.
101-
3. Give permissions to the Microsoft Entra Application to read from the event hub you created before.
104+
1. **If you're streaming alerts to QRadar** - Create an event hub "Listen" policy, then copy and save the connection string of the policy that you’ll use in QRadar.
105+
1. Create a consumer group, then copy and save the name that you’ll use in the SIEM platform.
106+
1. Enable continuous export of security alerts to the defined event hub.
107+
1. **If you're streaming alerts to QRadar** - Create a storage account, then copy and save the connection string to the account that you’ll use in QRadar.
108+
1. **If you're streaming alerts to Splunk**:
109+
1. Create a Microsoft Entra application.
110+
1. Save the Tenant, App ID, and App password.
111+
1. Give permissions to the Microsoft Entra Application to read from the event hub you created before.
102112

103113
For more detailed instructions, see [Prepare Azure resources for exporting to Splunk and QRadar](export-to-splunk-or-qradar.md).
104114

0 commit comments

Comments
 (0)