FortiGate units are installed as a gateway or router between two networks. This integration allows you to send FortiGate logs to your Logz.io SIEM account.
Before you begin, you’ll need:
Configure FortiGate logging
Configure your FortiGate firewall to send logs to your Filebeat server. Make sure you meet this configuration:
- Log format: syslog
- Send over: UDP
- IP address: Filebeat server IP address
- Port 514
See the FortiGate docs for more information on configuring your FortiGate firewall.
Sample commands for FortiOS 6.2
config log syslogd setting set status enable set format default set server <FILEBEAT-SERVER-IP-ADDR> set port 514 end
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/AAACertificateServices.crt
Add UDP traffic as an input
In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add UDP to the filebeat.inputs section.
<<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.
# ... filebeat.inputs: - type: udp max_message_size: 10MiB host: "0.0.0.0:514" fields: logzio_codec: plain # Your Logz.io account token. You can find your token at # https://app.logz.io/#/dashboard/settings/manage-accounts token: <<LOG-SHIPPING-TOKEN>> type: fortigate fields_under_root: true encoding: utf-8 ignore_older: 3h
If you’re running Filebeat 7, paste this code block. Otherwise, you can leave it out.
# ... For Filebeat 7 only ... filebeat.registry.path: /var/lib/filebeat processors: - rename: fields: - from: "agent" to: "filebeat_agent" ignore_missing: true - rename: fields: - from: "log.file.path" to: "source" ignore_missing: true
If you’re running Filebeat 6, paste this code block.
# ... For Filebeat 6 only ... registry_file: /var/lib/filebeat/registry
Set Logz.io as the output
If Logz.io is not an output, add it now. Remove all other outputs.
<<LISTENER-HOST>> with the host for your region. For example,
listener.logz.io if your account is hosted on AWS US East, or
listener-nl.logz.io if hosted on Azure West Europe.
# ... output.logstash: hosts: ["<<LISTENER-HOST>>:5015"] ssl: certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']
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 Kibana.
If you still don’t see your logs, see log shipping troubleshooting.