Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Adding custom fields to the card view

In card view, you can add additional search fields to the Search interface. This allows quick visualization of your preferred fields from the main page of the Search interface for each session.

Adding custom fields to the card view

  1. Click for more details and select Customize Card Fields from the list.

    Figure 268: Search — Customize Card Fields

  2. Select fields from Collapsed top and Collapsed bottom and the fields will be added as separate fields to the collapsed view of each session.

    The fields you select from Expanded top and Expanded bottom will be added to the expanded view of each session as shown in the figure below.

    Figure 269: Search — Preview

    NOTE: Some fields may not be available for every session. When the field is not available, for example, if you have data recorded by SPP, the field will be empty.

Table view

You can view sessions in a card, table or flow view. Click for more details and select from the list.

Figure 270: Search — Table view

Flow view

You can view sessions in a card, table or flow view. Click for more details and select from the list.

Figure 271: Search — Flow view

The flow view allows you to:

  • Quickly visualize the distribution of the sessions based on their various metadata, such as, client address, username, protocol, verdict, server address, and One Identity Safeguard for Privileged Analytics (SPA) score.

    The metadata of the sessions are presented as vertical bars and each bar represents the proportional value of the data.

    Example: Proportional data representation

    The Verdict column shows that most of the sessions failed, a large number were accepted, and the rest of the sessions fall into the category of AUTH_FAIL, and TERMINATED.

    Figure 272: Search > Flow view — proportional data representation

  • See at a glance the relationship between various metadata and identify patterns in user behavior.

    Example: Relationship between metadata

    You want to have an overview of activities where access was denied.

    A quick look at the Verdict column shows that there were several accesses where the authentication failed (AUTH_FAIL) and the lines from the AUTH_FAIL field point to several server addresses.

    Figure 273: Search > Flow view — relationship between metadata

  • Use it interactively to drill down further on information.

    To drill down on information, click on an item, then click Search.

    TIP: To exclude an item, press Ctrl while clicking the item.

    Example: Interactive drill down

    You want to investigate if there were any unusual activities. To take a closer look, in the Analytics Score column, click Unusual, then click Search.

    The flow view now only displays the unusual session activities. You can further narrow your search as required.

    Figure 274: Search > Flow view — interactive drill down

Search Permissions

The following describes how to assign users to access sessions only for connections for which they are granted permission.

Users need the Search privilege to access the Search interface.

Assigning the Search privilege to a user on the Users & Access Control > Appliance Access page, automatically enables the Search in all connections privilege, and grants the user access to every session, even if the user is not a member of the groups listed in the Access Control option of the particular connection policy.

Prerequisites

To assign users to access sessions only for connections for which they are granted permission

  1. Navigate to Users & Access Control > Appliance Access.

    Figure 275: Users & Access Control > Appliance Access — Configuring search privileges

  2. Assign the Search privilege to your usergroup as described in Assigning privileges to user groups for the One Identity Safeguard for Privileged Sessions (SPS) web interface.

  3. Deselect the Search in all connections privilege so that users can access sessions only for connections for which they are granted permission.

  4. To grant permission to a specific connection, navigate to the Connections page of the traffic (for example to SSH Control > Connections), and select the connection policy to modify.

    Figure 276: <Protocol name> Control > Connections > Access Control — Configuring search privileges

  5. Navigate to Access Control and click .

  6. Enter the name of the usergroup whose members are permitted to access the Search interface into the Authorizer Group field. This group must exist on the Users & Access Control > Local User Groups page.

    Caution:

    Usernames, the names of user lists, and the names of usergroups are case sensitive.

  7. Set the permissions of the usergroup.

    • If the usergroup can authorize (that is, enable) and audit (that is, monitor in real-time and download the audit trails) the sessions, select Permission > Follow&Authorize.

    • If the usergroup can only audit the sessions but cannot authorize, select Permission > Follow.

    NOTE: If the Client user is > Member of field is set, the auditor can only monitor the sessions of the specified usergroup. However, if Client user is > Member of field is set, the Auditor cannot access the Search page. To avoid this problem, add another Access Control rule for the Authorizer Group without setting the Client user isfield.

    The admin user of One Identity Safeguard for Privileged Sessions (SPS) can audit and authorize every connection.

Result

Users with the relevant privileges can now access the sessions for which they are granted permission. If users do not have the required permission to access sessions, a warning message is displayed and no session is visible as shown below:

Figure 277: Search — Permission denied

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation