One Identity Safeguard for Privileged Passwords 7.4.1 - Appliance Setup Guide

HTTPS used for a secure first-time configuration of the appliance. The IP address is a fixed address that cannot be changed. It is available in case the primary interface becomes unavailable.

Typically used: TCP/443 and IP address: 192.168.1.105

SMTP: Simple Mail Transfer

DNS (Domain Name Server)

NTP time synchronization

For communication with Active Directory, Safeguard uses port 88 (for example, Kerbos authorization against Active Directory).

LDAP used for Active Directory Asset Discovery and Directory Accounts Discovery. The standard global catalog port, 3268 (LDAP), must be open on the firewall for every Windows global catalog server in the environment and SPP Appliance to communicate for directory management tasks (for example, adding a directory account, a directory user account, or a directory user group). LDAP uses port 389 for unencrypted connections. For more information, see the Microsoft publication How the Global Catalog Works.

For basic functionality when changing an OS account password, the following ports are required:

• Windows Active Directory: TCP/389 and TCP/445
• Windows, Windows Desktop: TCP/445

Also see:

• Adding identity and authentication providers
• Preparing Windows systems
• Port 445

NetLogon Service (NP-In) is used to perform:

• Password check and changes for Windows Active Directory
• Password and SSH key check and changes for Windows, Windows Desktop.

Also see port 389 and Preparing Windows systems

The firewall must be configured to allow Windows Management Instrumentation (WMI) for computer name and other lookups. WMI is also required if SPP performs any of the functions listed below on any Windows machine (whether it be a dependent system or a normal target platform):

• Managing service account passwords
• Managing scheduled task passwords
• Restarting a service
• Using Account Discovery on the target

WMI / DCOM from DPA will need access to TCP/135 to initiate communication on the target. The conversation continues on a random negotiated port. On Windows 7 and Windows 2008 (and above) this is in the range: 49152 - 65535.

To limit the ports used by WMI/DCOM, refer to these Microsoft articles:

• How to configure RPC dynamic port allocation to work with firewalls
• Setting Up a Fixed Port for WMI

For Windows Active Directory, if using Account Discovery or Auto Discovery CLDAP ping UDP/389 is also required. See:

• Preparing Windows systems
• Networking

See port 135

Used for the SPP/SPS internal communications when SPS is linked with SPP.

• SPS to SPP:
  • SPS completes the link by talking to SPP on port 8649.
  • SPS authenticates a new session and acquires the password from SPP by talking on port 8649.
  • SPS queries SPP for cluster information and the appliance version.
• SPP to SPS:
  • SPP queries SPS for cluster information and node roles.
  • SPP pushes SSH host keys to SPS when a session is initiated.
  • SPP queries SPS for session playback, follow mode, and session termination.

In SPS, the nodes require UDP ports 500 and 4500 and TCP 8649. For the latest detail, see the SPS Administration Guide, Enabling cluster management.

WireGuard (655) is open for secure VPN communication between appliances in a clustered high-availability configuration.

To enroll an appliance into a cluster, the appliance must communicate over port 655 UDP and port 443 TCP, and must have IPv4 or IPv6 network addresses (not mixed). If both IPv4 and IPv6 are available for the connection then IPv6 will be used. See:

• KB article 232289
• KB article 252260
• KB article 232671
• Cluster
• Enrolling replicas into a cluster

HTTPS over TLS/SSL (443/TCP) permits inbound requests (for client/Web/API access). Used to initially log on to the appliance to join the cluster member. Users must have access to the cluster X0 ports on port 443.

To enroll an appliance into a cluster, the appliance must communicate over port 655 UDP and port 443 TCP, and must have IPv4 or IPv6 network addresses (not mixed). If both IPv4 and IPv6 are available for the connection then IPv6 will be used. See:

• KB article 232289
• KB article 252260
• KB article 232671
• KB article 229909 (Starling related endpoint)

The port is used to prepare VMware ESXi host. See:

• Preparing VMware ESXi hosts

The LDAP standard global catalog port for Active Directory. The standard global catalog port, 3268 (LDAP), must be open on the firewall for every Windows global catalog server in the environment and SPP Appliance to communicate for directory management tasks (for example, adding a directory account, a directory user account, or a directory user group). LDAP uses port 389 for unencrypted connections. For more information, see the Microsoft publication How the Global Catalog Works. Also see:

• Adding an account
• Adding a directory user group

There are no services listening for this port on a member/server workstation (local configuration).

Default port number that a Radius server uses to listen for authentication requests. See Adding identity and authentication providers.

For SonicWALL SMA or CMS appliance. See information related to authenticating an asset, Password (local service account).

The port on which the SQL server will be listening for connections. See information related to authenticating an asset, Password (local service account).