立即与支持人员聊天
与支持团队交流

One Identity Safeguard for Privileged Sessions 7.2 - 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

Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown

To reboot or shut down One Identity Safeguard for Privileged Sessions (SPS)

  1. Navigate to Basic Settings > System > System control > This node.
  2. Click the respective action button.

The Other node refers to the secondary node of a High Availability SPS cluster. For details on High Availability clusters, see Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster.

Caution:
  • When rebooting the nodes of a cluster, reboot the other (secondary) node first to avoid unnecessary takeovers.

  • When shutting down the nodes of a cluster, shut down the other (secondary) node first. When powering on the nodes, start the primary node first to avoid unnecessary takeovers.

  • When both nodes are running, avoid interrupting the connection between the nodes: do not unplug the Ethernet cables, reboot the switch or router between the nodes (if any), or disable the HA interface of SPS.

Figure 109: Basic Settings > System > System Control — Performing basic management

NOTE: Web sessions to the SPS interface are persistent and remain open after rebooting SPS, so you do not have to relogin after a reboot.

During the reboot process, SPS displays information about the progress of the reboot and any possible problems in the following places:

  • On the web interface of SPS, at any of the Listening addresses configured at Basic settings > Local Services > Web login (admin and user). (After booting, you are directed to the login screen of SPS.)

  • On the console, which you can monitor with IPMI (ILOM) or console access.

The information displayed in the browser and on the console is the same.

Disabling controlled traffic

This section describes how to temporarily disable some or all of the controlled traffic to the protected servers.

Figure 110: Basic Settings > System > Traffic control — Disabling the controlled traffic

Caution:

Using the Stop option of the respective traffic types on Basic Settings > System > Traffic control disables the traffic only temporarily. Committing specific changes on the SPS web interface enables the connections again. For details on how to permanently disable a type of traffic, see Disabling controlled traffic permanently.

NOTE: Disabling the traffic affects only the traffic configured in the Connection policies. Other network traffic (such as web management, DNS, LDAP, SNMP, SMTP, and so on) can pass SPS even if all traffic is disabled. For details on configuring Connection policies, see General connection settings.

To temporarily disable some or all of the controlled traffic to the protected servers

  1. Navigate to Basic Settings > System > Traffic control.

  2. To disable any of the supported traffic types, click Stop in the respective traffic field. You can disable the following traffic types on this page:

    • HTTP

    • ICA

    • MSSQL

    • RDP

    • SSH

    • Telnet

    • VNC

    • Sudo iolog

    • All services

    NOTE: Disabling SSH traffic also disables all other traffic forwarded in SSH, for example X11.

    Disabling Telnet also disables TN3270 traffic.

    The Traffic overview under About displays the status of all traffic types.

Disabling controlled traffic permanently

NOTE: Disabling the traffic affects only the traffic configured in the Connection policies, other traffic can pass SPS even if the all traffic is disabled. For details on configuring Connection policies, see General connection settings.

To disable controlled traffic permanently

  1. Figure 111: <Protocol name> Control > Global Options — Disabling the controlled traffic persistently

    Navigate to the Global Options page of the traffic type you want to disable, for example to SSH Control > Global Options to disable SSH traffic.

  2. Set the Traffic > Service field to disabled.

  3. Click .

Managing One Identity Safeguard for Privileged Sessions (SPS) clusters

When you have a set of two or more One Identity Safeguard for Privileged Sessions (SPS) instances in your deployment, you can join them into a cluster. This has several advantages. You can:

  • Manage the nodes from one central location.

  • Monitor their status and update their configuration centrally.

  • Search all session data recorded by all nodes in the cluster on a single node.

  • Scale the performance of the cluster by adding new nodes and joining them to the cluster easily.

  • Extend auditing to other networks by adding new nodes to the cluster and joining them to the cluster.

This is achieved by assigning roles to the individual nodes in your cluster: you can set one of your SPS nodes to be the Central management node and the rest of the nodes are managed from this central node.

NOTE: Consider the following:

  • All nodes in a cluster must run the same version of SPS.

  • One Identity recommends managing not more than a few tens of instances from the Central management node.

  • Nodes in the cluster connect to each other using IPsec.

You can configure your One Identity Safeguard for Privileged Sessions (SPS) cluster in the following ways:

  • Configuration synchronization without a central search: This method allows you to perform your configuration settings on your Central management node. Managed host nodes periodically fetch and merge the settings into their own: this is called "configuration synchronization". Central search is not configured in this method, so you can search for sessions on each node, including the Central management node.

    For more information on this method, see Configuration synchronization without a central search.

  • Central search with configuration synchronization: This method allows you to use a Central management node with a Search master role to view session data recorded by the minion nodes of your cluster, as well as manage all the nodes in the cluster from one central location.

    For more information on this method, see Central search with configuration synchronization.

    IMPORTANT: One Identity does not recommend having a central search configuration without configuration synchronization.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级