Skip to main content

Juniper SRX

Juniper SRX is a networking firewall solution and services gateway. If you ship your Juniper firewall logs to your 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's security team: port scanning activity detected, failed login attempt from a malicious address, and more.

You can review the Juniper SRX resources in your Cloud SIEM account, under the pre-configured Juniper SRX security rules and search for the provided Juniper SRX dashboards to get you started.

Before you begin, you'll need:

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 public certificate to your credentials server

For HTTPS shipping, download the public certificate to your certificate authority folder.

sudo curl --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt

Configure Filebeat

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. (You want to replace the file's content with this code block.)

This code block adds Juniper SRX as an input sent over UDP traffic.


Filebeat requires a file extension specified for the log input.

# ...
- type: udp
max_message_size: 10MiB
host: ""

logzio_codec: plain

# Your account token. You can find your token at
type: juniper
fields_under_root: true
encoding: utf-8
ignore_older: 3h

# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat
- rename:
- from: "agent"
to: "filebeat_agent"
ignore_missing: true
- rename:
- from: "log.file.path"
to: "source"
ignore_missing: true

Copy and paste the following code block directly below. It sets as the output.

# ...
hosts: ["<<LISTENER-HOST>>:5015"]
certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']

Replace the placeholders to match your specifics. (They are indicated by the double angle brackets << >>):

  • Replace <<LOG-SHIPPING-TOKEN>> with the token of the account you want to ship to.

  • Replace <<LISTENER-HOST>> with the host for your region. For example, if your account is hosted on AWS US East, or if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.


One last validation - make sure is the only output and appears only once. If the file has other outputs, remove them.

Start Filebeat

Start or restart Filebeat for the changes to take effect.

Check 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.