Desktop EPCS Authentication

ImprivataEnterprise Access Management supports Face Recognition for Windows desktop access, and also for:

Overview

The following configurations are required for Face Recognition. If you have already enabled Face Recognition for another EAM workflow, these steps do not need to be repeated; you only need to configure the workflow within user policy.

  • Configure an identity provider (IdP) to authenticate users to the Imprivata Hub.

  • Configure a connection to the Imprivata Cloud Platform.

  • If using an integration to Entra ID, sync your users with the Imprivata Cloud Platform.

    After configuring Entra ID and syncing users with the Imprivata Cloud Platform, verify that the users exist in the Imprivata Hub (access.imprivata.com).

  • Imprivata EAM also uses SCIM (System for Cross-domain Identity Management) to integrate with Active Directory and other non-Entra tenants to synchronize Imprivata EAM and the Imprivata Cloud Platform.

Requirements

  • Face recognition authentication requires an Authentication Management license and a Remote Access license.

  • Internet access is required for face recognition authentication. If the endpoint cannot connect with your Imprivata Cloud Platform, an error message will appear during authentication. The connection between the endpoint and your Imprivata appliance is not required.

  • A 1080p camera must be installed and enabled at the endpoint computer. Modern cameras capable of handling Zoom video conferencing are sufficient.

Configure an IdP to authenticate users to the Imprivata Hub

Configuring an IdP is required to authenticate administrators to the Imprivata Hub. You need access to theImprivata Hub to synchronize your Entra ID users with the Imprivata Cloud Platform.

NOTE:

If you have already configured access to the Imprivata Hub, you can skip this step.

You can configure:

  • Imprivata to function as an internal IdP.

    • Doing so creates a tenant-specific identity directory with a local administrator, which provides quick access to the Imprivata Hub without the need for an external IdP.

    • After configuring Imprivata as the IdP, you can configure an external IdP at any time.

  • Any external third-party IdP. For example, Microsoft Entra ID.

    • Configuring an external IdP lets you use your organization’s existing identity infrastructure to authenticate administrators.

    • Configuring Entra ID as an IdP has the added benefit of letting your non-administrative users enroll their face as an authenticator using My Imprivata Identity from any device. Unlike other enrollment methods, My Imprivata Identity does not require access to an endpoint where the Imprivata agent is installed.

Configure the Connection to the Imprivata Cloud Platform

Enabling Face recognition requires a connection to the Imprivata Cloud Platform. You need the following to complete the configuration:

  • Access to the Imprivata Appliance Console.

  • Access to the Imprivata Admin Console.

  • Optional — a PNG, JPG, or GIF of your organization logo (200 x 100 pixels or smaller, max 100KB).

NOTE:

If you have already configured a connection to the Imprivata Cloud Platform, you can skip this step. To determine if a connection has already been configured, log into the Imprivata Admin Console. The Status panel includes connection information. A green check mark for Access Management integration indicates a connection has been configured.

Configure Entra ID and sync your users with the Imprivata Cloud Platform

For Entra ID enterprises, additional Entra ID configuration is required to enable Face recognition.

For Active Directory-only enterprises, go to Configure SCIM Integration between EAM and ICP.

After configuring Entra ID and syncing users with the Imprivata Cloud Platform, verify that the users exist in the Imprivata Hub (access.imprivata.com). Complete the following steps.

SCIM Integration between EAM and ICP

Face authentication with Imprivata's Web authentication user interface is available for Imprivata EAM customers without synchronizing with Entra ID, through SCIM integration between EAM and the Imprivata Cloud Platform (ICP).

About SCIM Integration

SCIM (System for Cross-domain Identity Management) integration allows Imprivata EAM to automatically synchronize user lifecycle events (create, update, enable/disable, delete) with ICP.

With this integration, EAM now communicates with ICP through a standards-based identity API (SCIM v2), and pushes user lifecycle changes directly to ICP. Single-user changes are synchronized immediately; bulk user changes are queued and synchronized hourly.

SCIM or Entra Considerations

  • With the SCIM support, EAM enterprises that are Active Directory-only, and other non-Entra tenants, no longer need to connect Entra ID to their ICP environment to keep their user directories synchronized in ICP.

  • If a customer's ICP is synced with Entra ID, the SCIM integration will not be used.

  • SCIM  integration does not support hybrid configurations, where some users are synchronized with Entra ID, and some are Active Directory-only.

  • Enterprises whose users mainly use mobile devices would benefit from a Entra ID integration — SCIM integration does not support "inline" enrollment on mobile devices. Without the Entra ID integration, mobile device users must enroll their face at the Imprivata desktop before they can authenticate with face on their mobile device.

  • This integration is included with Imprivata EAM 26.2 and later. An Imprivata agent upgrade is not required. No additional software, library, or component needs to be installed in your enterprise.

Biometric Consent

In alignment with applicable law, Imprivata's facial recognition service requires users to provide their state or country of residence prior to using face recognition. As applicable by the location of their residence, they agree to one or more of the following:

  • Imprivata-provided biometric data terms and conditions.

  • In addition to the Imprivata-provided terms and conditions, your organization can provide its own notice and legal consent content for biometric use.

NOTE:

After the initial agreement, existing users are required to provide their state or country of residence annually. If required, they must agree to the Imprivata-provided and/or organization-specific terms and conditions for biometric use again to continue using face recognition.

To provide your own notice and/or legal consent content:

  1. Log in to the Imprivata Hub (access.imprivata.com).

  2. Click the gear icon > Customization > Biometric notice & legal consent.

  3. Based on your organization's requirements, upload a biometric consent document and/or a biometric notice document.

  4. If you uploaded a biometric consent document, select one or more locations where the consent is legally required.

  5. Click Save.

IMPORTANT:

Always consult your legal counsel before adding your own notice and legal consent content for biometric use at your organization.

Face Enrollment

Enroll during Login

  1. An unenrolled user clicks Use face at login. EAM attempts to match the face on camera with a user but does not find a match.

  2. To match the face on camera with a user, the user is prompted to enter their username.

  3. The user is then prompted to continue with inline Face enrollment, or enrollment at the enrollment utility.

Enroll with The Imprivata Agent

  1. From the Imprivata agent system tray, go to User Options and click Enroll Authentication Methods.

  2. Authenticate with username and password and click Enroll your face to begin the enrollment.

Enroll from Any Device

Users can access My Imprivata Identity from access.imprivata.com on any device.

Access to My Imprivata Identity requires that you configure Imprivata Access Management to use Entra ID as an IdP.

  1. The user authenticates to Imprivata Access Management from access.imprivata.com.

  2. They click their profile icon in the upper-right corner to open the user menu, and click My Imprivata Identity.

  3. From My Imprivata Identity, they click Add an authenticator > Face authentication.

BEST PRACTICE:

Imprivata Enterprise Access Management can authenticate users who are wearing masks. However, for best results, users should enroll their facial biometric without a mask on.

NOTE:

A user can delete their enrollment from the Imprivata agent in the system tray. Under User Options, they can click Enroll Authentication Methods > Face enrolled > Remove. An Imprivata Enterprise Access Management administrator can also remove the enrollment from the Users page (Users > Users) in the Imprivata Admin Console.

Face Recognition Settings

Opting Out of Face Enrollment

Before a user can use their face for authentication, they are required to complete a biometric agreement workflow. They are asked to provide their residence location, and may optionally be required to consent to certain terms and conditions before enrolling or authenticating with their face.

If the user declines consent, the user’s face is not enrolled and cannot use face authentication. The user will not be automatically prompted to enroll their face again.

The user's workflow continues, using other authentication methods (for example, PIN, password, or proximity card) associated with that workflow.

Enrolling Face Later

If the user wishes to enroll their face at a later date, they may open the EAM enrollment utility, select Face Recognition, complete the biometric agreement flow, and enroll their face.

Users who reside in a location where biometric consent is not required, and choose to not enroll their face, will continue to be prompted to enroll their face each time they attempt to use face authentication.

Prevent Duplicate Face Enrollments

Choose whether to block or allow the same face from being enrolled to multiple user accounts. When blocked, an enrolling user’s face is checked against faces already enrolled, and a duplicate enrollment is prevented.

In the Imprivata Hub, go to the gear icon > Hub security > Face recognition.

Camera Preview During Authentication

The Imprivata Hub provides controls over the onscreen camera preview during Face authentication:

In the Imprivata Hub, go to the gear icon > Hub security > Face recognition. The options are:

  • Hide the camera preview during face authentication

  • Allow users to show the camera preview for troubleshooting

  • Show the camera preview during face authentication

NOTE:

In the Imprivata Hub, go to the gear icon > Customization > Biometric notice & legal consent. On this page you can upload your organization's biometric consent and notice documents, and select the location(s) where consent is legally required.

Store Enrollment Photos

Imprivata administrators can control whether the photo captured during face enrollment is stored when enrollment is completed. This setting allows your enterprise to better support your  privacy or data-retention requirements.

The setting applies at the tenant level — it affects all applicable products and workflows for that tenant, not individual users.

NOTE:

This setting does not apply to Imprivata Patient Access.

To access this setting, in the Imprivata Hub, go to the gear icon > Hub security > Face recognition. Store enrollment photos is enabled by default.

  • With the setting off, the enrollment photo is used only to generate the biometric template needed for authentication, and is then immediately discarded.

  • With the setting on, the enrollment photo is used to generate the biometric template needed for authentication, and is then securely stored, subject to Imprivata's data retention policies.

Face Recognition and Security Lockout

Face Recognition includes the possibility of a user becoming locked out:

  • A user who fails to successfully authenticate 5 times in 5 minutes is blocked: they are prevented from attempting Face Recognition for five minutes. Inactivity timeouts during Face Recognition (15 seconds) count towards the failed attempt count.

  • A user who is blocked three times in a 24-hour period is locked out: they cannot attempt Face Recognition until an Administrator manually unlocks the user.