Skip to content

Commit 38cfac5

Browse files
committed
fixes finished
1 parent 2b07660 commit 38cfac5

File tree

1 file changed

+45
-22
lines changed

1 file changed

+45
-22
lines changed

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

Lines changed: 45 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Learn how to [integrate SIEM tools with Defender XDR](/microsoft-365/security/de
6363

6464
## Stream alerts to QRadar and Splunk
6565

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.
66+
To export security alerts to Splunk and QRadar, you 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.
6767

6868
### Prerequisites
6969

@@ -85,13 +85,15 @@ You can set up your Azure environment to support continuous export using either:
8585

8686
#### PowerShell script (Recommended)
8787

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.
88+
1. Download and run [the PowerShell script](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Powershell%20scripts/3rd%20party%20SIEM%20integration).
9189

92-
#### Azure portal
90+
1. Enter the required parameters.
91+
92+
1. Execute the script.
93+
94+
The script performs all of the steps for you. When the script finishes, use the output to install the solution in the SIEM platform.
9395

94-
Here's an overview of the steps you'll do in the Azure portal:
96+
#### Azure portal
9597

9698
1. Sign in to the [Azure portal](https://portal.azure.com).
9799

@@ -101,18 +103,35 @@ Here's an overview of the steps you'll do in the Azure portal:
101103

102104
1. Define a policy for the event hub with `Send` permissions.
103105

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+
**If you're streaming alerts to QRadar**
107+
108+
1. Create an event hub `Listen` policy.
109+
110+
1. Copy and save the connection string of the policy to use in QRadar.
111+
112+
1. Create a consumer group.
113+
114+
1. Copy and save the name to use in the SIEM platform.
115+
106116
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.
112117

113-
For more detailed instructions, see [Prepare Azure resources for exporting to Splunk and QRadar](export-to-splunk-or-qradar.md).
118+
1. Create a storage account.
114119

115-
### Step 2: Connect the event hub to your preferred solution using the built-in connectors
120+
1. Copy and save the connection string to the account to use in QRadar.
121+
122+
For more detailed instructions, see [Prepare Azure resources for exporting to Splunk and QRadar](export-to-splunk-or-qradar.md).
123+
124+
**If you're streaming alerts to Splunk**:
125+
126+
1. Create a Microsoft Entra application.
127+
128+
1. Save the Tenant, App ID, and App password.
129+
130+
1. Give permissions to the Microsoft Entra Application to read from the event hub you created before.
131+
132+
For more detailed instructions, see [Prepare Azure resources for exporting to Splunk and QRadar](export-to-splunk-or-qradar.md).
133+
134+
### Connect the event hub to your preferred solution using the built-in connectors
116135

117136
Each SIEM platform has a tool to enable it to receive alerts from Azure Event Hubs. Install the tool for your platform to start receiving alerts.
118137

@@ -123,14 +142,18 @@ Each SIEM platform has a tool to enable it to receive alerts from Azure Event Hu
123142

124143
## Stream alerts with continuous export
125144

126-
To stream alerts into **ArcSight**, **SumoLogic**, **Syslog servers**, **LogRhythm**, **Logz.io Cloud Observability Platform**, and other monitoring solutions, connect Defender for Cloud using continuous export and Azure Event Hubs:
145+
To stream alerts into **ArcSight**, **SumoLogic**, **Syslog servers**, **LogRhythm**, **Logz.io Cloud Observability Platform**, and other monitoring solutions, connect Defender for Cloud using continuous export and Azure Event Hubs.
127146

128147
> [!NOTE]
129148
> To stream alerts at the tenant level, use this Azure policy and set the scope at the root management group. You'll need permissions for the root management group as explained in [Defender for Cloud permissions](permissions.md): [Deploy export to an event hub for Microsoft Defender for Cloud alerts and recommendations](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2fcdfcce10-4578-4ecd-9703-530938e4abcb).
130149
131-
1. Enable [continuous export](continuous-export.md) to stream Defender for Cloud alerts into a dedicated event hub at the subscription level. To do this at the Management Group level using Azure Policy, see [Create continuous export automation configurations at scale](continuous-export.md?tabs=azure-policy#configure-continuous-export-at-scale-using-the-supplied-policies).
150+
**To stream alerts with continuous export**:
151+
152+
1. Enable continuous export:
153+
- At the [subscription level](continuous-export.md).
154+
- At the [Management Group level using Azure Policy](continuous-export.md?tabs=azure-policy#configure-continuous-export-at-scale-using-the-supplied-policies).
132155

133-
2. Connect the event hub to your preferred solution using the built-in connectors:
156+
1. Connect the event hub to your preferred solution using the built-in connectors:
134157

135158
| Tool | Hosted in Azure | Description |
136159
|:---|:---| :---|
@@ -140,15 +163,15 @@ To stream alerts into **ArcSight**, **SumoLogic**, **Syslog servers**, **LogRhyt
140163
| LogRhythm | No| Instructions to set up LogRhythm to collect logs from an event hub are available [here](https://logrhythm.com/six-tips-for-securing-your-azure-cloud-environment/).
141164
|Logz.io | Yes | For more information, see [Getting started with monitoring and logging using Logz.io for Java apps running on Azure](/azure/developer/java/fundamentals/java-get-started-with-logzio)
142165

143-
3. Optionally, stream the raw logs to the event hub and connect to your preferred solution. Learn more in [Monitoring data available](../azure-monitor/essentials/stream-monitoring-data-event-hubs.md#monitoring-data-available).
166+
1. (Optional) Stream the raw logs to the event hub and connect to your preferred solution. Learn more in [Monitoring data available](../azure-monitor/essentials/stream-monitoring-data-event-hubs.md#monitoring-data-available).
144167

145168
To view the event schemas of the exported data types, visit the [Event Hubs event schemas](https://aka.ms/ASCAutomationSchemas).
146169

147-
## Use the Microsoft Graph Security API to stream alerts to third-party applications
170+
## Use the Microsoft Graph Security API to stream alerts to non-Microsoft applications
148171

149-
As an alternative to Microsoft Sentinel and Azure Monitor, you can use Defender for Cloud's built-in integration with [Microsoft Graph Security API](/graph/security-concept-overview/). No configuration is required.
172+
Defender for Cloud's built-in integration with [Microsoft Graph Security API](/graph/security-concept-overview/) without the need of any further configuration requirements.
150173

151-
You can use this API to stream alerts from your **entire tenant** (and data from many Microsoft Security products) into third-party SIEMs and other popular platforms:
174+
You can use this API to stream alerts from your **entire tenant** (and data from many Microsoft Security products) into non-Microsoft SIEMs and other popular platforms:
152175

153176
- **Splunk Enterprise and Splunk Cloud** - [Use the Microsoft Graph Security API Add-On for Splunk](https://splunkbase.splunk.com/app/4564/)
154177
- **Power BI** - [Connect to the Microsoft Graph Security API in Power BI Desktop](/power-bi/connect-data/desktop-connect-graph-security).

0 commit comments

Comments
 (0)