Accenture MDR Quick Start Guide for Juniper Networks® SRX
This quick start guide will help Accenture MDR customers configure Juniper Networks® SRX to send logs to the Log Collection Platform (LCP).
The document includes the following topics:
Supported Versions
A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture Portal - https://mss.accenture.com/PortalNextGen/Reports/Documents
Port Requirements
Table 1-1: Port requirements for LCP communication.
Source | Destination | Port | Description |
Juniper SRX | LCP | 514 (UDP) or 601 (TCP) | Default port |
Configuring Juniper Networks SRX
Juniper Networks SRX can be configured to log event data in Structured Format
Structured log format represents the syslog data in a key-value pair. Specifying the structured data format can make it easier for applications to extract information from log messages.
Structured-data format complies with the Internet draft, the syslog protocol which can currently be found at http://tools.ietf.org/html/draft-ietf-syslog-protocol-23.
To configure the Juniper Networks SRX device for structured event format, follow the steps below.
Connect to the Juniper SRX CLI via SSH to its management IP address.
Once logged it then type CLI at the shell prompt and press enter.
Type configure and press enter to get into the configuration mode of the device.
Type the below commands:
set system syslog host <lcp_ip_address> any info
set system syslog host <lcp_ip_address> structured-data
5. To enable the structured logging for security logs, type the following commands.
set security log mode stream
set security log source-address <src_ip_address>
set security log stream <syslog_stream_name> host <lcp_ip_address>
set security log stream <syslog_stream_name> format sd-syslog
Here,
<
src_ip_address
> represents the IP address of the Juniper SRX device,<
syslog_stream_name
> represents the name which can be assigned to the syslog server, and<
lcp_ip_address
> represents the IP address of the LCP.
6. Make sure that logging is enabled on all the security policies, if not, then enable logging using 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
7. Configure the hostname on the device using the command:
Here, <
hostname
> represents the hostname assigned to Juniper Networks SRX device.
8. To save the above executed commands in the configuration, enter commit.
LCP Configuration Parameters
Table 1-2: The Juniper SRX event collector (Syslog - 3652) properties to be configured by MDR are shown in the table.
Property | Default Value | Description |
Protocol | UDP | The default protocol for syslog. The collector can also accept logs in TCP. Note: While TCP offers guaranteed delivery of log packets, it places a larger overhead on the LCP. To balance TCP for reliability over UDP for speed/simplicity, contact the MDR onboarding team. |
IP Address | Juniper SRX device IP address | Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ). Note: If the device sends logs using multiple interfaces, contact the MDR onboarding team. |
Signatures | ACCT_,ALARMD_,ANCPD_,ANTISPAM_, APPIDD_, APPTRACK_,ASP_, AUDITD_,AUTHD_,AUTOCONFD_, AUTOD_, AV_,BFDD_,BOOTPD_,CFMD_,CHASSISD_, CONTENT_,COSD_,DCD_,DFCD_,DFWD_, DH_, DHCPD_, DYNAMIC_,ESWD_, EVENTD_,FCD_,FLO_, FPCLOGIN_, FSAD_,FUD_,FWAUTH_,GPRSD_, HNCACHED_,ICCPD_, IDP_,JADE_, JCS_,JDIAMETERD_, JPTSPD_, JSRPD_,KMD_,L2ALD_,L2CPD_,L2TPD_, LACPD_,LFMD_,LIBESPTASK_, LIBJNX_, LIBJSNMP_ ,LIBMSPRPC_,LICENSE_,LLDPD_, LOGIN_,LPDD_,LRMUX_,LSYSD_,MCSN_, MCSNOOPD_, MIB2D_,MPLS_,MPLS_OAM_, NEXTHOP_,NSD_,NSTRACED_,NTPD_, NTPDATE_,PFE_,PFED_,PGCPD_, PING_,PKID_, PPMD_ ,PPPD_,PROFILER_, RDD_,RMOPD_,RPD_,RT_, RTLOG_, RTLOGD_,RTPERF_,SAVAL_,SDXD_, SFW_, STPD_, SNMP_,SNMPD_,SPD_, SSH_,SSHD_, SYSTEM_,TASK_,TFTPD_, UFDD_,UI_,UI_,UTMD_,VCCPD_,VRRPD_,VSYSD_,WEB_,WEBFILTER_ | MDR recommended signatures processed by the Juniper SRX event collector. |
Port Number | 514 | The default port number for syslog. For TCP, the default port is 601. Note: The LCP can be configured to listen on a non-standard port, please advise the MDR onboarding team if this is a requirement. |
Legal Notice
Copyright © 2021 Accenture. All rights reserved.
Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.