Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Common Ports and Servers Used by JSA


JSA requires that certain ports are ready to receive information from JSA components and external infrastructure. To ensure that JSA is using the most recent security information, it also requires access to public servers and RSS feeds.

SSH Communication on Port 22

All the ports that are used by the JSA console to communicate with managed hosts can be tunneled, by encryption, through port 22 over SSH.

The console connects to the managed hosts using an encrypted SSH session to communicate securely. These SSH sessions are initiated from the console to provide data to the managed host. For example, the JSA console can initiate multiple SSH sessions to the Event Processor appliances for secure communication. This communication can include tunneled ports over SSH, such as HTTPS data for port 443 and Ariel query data for port 32006. JSA Flow Processor that use encryption can initiate SSH sessions to Flow Processor appliances that require data.

Open Ports that are not Required by JSA

You might find additional open ports in the following situations:

  • When you install JSA on your own hardware, you may see open ports that are used by services, daemons, and programs included in Red Hat Enterprise Linux.

  • When you mount or export a network file share, you might see dynamically assigned ports that are required for RPC services, such as rpc.mountd and rpc.rquotad.