SonicWall Logs

Ship logs from SonicWall to Logstash

Filebeat is a lightweight shipper that enables you to send your SonicWall logs to Logstash and OpenSearch. Configure Filebeat using the pre-defined examples below to start sending and analysing your SonicWall logs.

Install Integration

Please click on the Install Integration button to configure your stack for this source.

Configure Syslog Server

Configure your SonicWall to write all logs to a single file and to send logs to a Syslog server.

View more details (opens in a new tab) on how to configure SonicWall Syslog.

Install Filebeat

To get started you will need to install filebeat. To do this you have two main options:

Choose the filebeat (opens in a new tab) ZIP file (Windows ZIP x86_64) or
Choose the Microsoft Software Installer MSI (opens in a new tab) file (Windows MSI x86_64 (beta))

To successfully install filebeat and set up the required Windows service you will need to have administrator access.

If you have chosen to download the zip file:

Extract the contents of the zip file into C:\Program Files.
Rename the extracted folder to filebeat
Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
From the PowerShell prompt, run the following commands to install filebeat as a Windows service:

cd 'C:\Program Files\filebeat'

.\install-service-filebeat.ps1

If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example:

PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1

For more information about Powershell execution policies see here (opens in a new tab).

If you have chosen to download the filebeat.msi file:

double-click on it and the relevant files will be downloaded.

At the end of the installation process you'll be given the option to open the folder where filebeat has been installed.

Open a PowerShell prompt as an Administrator (right-click the PowerShell icon and select Run As Administrator).
From the PowerShell prompt, change directory to the location where filebeat was installed and run the following command to install filebeat as a Windows service:

.\install-service-filebeat.ps1

If script execution is disabled on your system, you need to set the execution policy for the current session to allow the script to run. For example:

PowerShell.exe -ExecutionPolicy UnRestricted -File .\install-service-filebeat.ps1

For more information about Powershell execution policies see here (opens in a new tab).

Locate the configuration file

/etc/filebeat/filebeat.yml

Configure Filebeat.yml

The configuration file below is pre-configured to send data to your Logit.io Stack.

Copy the configuration file below and overwrite the contents of the Filebeat configuration file typically located at /etc/filebeat/filebeat.yml

# ============================== Filebeat inputs ===============================
filebeat.inputs:
 
- type: udp
  max_message_size: 10MiB
  host: "0.0.0.0:514"
  enabled: true
 
  fields:
      type: "@type:strip_quotes"
  fields_under_root: true
  encoding: utf-8
  ignore_older: 12h
 
# ================================== Outputs ===================================
output.logstash:
    hosts: ["@logstash.host:@logstash.sslPort"]
    loadbalance: true
    ssl.enabled: true

If you're running Filebeat 7, add this code block to the end. Otherwise, you can leave it out.

# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat

If you're running Filebeat 6, add this code block to the end.

# ... For Filebeat 6 only ...
registry_file: /var/lib/filebeat/registry

It's a good idea to run the configuration file through a YAML validator to rule out indentation errors, clean up extra characters, and check if your YAML file is valid. Yamllint.com (opens in a new tab) is a great choice.

Validate configuration

In the directory where Filebeat is installed, run the following command to validate the installation:

.\@beatname.exe test config -c @beatname.yml

If the yml file is invalid, @beatname will print a description of the error. For example, if the output.logstash section was missing, @beatname would print no outputs are defined, please define one under the output section

Start filebeat

To start Filebeat, run in Powershell:

Start-Service filebeat

Check Logit.io for your logs

Data should now have been sent to your Stack.

View My Data

If you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.

How to diagnose no data in Stack

If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.

SonicWall Logging Overview

SonicWall is a network security company that provides a range of products and services to protect networks from threats such as viruses, malware, and ransomware. Logging in SonicWall refers to the process of collecting and analyzing log data generated by SonicWall devices to monitor and troubleshoot network security issues.

SonicWall devices generate various types of log data, including system logs, security logs, and application logs. These logs contain information about events such as network traffic, user activity, and security threats.

SonicWall devices provide a range of logging options, including:

Syslog: This is a standard protocol for forwarding log messages across IP networks. SonicWall devices can be configured to send syslog messages to a syslog server, which can be used to collect and analyze log data from multiple devices.

SNMP Traps: SNMP (Simple Network Management Protocol) is a protocol used to manage and monitor network devices. SonicWall devices can be configured to send SNMP traps to a central management system, which can be used to monitor the health and performance of the devices.

Real-time Monitoring: SonicWall devices provide a real-time monitoring interface that enables administrators to view log data in real-time. This can be useful for quickly identifying and responding to security threats or network issues.

Analytics and Reporting: SonicWall devices also provide analytics and reporting capabilities, which enable administrators to analyze log data to identify trends and patterns. This can be useful for identifying areas of the network that may be vulnerable to security threats or for identifying potential performance issues.

Overall, logging in SonicWall devices provides visibility into network activity and security threats, which can help administrators monitor and troubleshoot network issues. SonicWall devices provide a range of logging options, including real-time monitoring, syslog, SNMP traps, and analytics and reporting, which enable administrators to collect and analyze log data to identify and respond to security threats and network issues.

Redis Stormshield