Skip to content

Commit 636bfff

Browse files
cwatson-catcwatson-cat
committed
Sentinel DCs - restore Sonicwall Firewall
1 parent d19e2f7 commit 636bfff

File tree

2 files changed

+102
-5
lines changed

2 files changed

+102
-5
lines changed

‎.openpublishing.redirection.sentinel.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1180,11 +1180,6 @@
11801180
"redirect_url": "/azure/sentinel/data-connectors-reference",
11811181
"redirect_document_id": false
11821182
},
1183-
{
1184-
"source_path_from_root": "/articles/sentinel/data-connectors/sonicwall-firewall.md",
1185-
"redirect_url": "/azure/sentinel/data-connectors-reference",
1186-
"redirect_document_id": false
1187-
},
11881183
{
11891184
"source_path_from_root": "/articles/sentinel/data-connectors/varmour-application-controller.md",
11901185
"redirect_url": "/azure/sentinel/data-connectors-reference",

‎articles/sentinel/data-connectors/sonicwall-firewall.md

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
title: "SonicWall Firewall connector for Microsoft Sentinel"
3+
description: "Learn how to install the connector SonicWall Firewall to connect your data source to Microsoft Sentinel."
4+
author: cwatson-cat
5+
ms.topic: how-to
6+
ms.date: 11/29/2023
7+
ms.service: microsoft-sentinel
8+
ms.author: cwatson
9+
---
10+
11+
# SonicWall Firewall connector for Microsoft Sentinel
12+
13+
Common Event Format (CEF) is an industry standard format on top of Syslog messages, used by SonicWall to allow event interoperability among different platforms. By connecting your CEF logs to Microsoft Sentinel, you can take advantage of search & correlation, alerting, and threat intelligence enrichment for each log.
14+
15+
## Connector attributes
16+
17+
| Connector attribute | Description |
18+
| --- | --- |
19+
| **Log Analytics table(s)** | CommonSecurityLog (SonicWall)<br/> |
20+
| **Data collection rules support** | [Workspace transform DCR](/azure/azure-monitor/logs/tutorial-workspace-transformations-portal) |
21+
| **Supported by** | [SonicWall](https://www.sonicwall.com/support/) |
22+
23+
## Query samples
24+
25+
**All logs**
26+
```kusto
27+
CommonSecurityLog
28+
| where DeviceVendor == "SonicWall"
29+
| sort by TimeGenerated desc
30+
```
31+
32+
**Summarize by destination IP and port**
33+
```kusto
34+
CommonSecurityLog
35+
| where DeviceVendor == "SonicWall"
36+
| summarize count() by DestinationIP, DestinationPort, TimeGenerated
37+
| sort by TimeGenerated desc
38+
```
39+
40+
**Show all dropped traffic from the SonicWall Firewall**
41+
```kusto
42+
CommonSecurityLog
43+
| where DeviceVendor == "SonicWall"
44+
| where AdditionalExtensions contains "fw_action='drop'"
45+
```
46+
47+
48+
49+
## Vendor installation instructions
50+
51+
1. Linux Syslog agent configuration
52+
53+
Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.
54+
55+
Notice that the data from all regions will be stored in the selected workspace
56+
1.1 Select or create a Linux machine
57+
58+
Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-prem environment, Azure or other clouds.
59+
60+
1.2 Install the CEF collector on the Linux machine
61+
62+
Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP.
63+
64+
1. Make sure that you have Python on your machine using the following command: python -version.
65+
2. You must have elevated permissions (sudo) on your machine.
66+
Run the following command to install and apply the CEF collector:
67+
68+
`sudo wget -O cef_installer.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_installer.py&&sudo python cef_installer.py [Workspace ID] [Workspace Primary Key]`
69+
70+
2. Forward SonicWall Firewall Common Event Format (CEF) logs to Syslog agent
71+
72+
Set your SonicWall Firewall to send Syslog messages in CEF format to the proxy machine. Make sure you send the logs to port 514 TCP on the machine's IP address.
73+
74+
Follow Instructions . Then Make sure you select local use 4 as the facility. Then select ArcSight as the Syslog format.
75+
76+
3. Validate connection
77+
78+
Follow the instructions to validate your connectivity:
79+
80+
Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.
81+
82+
It may take about 20 minutes until the connection streams data to your workspace.
83+
If the logs are not received, run the following connectivity validation script:
84+
85+
1. Make sure that you have Python on your machine using the following command: python -version
86+
2. You must have elevated permissions (sudo) on your machine
87+
Run the following command to validate your connectivity:
88+
89+
`sudo wget -O cef_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py&&sudo python cef_troubleshoot.py [Workspace ID]`
90+
91+
4. Secure your machine
92+
93+
Make sure to configure the machine's security according to your organization's security policy
94+
95+
96+
[Learn more >](https://aka.ms/SecureCEF)
97+
98+
99+
100+
## Next steps
101+
102+
For more information, go to the [related solution](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/sonicwall-inc.sonicwall-networksecurity-azure-sentinal?tab=Overview) in the Azure Marketplace.

0 commit comments

Comments
 (0)