This tutorial describes the deprecated version of the plugin.
To upgrade your deprecated plugin for One Identity Safeguard for Privileged Sessions 6.0, see Upgrading plugins for One Identity Safeguard for Privileged Sessions version 6.0.
This document describes how you can use the services of inWebo to authenticate the sessions of your privileged users with One Identity Safeguard for Privileged Sessions (SPS).
One Identity Safeguard for Privileged Sessions (SPS) controls privileged access to remote IT systems, records activities in searchable, movie-like audit trails, and prevents malicious actions. SPS is a quickly deployable enterprise device, completely independent from clients and servers — integrating seamlessly into existing networks. It captures the activity data necessary for user profiling and enables full user session drill down for forensic investigations.
SPS acts as a central authentication gateway, enforcing strong authentication before users access sensitive IT assets. SPS can integrate with remote user directories to resolve the group memberships of users who access nonpublic information. Credentials for accessing information systems can be retrieved transparently from SPS's local credential store or a third-party password management system. This method protects the confidentiality of passwords as users can never access them. When used together with inWebo (or another multi-factor authentication provider), SPS directs all connections to the authentication tool, and upon successful authentication, it permits the user to access the information system.
SPS can interact with your inWebo account and can automatically request strong multi-factor authentication for your privileged users who are accessing the servers and services protected by PSM. When used together with inWebo, SPS directs all connections to the inWebo tool, and upon successful authentication, it permits the user to access the information system.
The integration adds an additional security layer to the gateway authentication performed on SPS. If the inWebo Authenticator App is installed on the user's device (smartphone, notebook, and so on), the user can generate a one-time password on the device. This will be used for authentication to the One Identity platform. This way, the device turns into a two-factor authentication token for the user. The one-time password is changed after every authentication and is generated using dynamic keys.
ISO 27001, ISO 27018, SOC 2, and other regulations and industry standards include authentication-related requirements, for example, multi-factor authentication (MFA) for accessing production systems, and the logging of all administrative sessions. In addition to other requirements, using SPS and inWebo helps you comply with the following requirements:
PCI DSS 8.3: Secure all individual non-console administrative access and all remote access to the cardholder data environment (CDE) using multi-factor authentication.
PART 500.12 Multi-Factor Authentication: Covered entities are required to apply multi-factor authentication for:
Each individual accessing the covered entity’s internal systems.
Authorized access to database servers that allow access to nonpublic information.
Third parties accessing nonpublic information.
NIST 800-53 IA-2, Identification and Authentication, network access to privileged accounts: The information system implements multi-factor authentication for network access to privileged accounts.
Figure 1: How SPS and inWebo work together
A user attempts to log in to a protected server.
SPS receives the connection request and authenticates the user. SPS can authenticate the user to a number of external user directories, for example, LDAP, Microsoft Active Directory, or RADIUS. This authentication is the first factor.
If gateway authentication is successful, SPS connects the inWebo server to check which authentication factors are available for the user. Then SPS requests the second authentication factor from the user.
For OTP-like authentication factors, SPS requests the one-time password (OTP) from the user, and sends it to the inWebo server for verification.
For the inWebo push notification factor, SPS asks the inWebo server to check if the user successfully authenticated on the inWebo server.
If multi-factor authentication is successful, the user can start working, while SPS records the user's activities. (Optionally, SPS can retrieve credentials from a local or external credential store or password vault, and perform authentication on the server with credentials that are not known to the user.)
In order to successfully connect SPS with inWebo, you need the following components.
A valid inWebo subscription that permits multi-factor authentication.
Your users must be enrolled in inWebo and their access must be activated.
The users must install the inWebo mobile app.
A One Identity Safeguard for Privileged Sessions appliance (virtual or physical), at least version 5 F1.
A copy of the SPS inWebo plugin. This plugin is an Authentication and Authorization (AA) plugin customized to work with the inWebo multi-factor authentication service.
SPS must be able to access the Internet (at least the services on api.myinwebo.com). Since inWebo is a cloud-based service provider, SPS must be able to access its web services to authorize the user.
The connection also requires the Service ID that is displayed on the inWebo Administration interface under the Service Users tab.
Generate and download an X.509 certificate and store it in the credential store:
In the inWebo Administration interface, navigate to Secure Sites and click Download a new certificate for the API. Configure the parameters (Authentication: Yes, Provisioning: No) and click Download.
Decrypt the downloaded X.509 certificate with the following command: openssl rsa -in <certificate-file-name>.crt. Enter the required passphrase. The decrypted part of the certificate is displayed on the console screen.
Copy the decrypted part from -----BEGIN RSA PRIVATE KEY----- to -----END RSA PRIVATE KEY-----, open the <certificate-file-name>.crt and replace the encrypted part with the copied decrypted part from -----BEGIN ENCRYPTED PRIVATE KEY----- to -----END ENCRYPTED PRIVATE KEY-----.
Depending on the factor you use to authenticate your users, your users might need Internet access on their cellphones.
SPS supports AA plugins in the RDP, SSH, and Telnet protocols.
In RDP, using an AA plugin together with Network Level Authentication in a Connection Policy has the same limitations as using Network Level Authentication without domain membership. For details, see "Network Level Authentication without domain membership" in the Administration Guide.
In RDP, using an AA plugin requires TLS-encrypted RDP connections. For details, see "Enabling TLS-encryption for RDP connections" in the Administration Guide.
The SPS inWebo plugin is available as-is, free of charge to every SPS customer from the Plugin Page. In case you need any customizations or additional features, contact our Professional Services Team.
You can use the plugin on SPS 5 F4 and later. If you need to use the plugin on SPS 5 LTS, contact our Professional Services Team.