Collect Juniper Junos logs

This document describes how you can collect Juniper Junos logs by using a Google Security Operations forwarder.

For more information, see Data ingestion to Google Security Operations.

An ingestion label identifies the parser which normalizes raw log data to structured UDM format. The information in this document applies to the parser with the JUNIPER_JUNOS ingestion label.

Configure structured logging for a Juniper Networks SRX device

Structured log format extracts information from log messages. The log format complies with the Syslog protocol.

1. Sign in to Juniper SRX CLI using SSH to its management IP address.
2. Type CLI at the shell prompt and press enter.
3. Type configure and press enter to get into the configuration mode of the device.
4. Enter the contact details or customer reference point.

5. To map the fields to the user account, run the following commands:

      set system syslog host FORWARDER_IP_ADDRESS any info
   
      set system syslog host FORWARDER_IP_ADDRESS structured-data
   
   

   Replace FORWARDER_IP_ADDRESS with the IP address of the Google Security Operations forwarder.

6. To enable the structured logging for security logs, use the following commands:

      set security log mode stream
   
      set security log source-address SRC_IP_ADDRESS
   
      set security log stream SYSLOG_STREAM_NAME host FORWARDER_IP_ADDRESS
   
      set security log stream SYSLOG_STREAM_NAME format sd-syslog
   
   

   Replace the following:

   • SRC_IP_ADDRESS: the IP address of the Juniper SRX device.

   • SYSLOG_STREAM_NAME: the name which is assigned to the syslog server.

   • FORWARDER_IP_ADDRESS: the IP address of the Google Security Operations forwarder.

7. Make sure that logging is enabled on all the security policies. To enable logging, run the following commands:

      set security policies from-zone <zone-name1> to-zone <zone-name2> policy <policy-name> then log session-close
   
      set security policies from-zone <zone-name1> to-zone <zone-name2> policy <policy-name> then log session-init
   
   

8. Configure the hostname on the device using the following command:

      set system host-name HOSTNAME
   
   

   Replace HOSTNAME with the assigned Juniper Networks SRX device.

9. Enter commit to save the executed commands in the configuration.

Configure Google Security Operations forwarder and syslog to ingest Juniper Junos logs

1. Select SIEM Settings > Forwarders.
2. Click Add new forwarder.
3. Enter a unique name in the Forwarder name field.
4. Click Submit and then click Confirm. The forwarder is added and the Add collector configuration window appears.
5. In the Collector name field, enter a unique name for the collector.
6. Select Juniper Junos as the Log type.
7. Select Syslog as the Collector type.
8. Configure the following input parameters:
   • Protocol: specify the protocol as UDP.
   • Address: specify the target IP address or hostname where the collector resides and listens for syslog data.
   • Port: specify the target port where the collector resides and listens for syslog data.
9. Click Submit.

For more information about Google Security Operations forwarders, see Google Security Operations forwarders documentation. For information about requirements for each forwarder type, see Forwarder configuration by type. If you encounter issues when you create forwarders, contact Google Security Operations support.

Field mapping reference

This parser extracts fields from Juniper JUNOS syslog messages, handling both key-value and non-key-value formats. It uses grok patterns to match various message structures, including firewall logs, SSH activity, and command executions, then maps the extracted fields to the UDM. The parser also handles CEF formatted logs using an include file and performs specific actions based on the message content, such as merging IP addresses and usernames into appropriate UDM fields.

UDM mapping table

Changes

2024-05-02

• Enhancement-
• Added Grok patterns to support new SYSLOG + KV format logs.

2023-10-25

• Enhancement-
• Added Grok patterns to parse unparsed logs.
• Mapped "source_port" to "principal.port".
• Mapped "source_address" to "principal.ip".
• Mapped "user_name" to "target.user.userid".
• Mapped "application_name" to "target.application".
• Mapped "p_id" to "target.process.pid".
• Added "invalid_pattern" check before KV mapping.
• Added a Grok pattern to map "security_result.description" when "description_present" is false.

2023-08-17

• Enhancement-
• Added Grok pattern to parsed unparsed logs.
• Mapped "msg" to "security_result.summary".
• Mapped "src_ip" to "principal.ip".
• Mapped "user" to "target.user.userid".
• Mapped "username" to "principal.user.userid".
• Mapped "command" to "target.process.command_line".
• Mapped "src_port" to "principal.port".
• Mapped "ssh2" to "security_result.detection_fields".
• Mapped "sha256" to "principal.process.file.sha256".
• Mapped "desc" to "sec_result.summary".
• Mapped "mac-address" to "principal.mac".
• Mapped "host" to "principal.hostname" if event_type is "STATUS_UPDATE".

2023-01-15

• Enhancement-
• Modified Grok pattern to support unparsed logs containing type "UI_CMDLINE_READ_LINE", "UI_COMMIT_PROGRESS", "UI_CHILD_START",
• "UI_CFG_AUDIT_OTHER", "UI_LOGIN_EVENT", "UI_CHILD_STATUS", "UI_LOGOUT_EVENT", "UI_LOAD_EVENT",
• "JTASK_IO_CONNECT_FAILED", "UI_AUTH_EVENT", "UI_NETCONF_CMD", "UI_COMMIT_NO_MASTER_PASSWORD", "UI_CFG_AUDIT_SET", "UI_JUNOSCRIPT_CMD",
• "SNMPD_AUTH_FAILURE", "UI_CFG_AUDIT_NEW", "UI_COMMIT" , "LIBJNX_LOGIN_ACCOUNT_LOCKED", "UI_COMMIT_COMPLETED",
• "PAM_USER_LOCK_LOGIN_REQUESTS_DENIED", "RTPERF_CPU_USAGE_OK", "RTPERF_CPU_THRESHOLD_EXCEEDED", "LIBJNX_LOGIN_ACCOUNT_UNLOCKED",
• "JSRPD_SET_OTHER_INTF_MON_FAIL", "JSRPD_SET_SCHED_MON_FAILURE", "UI_CHILD_WAITPID", "UI_DBASE_LOGIN_EVENT".

2022-05-02

• New default parser.