サポートと今すぐチャット
サポートとのチャット

One Identity Safeguard for Privileged Sessions 7.3.1 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS)
The philosophy of One Identity Safeguard for Privileged Sessions (SPS) Policies Credential Stores Plugin framework Indexing Supported protocols and client applications Modes of operation Connecting to a server through One Identity Safeguard for Privileged Sessions (SPS) Archive and backup concepts Maximizing the scope of auditing IPv6 in One Identity Safeguard for Privileged Sessions (SPS) SSH host keys Authenticating clients using public-key authentication in SSH The gateway authentication process Four-eyes authorization Network interfaces High Availability support in One Identity Safeguard for Privileged Sessions (SPS) Versions and releases of One Identity Safeguard for Privileged Sessions (SPS) Accessing and configuring One Identity Safeguard for Privileged Sessions (SPS)
Cloud deployment considerations The Welcome Wizard and the first login Basic settings
Supported web browsers The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving Cleaning up audit data Using plugins Forwarding data to third-party systems Starling integration
User management and access control
Login settings Managing One Identity Safeguard for Privileged Sessions (SPS) users locally Setting password policies for local users Managing local user groups Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database Authenticating users to a RADIUS server Authenticating users with X.509 certificates Authenticating users with SAML2 Managing user rights and usergroups Creating rules for restricting access to search audit data Displaying the privileges of users and user groups Listing and searching configuration changes
Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing One Identity Safeguard for Privileged Sessions (SPS) clusters Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS)
General connection settings HTTP-specific settings ICA-specific settings MSSQL-specific settings RDP-specific settings SSH-specific settings Using Sudo with SPS Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS)
Network troubleshooting Gathering data about system problems Viewing logs on One Identity Safeguard for Privileged Sessions (SPS) Changing log verbosity level of One Identity Safeguard for Privileged Sessions (SPS) Collecting logs and system information for error reporting Collecting logs and system information of the boot process for error reporting Support hotfixes Status history and statistics Troubleshooting a One Identity Safeguard for Privileged Sessions (SPS) cluster Understanding One Identity Safeguard for Privileged Sessions (SPS) RAID status Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data VNC is not working with TLS Configuring the IPMI from the BIOS after losing IPMI password Incomplete TSA response received Using UPN usernames in audited SSH connections
Using SPS with SPP Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help Configuring SPS to use an LDAP backend Glossary

Configuring SPS to enable exporting sound from audit trails

From SPS version 6.11, you can enable auditing the sound that is transferred between an RDP client and the server.

Using the Safeguard Desktop Player application, you can export the input and output sound recorded on the side of the audited user to a .wav file.

NOTE: To export audio files from the audit trails, make sure that you have the appropriate version of Safeguard Desktop Player installed.

For more information on the sound export process in Safeguard Desktop Player, see Exporting files from an audit trail.

To configure SPS to enable extracting sound from audit trails

  1. Navigate to RDP Control > Channel Policies and open the policy that you want to use for sound auditing or create and configure a new connection for this purpose.

    For example, you can use the all policy for sound auditing as well.

  2. From the Type drop-down, open Sound and Dynamic virtual channel and make sure that the Record audit trail checkbox is selected for both of these channel types.

    NOTE: If the Record audit trail checkbox is selected only for the Sound channel, only the output sound (the one that is received by the audited user) is recorded in the audit trail.

    If the Record audit trail checkbox is selected for the Dynamic virtual channel, both the input sound (the one that comes from the audited user) and output sound (the one that is received by the audited user) are recorded.

    TIP: To play back the video file of the recorded audit trails with sound, enable the Record audit trail checkbox for the Drawing channel as well.

  3. Click to save your configuration.

Sharing RDP connection policies with SPP

The Share connection policy with SPP option enables you to use RDP connection policies in SPP to initiate sessions.

Prerequisites

Link an SPP appliance to SPS. For more information, see Linking SPS to SPP.

To share an RDP connection policy

  1. Navigate to RDP Control > Connections.

    Figure 228: RDP Control > Connections — Functions shared with SPP

  2. Select Share connection policy with SPP.

    NOTE: The Share connection policy with SPP checkbox is enabled only if you have linked an SPP appliance to SPS.

  3. Set the following configuration for the RDP connection policy:

    • In Target, select Inband destination selection.

    • Unselect Require Gateway Authentication on the SPS Web Interface.

    • In AA plugin, consider the following, then select the AA plugin of your choice:

      • Select an AA plugin different from the safeguard_default plugin.

      • Alternatively, leave AA plugin unset.

      WARNING: Do not delete or rename the safeguard_default AA plugin; otherwise, you are not able to use the Share connection policy with SPS option.
      If you have modified the safeguard_default plugin, to proceed, revert your changes.

    • In Credential Store, select SGCredStore.

      NOTE: The SGCredStore option is available only if you have linked an SPP appliance to SPS.

  4. To save your changes, click Commit.

Sharing RDP connection policies with SPS

If you have joined an SPP to SPS, the Share connection policy with SPS option enables you to use RDP connection policies in SPS to initiate sessions.

Prerequisites

Link an SPP appliance to SPS. For more information, see Linking SPS to SPP.

To share an RDP connection policy

  1. Navigate to RDP Control > Connections.

    Figure 229: RDP Control > Connections — Functions shared with SPP

  2. Select Share connection policy with SPS.

    NOTE: The Share connection policy with SPS checkbox is enabled only if you have linked an SPP appliance to SPS.

  3. Set the following configuration for the RDP connection policy:

    • Unselect Require Gateway Authentication on the SPS Web Interface.

    • In AA plugin, consider the following:

      • Select an AA plugin different from the safeguard_default plugin.

      • Alternatively, leave AA plugin unset.

      WARNING: Do not delete or rename the safeguard_default AA plugin; otherwise, you are not able to use the Share connection policy with SPS option.
      If you have modified the safeguard_default plugin, to proceed, revert your changes.

  4. To save your changes, click Commit.

Using credential injection in SPP-initiated RDP sessions

The Credential injection option enables you to use credential injection in SPP-initiated RDP sessions.

The RDP Application session initiated on the SPP side provides the password automatically for the RemoteApp Launcher. To use credential injection, use a connection policy for the RDP Application session that has Credential injection selected.

Prerequisites

Link an SPP appliance to SPS. For more information, see Linking SPS to SPP.

To enable credential injection for SPP, select the Share connection policy with SPP option as well.

To use credential injection in SPP-initiated sessions

  1. Navigate to RDP Control > Connections.

    Figure 230: RDP Control > Connections — Functions shared with SPP

  2. Select Share connection policy with SPP.

    NOTE: The Share connection policy with SPP checkbox is enabled only if you have linked an SPP appliance to SPS.

    For more information on the required connection policy settings, see Sharing RDP connection policies with SPP.

  3. Select Credential injection and set the following configuration in RDP > Channel policies:

    • In RDP Control > Channel policies, select Drawing.

    • In RDP Control > Channel policies, select Dynamic virtual channel.

    • In RDP Control > Channel policies > Custom > Permitted channels, set rail.

    • In RDP Control > Channel policies > Custom > Permitted channels, set rail_ri.

    • In RDP Control > Channel policies > Custom > Permitted channels, set rail_wi.

    1. To save your changes, click Commit.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択