CommandCenter Secure Gateway - Admin Guide - Version ... - Raritan

Appendix B: CC-SG and Network Configuration
Port Number Protocol Purpose Details
51000 TCP SX Target Access (Direct Mode) AES-128/AES-256 encrypted if
configured.
Possible exceptions to the required open ports:
Port 80 can be closed if all access to the CC-SG is via HTTPS addresses.
Ports 5000 and 51000 can be closed if CC-SG Proxy mode is used for any
connections from the firewall(s).
CC-SG Communication Channels
Each communication channel is documented. For each communication
channel, the table includes:
• The symbolic IP Addresses used by the communicating parties.
These addresses must be allowed over any communication path
between the entities.
• The Direction in which the communication is initiated. This may be
important for your particular site policies. For a given CC-SG role, the
path between the corresponding communicating parties must be
available and for any alternate re-route paths that might be used in the
case of a network outage.
• The Port Number and Protocol used by CC-SG.
• Whether the port is Configurable, which means the Admin Client or
Diagnostic Console provides a field where you can change the port
number to a different value from the default listed if there are conflicts
with other applications on the network or for security reasons.
• Details about the method of communication, the message that is
passed via the communication channel, or its encryption.
CC-SG and Raritan Devices
A main role of CC-SG is to manage and control Raritan devices, such as
Dominion KX II. Typically, CC-SG communicates with these devices over
a TCP/IP network (local, WAN, or VPN) and both TCP and UDP protocols
are used as follows:
Communication Direction Port Number Protocol Configurable? Details
CC-SG to Local Broadcast 5000 UDP yes heartbeat
CC-SG to Remote LAN IP 5000 UDP yes heartbeat
280