Merge pull request #274280 from cwatson-cat/5-03-24-sf-dc-restore

Sentinel DCs - restore Sonicwall Firewall

Author: JamesJBarnett

.openpublishing.redirection.sentinel.json

@@ -1180,11 +1180,6 @@
             "redirect_url": "/azure/sentinel/data-connectors-reference",
             "redirect_document_id": false
         },
-        {
-            "source_path_from_root": "/articles/sentinel/data-connectors/sonicwall-firewall.md",
-            "redirect_url": "/azure/sentinel/data-connectors-reference",
-            "redirect_document_id": false
-        },
         {
             "source_path_from_root": "/articles/sentinel/data-connectors/varmour-application-controller.md",
             "redirect_url": "/azure/sentinel/data-connectors-reference",

articles/sentinel/TOC.yml

@@ -716,6 +716,8 @@
       href: data-connectors/snowflake.md
     - name: Sonrai Data Connector
       href: data-connectors/sonrai-data-connector.md
+    - name: SonicWall Firewall 
+      href: data-connectors/sonicwall-firewall.md
     - name: Sophos Cloud Optix
       href: data-connectors/sophos-cloud-optix.md
     - name: Sophos Endpoint Protection (using Azure Functions)

articles/sentinel/data-connectors-reference.md

@@ -617,6 +617,10 @@ Data connectors are available as part of the following offerings:
 
 - [Snowflake (using Azure Functions)](data-connectors/snowflake.md)
 
+## SonicWall Inc
+
+- [SonicWall Firewall](data-connectors/sonicwall-firewall.md)
+
 ## Sonrai Security
 
 - [Sonrai Data Connector](data-connectors/sonrai-data-connector.md)

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

@@ -0,0 +1,105 @@
+---
+title: "SonicWall Firewall connector for Microsoft Sentinel"
+description: "Learn how to install the connector SonicWall Firewall to connect your data source to Microsoft Sentinel."
+author: cwatson-cat
+ms.topic: how-to
+ms.date: 11/29/2023
+ms.service: microsoft-sentinel
+ms.author: cwatson
+---
+
+# SonicWall Firewall connector for Microsoft Sentinel
+
+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.
+
+This is autogenerated content. For changes, contact the solution provider.
+
+
+## Connector attributes
+
+| Connector attribute | Description |
+| --- | --- |
+| **Log Analytics table(s)** | CommonSecurityLog (SonicWall)<br/> |
+| **Data collection rules support** | [Workspace transform DCR](/azure/azure-monitor/logs/tutorial-workspace-transformations-portal) |
+| **Supported by** | [SonicWall](https://www.sonicwall.com/support/) |
+
+## Query samples
+
+**All logs**
+   ```kusto
+CommonSecurityLog
+   | where DeviceVendor == "SonicWall"
+   | sort by TimeGenerated desc
+   ```
+
+**Summarize by destination IP and port**
+   ```kusto
+CommonSecurityLog
+   | where DeviceVendor == "SonicWall"
+   | summarize count() by DestinationIP, DestinationPort, TimeGenerated
+   | sort by TimeGenerated desc
+   ```
+
+**Show all dropped traffic from the SonicWall Firewall**
+   ```kusto
+CommonSecurityLog
+   | where DeviceVendor == "SonicWall"
+   | where AdditionalExtensions contains "fw_action='drop'"
+   ```
+
+
+
+## Vendor installation instructions
+
+1. Linux Syslog agent configuration
+
+Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.
+
+Notice that the data from all regions will be stored in the selected workspace
+1.1 Select or create a Linux machine.
+
+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.
+
+1.2 Install the CEF collector on the Linux machine
+
+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.
+
+1. Make sure that you have Python on your machine using the following command: python -version.
+2. You must have elevated permissions (sudo) on your machine.
+   Run the following command to install and apply the CEF collector:
+
+   `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]`
+
+2. Forward SonicWall Firewall Common Event Format (CEF) logs to Syslog agent
+
+   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.
+
+    Follow Instructions. Then Make sure you select local use 4 as the facility. Then select ArcSight as the Syslog format.
+
+3. Validate connection
+
+Follow the instructions to validate your connectivity:
+
+Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.
+
+It may take about 20 minutes until the connection streams data to your workspace.
+If the logs are not received, run the following connectivity validation script:
+
+1. Make sure that you have Python on your machine using the following command: python -version
+2. You must have elevated permissions (sudo) on your machine
+   Run the following command to validate your connectivity:
+
+   `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]`
+
+4. Secure your machine 
+
+Make sure to configure the machine's security according to your organization's security policy.
+
+
+[Learn more >](https://aka.ms/SecureCEF)
+
+
+
+## Next steps
+
+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.