JSA Common Ports Lists

Transcription

1 Juniper Secure Analytics Release Juniper Networks, Inc North Mathilda Avenue Sunnyvale, CA USA Published:

2 Copyright Notice Copyright 2016 Juniper Networks, Inc. All rights reserved. Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. The following terms are trademarks or registered trademarks of other companies: Java TM and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. All specifications are subject to change without notice. Juniper Networks assumes no responsibility for any inaccuracies in this document or for any obligation to update information in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. FCC Statement The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. The equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense. The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Juniper Networks installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Consult the dealer or an experienced radio/tv technician for help. Connect the equipment to an outlet on a circuit different from that to which the receiver is connected. Caution: Changes or modifications to this product could void the user's warranty and authority to operate this device. Disclaimer THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT, SUBJECT TO THE MODIFICTAIONS SET FORTH BELOW ON THIS PAGE, ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR JUNIPER NETWORKS REPRESENTATIVE FOR A COPY. Release Copyright 2016, Juniper Networks, Inc. All rights reserved. Printed in USA. Revision History April 2016 The information in this document is current as of the date listed in the revision history. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ( EULA ) posted at as modified by the following text, which shall be treated under the EULA as an Entitlement Document taking precedence over any conflicting provisions of such EULA as regards such software: As regards software accompanying the STRM products (the Program ), such software contains software licensed by Q1 Labs and is further accompanied by third-party software that is described in the applicable documentation or materials provided by Juniper Networks. 2

3 For the convenience of Licensee, the Program may be accompanied by a third party operating system. The operating system is not part of the Program, and is licensed directly by the operating system provider (e.g., Red Hat Inc., Novell Inc., etc.) to Licensee. Neither Juniper Networks nor Q1 Labs is a party to the license between Licensee and the third party operating system provider, and the Program includes the third party operating system AS IS, without representation or warranty, express or implied, including any implied warranty of merchantability, fitness for a particular purpose or non-infringement. For an installed Red Hat operating system, see the license file: /usr/share/doc/redhat-release-server-6server/eula. By downloading, installing or using such software, you agree to the terms and conditions of that EULA as so modified. 3

4 4

5 CONTENTS 1 JSA COMMON PORTS JSA Common Ports Viewing Random Port Associations Searching for Ports on JSA

6

7 1 JSA COMMON PORTS This technical note provides a list of common ports used by Juniper Secure Analytics (JSA), services, and. The information provided in this document contains the assigned port number, descriptions, protocols, and the signaling direction for the port. Unless otherwise noted, all references to JSA refer to JSA and Log Manager. References to flows do not apply to Log Manager. JSA Common Ports The listening ports for JSA as listed in Table 1-1 are valid only when iptables is enabled on your JSA system. c Table 1-1 Listening Ports Used by JSA, Services, and Components Port Description Protocol Direction Required for 22 SSH TCP JSA console to all other 25 SMTP TCP From all managed hosts to your SMTP gateway Remote management access Adding a remote system as a managed host Log source protocols to retrieve files from external devices, for example the Log File protocol End-users who use the command line to communicate from desktops to the JSA console high availability hcommunication Allowing JSA to send s to an SMTP gateway Error and warning message delivery to an administrative contact

8 8 JSA COMMON PORTS Table 1-1 Listening Ports Used by JSA, Services, and Components (continued) Port Description Protocol Direction Required for 37 Rdate (time) UDP/TCP All systems to the JSA console JSA console to the NTP or RDATE server 80 Apache/https TCP End users to the JSA console End users to the JSA Deployment Editor 111 Port mapper TCP/UDP JSA managed hosts connecting to the JSA console. End users connecting to the JSA console 135 and dynamically allocated ports above 1024 for RPC calls. DCOM TCP From Windows host providing events using Windows Management Instrumentation (WMI) to JSA consoles or Event Collectors 161 SNMP agent UDP JSA managed hosts connecting to the Juniper Secure Analytics (JSA) console External log sources to JSA Event Collectors 199 NetSNMP TCP JSA managed hosts connecting to the JSA console External log sources to JSA Event Collectors Time synchronization between the JSA console and managed hosts Communication and downloads from the JSA console to end-user desktops Allowing the deployment editor application to download from the JSA console to end-user desktops Remote Procedure Calls (RPC) for required services, such as Network File System (NFS) DCOM communication and the collection of Windows events using WMI. Firewalls between JSA and the target Microsoft Windows host must be configured to allow DCOM communication. Note: DCOM typically uses a range of random ports, which can be configured to use a specific range. For more information, see your Microsoft Windows documentation. UDP listening port for the SNMP agent TCP port for the NetSNMP daemon listening for communications (v1, v2c, and v3) from external log sources

9 JSA Common Ports 9 Table 1-1 Listening Ports Used by JSA, Services, and Components (continued) Port Description Protocol Direction Required for 443 Apache/https TCP JSA managed hosts connecting to the JSA console End users connecting to the Juniper Secure Analytics (JSA) console 514 Syslog UDP External log sources to JSA Event Collectors 762 Network File System mount daemon (mountd) TCP/UDP Connections between the JSA console and NFS server 1514 Syslog-ng TCP/UDP Connection between the local Event Collector component and local Event Processor component to the syslog-ng daemon for logging 2049 NFS TCP Connections between the JSA console and NFS server 2055 NetFlow data UDP From the management interface on the flow source (typically a router) to the Flow Processor Configuration downloads to managed hosts from the JSA console End users to have log in access to Juniper Secure Analytics (JSA) External log sources to send event data to JSA The Network File System (NFS) mount daemon, which processes requests to mount a file system at a specified location Internal logging port for syslog-ng The Network File System (NFS) protocol to share files or data between NetFlow datagram from, such as routers 4333 Redirect port TCP This port is assigned as a redirect port for Address Resolution Protocol (ARP) requests in JSA Offense Resolution 5432 Postgres TCP Communication for the managed host used to access the local database instance 6543 High Availability heartbeat TCP/UDP Bi-directional between the secondary host and primary host in an high availability cluster When provisioning managed hosts using the Admin tab Heartbeat ping from a secondary host to a primary host in an high availability cluster to detect hardware or network failure

10 10 JSA COMMON PORTS Table 1-1 Listening Ports Used by JSA, Services, and Components (continued) Port Description Protocol Direction Required for 7676, 7677, and four randomly bound ports above Messaging connections (IMQ) TCP Message queue communications between on a managed host to 7782, 7790, 7791 JMX server ports TCP Internal communications, these ports are not available externally 7789 high availability Distributed Replicated Block Device (DRBD) TCP/UDP Bi-directional between the secondary host and primary host in an high availability cluster 7800 Apache Tomcat TCP From the Event Collector to the JSA console 7801 Apache Tomcat TCP From the Event Collector to the JSA console 7803 Apache Tomcat TCP From the Event Collector to the JSA console 8000 Event Collection Service (ECS) TCP From the Event Collector to the JSA console Message queue broker for communications between on a managed host Ports 7676 and 7677 are static TCP ports and four additional connections are created on random ports. For more information on randomly bound ports, see Viewing Random Port Associations. JMX server (Mbean) monitoring for ECS, hostcontext, Tomcat, VIS, reporting, ariel, and accumulator services. These ports are used by JSA support. Distributed Replicated Block Device (DRBD) used to keep discs synchronized between the primary and secondary hosts in high availability configurations Real-time (streaming) for events Real-time (streaming) for flows Anomaly Detection Engine listening port Listening port for specific Event Collect Service (ECS) events 8005 Apache Tomcat TCP None This is a local port not used by JSA Apache Tomcat TCP From the HTTP daemon (httpd) process to Tomcat 8080 Apache Tomcat TCP From the HTTP daemon (httpd) process to Tomcat 9995 NetFlow data UDP From the management interface on the flow source (typically a router) to the Flow Processor Tomcat connector, where the request is used and proxied for the web service Tomcat connector, where the request is used and proxied for the web service. NetFlow datagram from, such as routers

11 JSA Common Ports 11 Table 1-1 Listening Ports Used by JSA, Services, and Components (continued) Port Description Protocol Direction Required for TCP/UDP End-user desktop to all JSA hosts Juniper Secure Analytics (JSA) Web-Based System Administration Interface Server changes, such as root password and firewalls SOAP Webserver TCP SOAP Webserver listening port for the Event Collection Service (ECS) Normalized Event Forwarding TCP Bi-directional between JSA Data flow TCP Bi-directional between JSA Ariel queries TCP Bi-directional between JSA Identity data TCP Bi-directional between JSA Flow source listening port TCP Bi-directional between JSA Ariel listening port TCP Bi-directional between JSA Data flow (flows, events, flow context) TCP Bi-directional between JSA PCAP data TCP From Juniper Networks SRX Series appliances to JSA Normalized event data communicated from an off-site source or between Event Collectors Data flow communication port between Event Collectors when located on separate managed hosts Communication port between the Ariel Proxy server and the Ariel Query server Identity data communicated between the passive Vulnerability Information Service (VIS) and the Event Collection Service (ECS) Flow listening port to collect data from Flow Processors Ariel listening port for database searches, progress information, and other associated commands Data flows, such as events, flows, flow context, and event search queries Collecting incoming packet capture (PCAP) data from Juniper Networks SRX Series appliances Note: The packet capture on your device can use an alternate port to For more information on configuring packet capture, see your Juniper Networks SRX Series appliance documentation.

12 12 JSA COMMON PORTS Table 1-1 Listening Ports Used by JSA, Services, and Components (continued) Port Description Protocol Direction Required for ICMP ICMP Bi-directional between the secondary host and primary host in an high availability cluster Testing the network connection between the secondary host and primary host in an high availability cluster using Internet Control Message Protocol (ICMP) All the ports listed in Table 1-1 can be tunneled, by encryption, through port 22 over SSH. Viewing Random Port Associations Several ports allocate additional random port numbers for application services, for example, Message Queues (IMQ). About this task You can view additional port numbers using telnet to connect to the localhost and look up the port number. NOTE Random port associations are not static port numbers. If a service is restarted, the ports generated for a service are reallocated and the service is provided with a new set of port numbers. Step 1 Step 2 Step 3 Procedure Using SSH, log in to your JSA console, as the root user. Login: root Password: <password> Type the following command: telnet localhost 7676 If no information is displayed, press Enter to terminate the connection. Searching for Ports on JSA Netstat is a command line tool used to determine which ports are in use on your JSA console or managed host. About this task The netstat command allows you to view all listening and established ports on the system.

13 Searching for Ports on JSA 13 Step 1 Step 2 Step 3 Procedure to use the netstat command Using SSH log in to your JSA console, as the root user. Login: root Password: <password> Type the following command: netstat -nap To search for specific information from the netstat port list, type the following command: netstat -nap grep <port> Where <port> is the port number or search term for the netstat search. For example: netstat -nap grep Displays all ports matching 199. netstat -nap grep postgres - Displays all postgres related ports. netstat -nap grep LISTEN - Displays information on all listening ports. What to do next For more information on using the netstat command, type netstat? for a list of netstat options.

14