Authentication mechanisms

You can select the authentication mechanisms that will be available to users. However, the mechanisms offered to users on the login prompt depend on the user account’s properties. For example, if you select all of the mechanisms in a challenge column but a user only has a password and email address, then the login drop-down menu only offers those two options.

Some authentication mechanisms require additional configurations before users can authenticate using those mechanisms. Make sure your users complete the configuration requirements for any mechanism you plan to use. Refer to Secure access with adaptive MFA for more detail.

To set the authentication mechanisms, see Create authentication profiles.

Refer to the following table for a description of available authentication mechanisms.

Authentication mechanism

Description

Something you have

Mobile Authenticator

When you select this option, users authenticate using a one-time passcode displayed by the CyberArk Identity mobile app installed on their mobile devices.

If devices are connected via the cell network or a wi-fi connection, users can send the passcodes from the devices. If the devices are not connected, users must manually enter the passcodes into the CyberArk Identity mobile app login prompt.

If devices are connected via the cell network or a wi-fi connection, users can send the passcodes from the devices. If the devices are not connected, users must manually enter the passcodes into the Admin Portal or CyberArk Identity user portal login prompt.

The availability of this mechanism to users can be controlled using the Show Mobile Authenticator by default policy. This policy is in Core Services > Policies > select existing policy or create a new one > Endpoint Policies > Common Mobile Settings > Security Settings. Mobile device configuration policies overview for more information on the policy.

This option requires users to have CyberArk Identity mobile app installed on their devices and those devices must be enrolled in CyberArk Identity.

The following video illustrates how to enable users to use the CyberArk Identity mobile app as a mobile authenticator.

Phone call

When you select this option, CyberArk Identity calls the user using the stored phone number (mobile or land line) and describes an action the user must perform to complete the authentication. The user completes the action from the device to log in. If your tenant is configured on CyberArk Identity 17.10 or newer, see Enable phone PIN because additional configuration is required.

This option is disabled for new tenants by default. Contact your account representative to enable this authentication mechanism.

OATH OTP Client

This text string is configurable and reflects what you entered during the OATH OTP configuration. When you select this option, users can use a third party authenticator (like Google Authenticator) to scan a CyberArk Identity generated QR code and get a one-time-passcode (OTP). This authentication mechanism requires additional configurations. See Enable OATH OTP.

Text message (SMS) confirmation code

When you select this option, CyberArk Identity sends a text message to the user’s mobile phone with a one-time confirmation code and/or an authentication link. Depending on the language setting, some languages display only the confirmation code while others display the confirmation code and link. Users who are connected to the Internet can click/tap the link. Otherwise, they need to enter the confirmation code in the login prompt.

This option is disabled for new tenants by default. Contact your account representative to enable this authentication mechanism.

You can configure the confirmation code length (6 or 8 digits) in Admin PortalSettings > Authentication > Security Settings > Email and SMS passcode length drop down option. The default is 8 digits.

The link and confirmation code are valid for 20 minutes. If a user does not respond within this time period, the CyberArk Identity cancels the login attempt.

Additionally, you can configure CyberArk Identity to allow users to click a Send SMS again link to request a new SMS text message if the user doesn't receive the initial message in a specified period of time. You can configure this in Admin Portal > Core Services > Policies > Authentication Policies > CyberArk Identity > Other Settings.

To ensure delivery of SMS messages, CyberArk Identity uses a backup SMS provider and cycles through the providers on SMS retry attempts.

Duo

Select this option to use Duo as an authentication factor. For example, if you already use Duo for authentication to other applications, you can continue to use it with CyberArk Identity as well. If you select Duo, the authentication process provides an opportunity for users to configure their devices to use Duo, if they haven't already done so.

You have to configure Duo in your CyberArk Identity tenant before you can select it as a authentication mechanism. Refer to Duo authentication for more information.

Email confirmation code

When you select this option, CyberArk Identity sends a confirmation code and a link to the user’s email address. Users who are connected to the Internet can click/tap the link. Otherwise, they need to enter the confirmation code in the login prompt.

You can configure the confirmation code length (6 or 8 digits) in Admin PortalSettings > Authentication > Security Settings > Email and SMS passcode length drop down option. The default is 8 digits.

The link and confirmation code are valid for 20 minutes. If a user does not respond within this time period, the CyberArk Identity cancels the login attempt.

QR Code

Select this option to present users with a Quick Response (QR) Code that they can scan with the CyberArk Identity mobile app on an enrolled mobile device.

Successfully scanning a QR Code bypasses other authentication mechanisms when it's selected under Single Authentication Mechanism.

FIDO2 Authenticator(s) (single factor)

FIDO2 is an authentication standard hosted by FIDO Alliance. This standard includes the Web Authentication ("WebAuthn") API, which is a specification written by the World Wide Web Consortium (W3C) and FIDO, with participation from additional third parties. The WebAuthn API is backward compatible with Universal 2nd Factor (U2F) keys.

CyberArk leverages the WebAuthn API to enable passwordless authentication to the CyberArk Identity using either external or on-device authenticators.

Single-factor FIDO2 authenticators are something you have. Examples are external authenticators like security keys that you plug into the device's USB port; for example, a YubiKey.

Refer to NIST 800-63b for more information about single-factor cryptographic devices.

FIDO2 authenticator(s) are either on-device or external security keys that provide passwordless authentication.

Something you are

FIDO2 Authenticator(s) (multi-factor)

FIDO2 is an authentication standard hosted by FIDO Alliance. This standard includes the Web Authentication ("WebAuthn") API, which is a specification written by the World Wide Web Consortium (W3C) and FIDO, with participation from additional third parties. The WebAuthn API is backward compatible with Universal 2nd Factor (U2F) keys.

CyberArk leverages the WebAuthn API to enable passwordless authentication to the CyberArk Identity using either external or on-device authenticators.

Supported multi-factor FIDO2 authenticators are something you are. Popular examples are biometric authenticators integrated into device hardware, such as Mac Touch ID, Windows Hello, and fingerprint scanners.

Refer to NIST 800-63b for more information about multi-factor cryptographic devices.

FIDO2 authenticator(s) are either on-device or external security keys that provide passwordless authentication.

Something you know

 

Password

When you select this option, users are prompted for either their Active Directory or CyberArk Identity user password when logging in to the Admin portal.

Security Question(s)

When you select this option, users are prompted to answer user-defined and/or admin-defined security questions. When creating the authentication profile, you can specify the number of questions users must answer. You can also specify the number of user-defined and admin-defined questions available to users. See Enable and configure Security Questions. Users create, select, or change the question and answer from their Account page in the user portal.

Other

3rd Party RADIUS Authentication

When you select this option, we communicate with your RADIUS server to allow for user authentication into CyberArk Identity or an enrolled endpoint. See Configure CyberArk Identity for RADIUS.