Cisco ASA is a security device that combines firewall, antivirus, intrusion prevention, and virtual private network (VPN) capabilities.
Before you begin, you'll need: Root access to a server running Filebeat with port 6514 open for incoming traffic and 5015 open for outgoing traffic
Configure Cisco ASA Server logging
Configure your Cisco ASA firewall to send logs to your Filebeat server. Make sure you meet this configuration:
- Log format: syslog
- Send over: TCP
- IP address: Filebeat server IP address
- Port 6514
See Cisco docs for more information on configuring your Cisco ASA 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
Add TCP traffic as an input
In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add TCP to the filebeat.inputs section.
<<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.
Filebeat requires a file extension specified for the log input.
- type: tcp
# Your Logz.io account token. You can find your token at
If you're running Filebeat 7, paste this code block. Otherwise, you can leave it out.
# ... For Filebeat 7 only ...
- from: "agent"
- from: "log.file.path"
If you're running Filebeat 6, paste this code block.
# ... For Filebeat 6 only ...
Set Logz.io as the output
If Logz.io is not an output, add it now. (Remove all other outputs - there should only be 1 output in the configuration file.)
<<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. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
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.