Juniper SRX is a networking firewall solution and services gateway. If you ship your Juniper firewall logs to your Logz.io Cloud SIEM, you can centralize your security ops and receive alerts about security events logged by Juniper SRX.
Here are just a few examples for security rules written specifically for Juniper SRX and provided out-of-the-box by Logz.io’s security team: port scanning activity detected, failed login attempt from a malicious address, and more.
On this page
- Configure Juniper SRX Server logging
- Download the Logz.io public certificate to your Filebeat server
- Configure Filebeat
- Replace the placeholders in the Filebeat configuration
- Start Filebeat
- Check Logz.io for your logs
Step by step
Before you begin, you’ll need:
- Juniper SRX
- Filebeat 7
- Root access
Configure Juniper SRX Server logging
Configure your Juniper 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 Juniper SRX docs for more information on configuring your Juniper SRX firewall.
Download the Logz.io public certificate to your Filebeat 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 contents. (You want to replace the file’s contents with this code block.)
This code block adds Juniper SRX as an input sent over UDP traffic. It contains the placeholder
<<SHIPPING-TOKEN>> which you’ll need to replace in the next step.
# ... 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: <<SHIPPING-TOKEN>> type: juniper fields_under_root: true encoding: utf-8 ignore_older: 3h # ... 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
Copy and paste the following code block directly below. It sets Logz.io as the output. It contains the placeholder
<<LISTENER-HOST>> which you’ll need to replace in the next step.
# ... output.logstash: hosts: ["<<LISTENER-HOST>>:5015"] ssl: certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']
Replace the placeholders in the Filebeat configuration
Still in the same configuration file, replace the placeholders to match your specifics.
<<SHIPPING-TOKEN>>with the token of the account you want to ship to.
<<LISTENER-HOST>>with your region’s listener host (for example,
listener.logz.io). For more information on finding your account’s region, see Account region.
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.
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.