One Identity Safeguard for Privileged Sessions 5.7.0 - Duo Multi-Factor Authentication - Tutorial

Introduction

This document describes how you can use the services of Duo to authenticate the sessions of your privileged users with One Identity Safeguard for Privileged Sessions (Safeguard for Privileged Sessions).

One Identity Safeguard for Privileged Sessions:

One Identity Safeguard for Privileged Sessions (Safeguard for Privileged Sessions) controls privileged access to remote IT systems, records activities in searchable, movie-like audit trails, and prevents malicious actions. Safeguard for Privileged Sessions 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.

Safeguard for Privileged Sessions acts as a central authentication gateway, enforcing strong authentication before users access sensitive IT assets. Safeguard for Privileged Sessions 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 Safeguard for Privileged Sessions'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 Duo (or another multi-factor authentication provider), Safeguard for Privileged Sessions directs all connections to the authentication tool, and upon successful authentication, it permits the user to access the information system.

Integrating Duo with Safeguard for Privileged Sessions:

Safeguard for Privileged Sessions can interact with your Duo 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 Duo, Safeguard for Privileged Sessions directs all connections to the Duo 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 Safeguard for Privileged Sessions. If the Duo Mobile app is installed on the user's device (smartphone, notebook, smartwatch, and so on), the user can generate a one-time password on the device. This will be used for the 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.

Meet compliance requirements

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 Safeguard for Privileged Sessions and Duo 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.

How Safeguard for Privileged Sessions and Duo MFA work together

Figure 1: How Safeguard for Privileged Sessions and Duo work together

  1. A user attempts to log in to a protected server.

  2. Gateway authentication on Safeguard for Privileged Sessions

    Safeguard for Privileged Sessions receives the connection request and authenticates the user. Safeguard for Privileged Sessions 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.

  3. Outband authentication on Duo

    If gateway authentication is successful, Safeguard for Privileged Sessions connects the Duo server to check which authentication factors are available for the user. Then Safeguard for Privileged Sessions requests the second authentication factor from the user.

    • For OTP-like authentication factors, Safeguard for Privileged Sessions requests the one-time password (OTP) from the user, and sends it to the Duo server for verification.

    • For the Duo push notification factor, Safeguard for Privileged Sessions asks the Duo server to check if the user successfully authenticated on the Duo server.

  4. If multi-factor authentication is successful, the user can start working, while Safeguard for Privileged Sessions records the user's activities. (Optionally, Safeguard for Privileged Sessions 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.)

Technical requirements

In order to successfully connect Safeguard for Privileged Sessions with Duo, you need the following components.

In Duo:
  • A valid Duo subscription that permits multi-factor authentication.

  • Your users must be enrolled in Duo and their access must be activated.

  • The users must install the Duo Mobile app.

In Safeguard for Privileged Sessions:
  • A One Identity Safeguard for Privileged Sessions appliance (virtual or physical), at least version 5 F1.

  • A copy of the Safeguard for Privileged Sessions Duo plugin. This plugin is an Authentication and Authorization (AA) plugin customized to work with the Duo multi-factor authentication service.

  • Safeguard for Privileged Sessions must be able to access the Internet (at least the API services). Since Duo is a cloud-based service provider, Safeguard for Privileged Sessions must be able to access its web services to authorize the user.

    The connection also requires the ikey, skey, and host parameters:

    1. Log on to the Duo Admin Panel interface and navigate to Applications.

    2. Click Protect an Application and locate Web SDK in the applications list.

    3. Click Protect this Application to get your integration key (ikey), secret key, (skey), and API hostname (host). For details, see Getting Started with Duo Security.

  • Depending on the factor you use to authenticate your users, your users might need Internet access on their cellphones.

Availability and support of the plugin

The Safeguard for Privileged Sessions Duo plugin is available as-is, free of charge to every Safeguard for Privileged Sessions customer from the Plugin Page. In case you need any customizations or additional features, contact professionalservices@balabit.com.

You can use the plugin on Safeguard for Privileged Sessions 5 F5 and later. If you need to use the plugin on Safeguard for Privileged Sessions 5 LTS, contact professionalservices@balabit.com.

How Safeguard for Privileged Sessions and Duo work together in detail

  1. A user attempts to log in to a protected server.

  2. Gateway authentication on Safeguard for Privileged Sessions

    Safeguard for Privileged Sessions receives the connection request and authenticates the user. Safeguard for Privileged Sessions 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.

  3. Check if the user is exempt from multi-factor authentication

    You can configure Safeguard for Privileged Sessions using whitelists and blacklists to selectively require multi-factor authentication for your users, for example, to create break-glass access for specific users.

    • If multi-factor authentication is not required, the user can start working, while Safeguard for Privileged Sessions records the user's activities. The procedure ends here.

    • If multi-factor authentication is required, Safeguard for Privileged Sessions continues the procedure with the next step.

    For details on creating exemption lists, see Safeguard for Privileged Sessions Duo plugin parameter reference.

  4. Determining the Duo username

    If the gateway usernames are different from the Duo usernames, you must configure the Safeguard for Privileged Sessions Duo plugin to map the gateway usernames to the Duo usernames. The mapping can be as simple as appending a domain name to the gateway username, or you can query an LDAP or Microsoft Active Directory server. For details, see Mapping Safeguard for Privileged Sessions usernames to Duo identities.

  5. Outband authentication on Duo

    If gateway authentication is successful, Safeguard for Privileged Sessions connects the Duo server to check which authentication factors are available for the user. Then Safeguard for Privileged Sessions requests the second authentication factor from the user.

    • For OTP-like authentication factors, Safeguard for Privileged Sessions requests the OTP from the user, and sends it to the Duo server for verification.

    • For the Duo push notification factor, Safeguard for Privileged Sessions asks the Duo server to check if the user successfully authenticated on the Duo server.

  6. If multi-factor authentication is successful, the user can start working, while Safeguard for Privileged Sessions records the user's activities. (Optionally, Safeguard for Privileged Sessions 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.)

  7. If the user opens a new session within a short period, they can do so without having to perform multi-factor authentication again. After this configurable grace period expires, the user must perform multi-factor authentication to open the next session. For details, see Safeguard for Privileged Sessions Duo plugin parameter reference.

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

Please note our Privacy Policy recently changed to support GDPR. You may read it here. Continuing to use our website indicates you have accepted the new policy.