SonicWall firewalls allow you to identify and control all of the applications in use on your network. This integration allows you to send logs from your SonicWall applications to your Logz.io SIEM account.
Before you begin
These are the prerequisites you'll need before you can begin:
Configure SonicWall Server logging
Configure your SonicWall firewall to send logs to your Filebeat server. Make sure you meet this configuration:
- Log format: syslog
- IP address: Filebeat server IP address
- Port 514
SonicWall firewall sends logs over UDP by default. See SonicWall docs for more information on configuring your SonicWall firewall.
Download the Logz.io public certificate to your credentials server
For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.
sudo curl https://raw.githubusercontent.com/logzio/public-certificates/master/AAACertificateServices.crt --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt
Open the Filebeat configuration file (/etc/filebeat/filebeat.yml) with your preferred text editor. Copy and paste the code block below, overwriting the previous content.
Filebeat requires a file extension specified for the log input.
This code block adds SonicWall as an input sent over UDP traffic.
- type: udp
# Your Logz.io account token. You can find your token at
# ... For Filebeat 7 only ...
- from: "agent"
- from: "log.file.path"
Copy and paste the following code block directly below. It sets Logz.io as the output.
Replace the placeholders to match your specifics. (They are indicated by the double angle brackets
<<LOG-SHIPPING-TOKEN>>with the token of the account you want to ship to.
<<LISTENER-HOST>>with the host for your region. For example,
listener.logz.ioif your account is hosted on AWS US East, or
listener-nl.logz.ioif hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
One last validation - make sure Logz.io is the only output and appears only once. If the file has other outputs, remove them.
Start or restart Filebeat for the changes to take effect. Start or restart Filebeat for the changes to take effect.
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Open Search Dashboards.
If you still don't see your logs, see Filebeat troubleshooting.