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

One Identity Safeguard for Privileged Sessions 7.3 - Getting Started with Safeguard for Privileged Sessions as a Virtual Appliance

Setting up a basic monitoring and controlling configuration for SSH and RDP

The rest of the guide will walk you through the steps required after the installation to get you started. You will learn how to do the following in the next sections:

  1. Review and customize your network settings.

  2. Configure a basic SSH Connection Policy.

  3. Understand and customize the most important options around authentication and destination selection.

  4. Understand and test real-time activity monitoring and Four Eyes Authorization.

  5. Configure a basic RDP Connection Policy.

  6. Understand and configure screen content indexing.

  7. Understand and test the main functions of the search interface for audit recordings.

Initial setup

To start the setup of SPS

  1. Connect to SPS.

    The SPS virtual machine acquires an IP address from your DHCP server accessible in the virtual environment. After SPS has booted up, the console displays the IP address of the SPS web interface at login prompt. To connect to SPS, use this IP address. For details, or tips if SPS cannot receive an IP address, see "The initial connection to One Identity Safeguard for Privileged Sessions (SPS)" in the Administration Guide.

  2. Complete the Welcome Wizard as described in "Configuring One Identity Safeguard for Privileged Sessions (SPS) with the Welcome Wizard" in the Administration Guide. Upload the evaluation license file you have downloaded with your support portal account.

General connection settings

SPS supports transparent and non-transparent proxy operation modes to make deployments in existing network infrastructures as easy as possible. SPS will automatically handle non-transparent and transparent connections simultaneously.

Modes of operation

The following operation modes are possible:

Non-transparent proxy operation

This guide focuses on non-transparent proxy operation, which is the easiest to implement. In this configuration, clients connect to a server through SPS. That is, end-users address SPS explicitly, which then forwards connections to target systems based on various parameters depending on what destination selection method you select.

Figure 1: SPS in non-transparent mode

For an illustration of what happens when a client connects a server through SPS and how the different configuration options and policies of SPS affect this process, see:

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択