Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 2.4 - Administration Guide

Introduction System requirements Installing the One Identity Safeguard for Privileged Passwords desktop client Setting up Safeguard for Privileged Passwords for the first time Getting acquainted with the console Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Directories Entitlements Partitions Settings
Access Request settings Appliance settings Asset Management settings Backup and Retention settings Certificate settings Cluster settings External Integration settings Messaging settings Profile settings Access settings Sessions settings
Users User Groups Disaster recovery Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions
How do I access the API How do I audit transaction activity How do I configure external federation authentication How do I manage accounts on unsupported platforms How do I modify the appliance configuration settings How do I prevent Safeguard for Privileged Passwords messages when making RDP connections How do I see which assets and/or accounts are governed by a profile How do I set the appliance system time How do I setup discovery jobs How do Safeguard for Privileged Passwords database servers use SSL What are the access request states What do I do when an appliance goes into quarantine What is required for One Identity Safeguard for Privileged Passwords Privileged Sessions What is required to integrate with Starling Identity Analytics & Risk Intelligence What needs to be set up to use Application to Application What role-based email notifications are generated by default When does the rules engine run for dynamic grouping and tagging Why did the password change during an open request Why join Safeguard for Privileged Passwords to One Identity Starling
Safeguard Desktop Player Appendix: Safeguard ports

Exporting video

Use the Export Video button at the top of the Safeguard Desktop Player to export the sessions recording file as a video file (WEBM format). This WEBM file can then be played back using any standard video player, such as the one available with Firefox or Google Chrome.

To export a video

  1. In the Safeguard for Privileged Passwords Desktop Player, click (or tap) Export Video.

    The Export screen appears, displaying the name of the video file and the size of the file.

  2. If you want to include user event subtitles with the exported file, select the Subtitle check box in the upper left corner of the screen.
  3. Click (or tap) the browse button () in the lower right corner of the screen to specify the location where the file is to be stored.

    The specified location appears in the Export to field.

  4. Click the Export button.

    An Export Successful message appears.

Key descriptions

Expanding a channel in the Channels pane of the Safeguard for Privileged Passwords Desktop Player displays additional details about the recording. The keys displayed depends on the type of channel selected. The keys marked with an asterisk (*) may provide you some additional insight into the recording; most of the other keys are internal values.

Table 285: Safeguard Desktop Player: Key descriptions
Key Description
auth_method Authentication method used.
bpp Color depth (bits-per-pixel) of the remote machine.
channel_id Internal identifier assigned to the channel being recorded.
channel_name Internal name assigned to the channel being recorded.
channel_policy Internal name assigned to the channel policy being used.
channel_type Type of channel: SSH or RDP
client_address* Address of the client computer.
client_address.ip IP address of the client computer.
client_address.port Port used by the client computer.
client_id Internal identifier assigned to the client computer.
client_x509_subject Client certificate subject.
connection Internal connection policy being used.
connection_id Internal connection identifier assigned to the recording.
data_received Data received flag: True
data_sent Data sent flag: True
dst_ip IP address of the session recording module.
duration* Duration of the recording.
duration_raw Raw duration of the recording (should be the same as the duration).
exit_status Exit status of the program run on the remote server.
height_rows* Number of rows shown in the SSH terminal.
initiator Who initiated the connection: Client
is_processable Indicates if the session can be processed: True
local_ip IP address of the sessions module.
protocol* Protocol used: SSH or RDP
remote_username* Name of the user name that log into the remote machine.
server_address* Address and port of the remote machine.
server_address.ip IP address of the remote machine.
server_address.port Port used to connect to the remote machine.
server_id Internal identifier assigned to the remote machine.
server_ip IP address of the remote machine.
session_end Time (in milliseconds) when the session ended.
session_id Internal session ID assigned to the session.
session_start Time (in milliseconds) when the session started.
Signature Validity of the Session Recording Signing certificate.
source Source protocol: SSH or RDP
stream_type Internal type assigned to the recording stream.
term Type of SSH terminal.
Timestamp Validity of the Timestamping Authority certificate.
username Name of the user that authenticated to the remote machine.
width_cols Width (in columns) of the original SSH session screen.
width_pix* Width (in pixels) of the original SSH session screen.
width* Screen width of the RDP session.

Appendix: Safeguard ports

Safeguard for Privileged Passwords requires port availability for various system operations.

Port details

Safeguard network port details are in the following table.

Table 286: Safeguard ports

Use in SPP

Appliance Port

Protocol

Description

 

 MGMT

TCP

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.

Base operation

25

TCP

SMTP: Simple Mail Transfer

Base operation

53

TCP / UDP

DNS (Domain Name Server)

Base operation

123

 

NTP time synchronization

Base operation (AD asset and account discovery, password check and change)

389

TCP

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:

Base operation (password check and change)

445

TCP SMB

NetLogon Service (NP-In) is used to perform password check and changes for Windows Active Directory and Windows, Windows Desktop. Also see port 389 and Prepare Windows systems

WMI

135

(49152-65535 Windows)

TCP

The firewall must be configured to allow WMI (Windows Management Instrumentation 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
  • Recording using embedded sessions

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:

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

WMI

49152-65535

 

See port 135

Archiving

22

TCP (X0)

The Secure Shell (SSH) Protocol for SFTP/SCP transfers backups and session recordings to the archive server for the SPP embedded sessions module.

See:

Embedded sessions

22 and 3389

TCP (X1)

RDP (3389/TCP) is permitted inbound for PSM RDP sessions (SPP embedded sessions module). Users who will use the embedded session require access to the cluster X1 ports on port 3389 to make an RDP connection to the target system and to port 22 for SSH connections. See: KB article 262371.

Firewall

655

TCP / UDP (X0)

TINC (665) is open for secure VPN communication between appliances in a clustered high-availability configuration. TINC perfers UDP and uses TCP if UDP is unreliable. See KB article 23267.

To enroll an appliance into a cluster, the appliance must communicate over port 655 UDP/TCP and port 443 TCP and must have IPv4 or IPv6 network addresses (not mixed). See:

Firewall and Client and Web browser points

443

TCP

(X0)

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/TCP and port 443 TCP and must have IPv4 or IPv6 network addresses (not mixed). See:

The port is used to prepare VMware ESXi host and HP iLO servers. See:

Global catalog

3268

 

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:

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

SQL server

1433

 

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

Radius server

1812

 

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

Kiosk

DB9

SERIAL

To connect to the Safeguard Kiosk. See KB article 233584.

 

23

TCP

Telnet

 

8443

TCP/ UDP

For SonicWALL SMA or CMS appliance. See information related to authenticating an asset, Password.

Platform ports

ACF2 – 23

ACF2 LDAP – 389

AIX – 22

AWS – 443

Cent OS – 22

Cisco Pix – 22

Debian – 22

IDRAC – 22

ESXi - 443 default

F5 - 22 default

Facebook - 443

Fortinet – 22 default

Free BSD – 22

HP* - 22

IBM I – 23

JunOS – 22

MongoDB - https://docs.mongodb.com/manual/reference/default-mongodb-port/

MySQL – 3306

Oracle – 1521

Oracle Linux – 1521

OSX – 22

Other – no default port

Other Linux – 22

Pan OS – 22

PostgreSQL – 5432 default

RACF – 23

RACF LDAP – 389

RHEL – 22

SAP Hana – 39013 default

SAP Netweaver – 3300

Solaris – 22

SoniOS – 22

SonicWall SMA – 22

SQL – 1433

SUSE – 22

SyBase – 5002

Top Secret – 23

Top Secret LDAP – 389

Twitter – 443

Ubuntu – 22

Windows (various depanding on OS type) – 135/389/445 and maybe dynamic ports

Archiving

Archiving uses uses SFTP/SCP and CIFS.

  • SFTP/SCP: 22 TCP (X0). See the Port details table, 22 for X0.
  • CIFS: Uses UDP ports 137 and 138 and TCP ports 139 and 445.

Backup

Same as Archiving.

External Authentication

Federation – Port 443

Secondary Auth – Radius Port 1812

Starling - Port 443

External Integration

SNMP – Port 162 UDP

SNTP - Port 25 TCP Simple Mail Transfer

SysLog – 514 UDP

External Integration for Password Workflow

Approval Anywhere - 443

Ticketing – Service now 443

Ticketing - Remedy 1433 (communicates to the SQL server directly)

Other

NTP – port 123 UDP

Directories – Ports 389 LDAP and 3268 global catalog

Related Documents