Chatee ahora con Soporte
Chat con el soporte

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

Managing One Identity Safeguard for Privileged Sessions (SPS) users locally

By default, One Identity Safeguard for Privileged Sessions (SPS) users are managed locally on SPS. To add local users in SPS, complete all steps of the following procedure:

  1. Create users.

    For detailed instructions on how to create local users, see Creating local users in One Identity Safeguard for Privileged Sessions (SPS).

  2. Assign users to groups.

    For details about how to add a usergroup, see Managing local user groups.

  3. Assign privileges to groups.

    For information on how to control the privileges of usergroups, see Managing user rights and usergroups.

Creating local users in One Identity Safeguard for Privileged Sessions (SPS)

This section describes how to create local users.

NOTE: The admin user is available by default, and has all possible privileges. It is not possible to delete this user.

When using RADIUS authentication together with local users, the users are authenticated to the RADIUS server, only their group memberships must be managed locally on One Identity Safeguard for Privileged Sessions (SPS). For details, see Authenticating users to a RADIUS server.

To create a local user

  1. Navigate to Users & Access Control > Local Users and click .

    Figure 82: Users & Access Control > Local Users — Creating local users

  2. Enter the username in the User field.

    NOTE: For the username of SSH users, only valid UTF-8 strings are allowed.

    The following characters cannot be used in usernames: <>\/[]:;|=,+*?

  3. Enter a password for the user in the Password and Verify password fields.

    The strength of the password is indicated below the Password field, as you type. To set a policy for password strength, see Setting password policies for local users. The user can change the password later from the SPS web interface, and you can modify the password of the user here.

    Use strong passwords: at least 8 characters that include numbers, letters, special characters, and capital letters. For local One Identity Safeguard for Privileged Sessions (SPS) users, require the use of strong passwords (set Users & Access Control > Login options > Minimal password strength to strong). For more information, see "Setting password policies for local users" in the Administration Guide.

    NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:

    • Letters A-Z, a-z

    • Numbers 0-9

    • The space character

    • Special characters: !"#$%&'()*+,-./:;<>=?@[]\^-`{}_|

    NOTE: If possible, use a random password generator.

    To create a strong password:

    • Use special characters

    • Use long passwords

    • Mix uppercase and lowercase letters

    For strong passwords, do not use:

    • Personal information in the passwords

    • Sequential letters or numbers

    • The word password as the password

    • Keyboard paths (for example, qwerty)

  4. Click in the Groups section and select a group that the user will be a member of. Repeat this step to add the user to multiple groups.

    You can also modify the group membership of local users here.

    To remove a user from a group, click next to the group.

  5. To save the modifications, click Commit.

Deleting local users from One Identity Safeguard for Privileged Sessions (SPS)

This section describes how to delete local users from One Identity Safeguard for Privileged Sessions (SPS).

To delete a local user from SPS

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

  2. Find the user you want to delete.

  3. Click next to the user, at the right edge of the screen.

  4. To save your modifications, click Commit.

Setting password policies for local users

One Identity Safeguard for Privileged Sessions (SPS) can use password policies to enforce the use of:

  • Password history

  • Password strength

  • Password length

  • Password expiry

  • Cracklib protection

Limitations

Consider the following limitations when configuring password policies:

  • Password policies apply only to locally managed users.

  • Password policies do not apply to users managed from an LDAP database, or authenticated to a RADIUS server.

NOTE: SPS accepts passwords that are not longer than 150 characters and supports the following characters:

  • Letters A-Z, a-z

  • Numbers 0-9

  • The space character

  • Special characters: !"#$%&'()*+,-./:;<>=?@[]\^-`{}_|

To edit a password policy

  1. Navigate to Users & Access Control > Login options.

  2. Under Login Options, select the Built-in Local login method and click Edit.

    NOTE: Only the local users are affected by the password policy. The password rules of LDAP and RADIUS authentication are not managed by SPS.

    Figure 83: Users & Access Control > Login options — Configuring password policies

  3. (Optional) To do a basic dictionary check on passwords, enable Cracklib protection.

  4. In the Expire after text box, configure the validity period of passwords (in days). Once the configured period expires, SPS users must change their passwords. The value range is 1-365. You can also disable the password expiration.

  5. Reject reusing previous passwords: use this option to prevent using the same password again for the configured number of password changes. For example, if the value is set to 10, the users must use 10 different passwords consecutively, until the first password can be used again. The acceptable values are 1-30. To disable this option, select Enable reusing passwords.

  6. Set the required password complexity level in Password strength. The available values are disabled, good, and strong.

    NOTE: The strength of a password is determined by its length and complexity: the variety of numbers, letters, capital letters, and special characters used.

    To run simple dictionary-based attacks to find weak passwords, enable Cracklib (eg. dictionary) protection.

  7. In Password length, set the minimum number of characters for the passwords. The acceptable values are 1-99.

  8. In the Script reference text box, specify a unique, human readable ID for referencing the configured settings in scripts (for example, to enable the REST API clients to select the login method).

  9. To save your modifications, click Commit.

    NOTE: The changes you make in the password policy do not affect existing passwords. However, configuring password expiration will require every user to change their password after the expiration date. Also, new passwords must comply with the current password strength settings.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación