Service Desk Verification From Imprivata

The Verify Identity feature in each user record provides an authentication workflow within the Imprivata Admin Console when your IT service desk must confirm a caller's identity before providing support. This protects against social engineering attacks where a bad actor impersonates a legitimate user.

To configure Service Desk Verification from the ServiceNow app, see Service Desk Verification From ServiceNow.

Requirements

  • The Advanced and Passwordless Access license.

  • A connection to the Imprivata Cloud Platform.

  • Your SMTP server must be configured to send the link for identity verification by email.

  • To receive the link for identity verification by SMS, the user must have a mobile phone number in their user record (Active Directory or Entra ID), or a mobile number already enrolled for SMS authentication.

  • An Imprivata Super Administrator must configure the service desk verification settings, or grant an administrator role access to these settings. In the Administrator Roles page, select the Verify user for Service desk role for an Administrator. See Administrator Roles (Delegated Administration).

  • Staff answering calls to the service desk who need to use this feature must have access to the Imprivata Admin Console.

  • The user's record must include a phone number or an email address, either synchronized from Active Directory, or enrolled for email authentication.  See Set Up Enterprise.

  • The user must have the required authentication methods enrolled.

Feature Configuration

  1. In the Imprivata Admin Console, go to Users > Workflow policy.

  2. Go to Service desk verification and select authentication and verification method(s) required. Imprivata ID or SMS Code is the default.

  3. Associate user policies with the workflow.

  4. Optional — Enable Risk-Based Access. See Risk-Based Access.

  5. Cilck Save.

Workflow During A Service Desk Call

  1. A user calls the service desk. The service desk must confirm a caller's identity before providing support.

  2. The service desk logs onto the Imprivata Admin Console. They go to Users > Users and search for the user who is calling.

  3. The user(s) listed in the search results will include a Verify link if the user details include mobile phone number or email address — either from Active Directory, or enrolled as an authentication method. (If the user is listed but the Verify link is not present, the service desk cannot use this workflow to verify their identity.)

  4. The service desk admin clicks Verify. The Verify user identity page opens.

  5. The service desk admin selects a delivery method and clicks Send verification request.

    BEST PRACTICE:

    When selecting an email address, send the message to the address associated with your enterprise domain, when available.

    After the request is sent, a progress bar appears onscreen.

  6. An email or SMS is sent to the user. The message "Please verify your identity" includes a link they must click (the link expires in 30 minutes).

    IMPORTANT:

    The service desk is notified that an SMS was requested, but does not receive notification that it was delivered.

  7. The service desk admin tells the caller to check for the message.

  8. The user opens the message. When the user clicks the link in the message, a browser window opens with the user interface common to many Imprivata authentication workflows.

  9. The user completes the authentication, either with authentication methods configured in Workflow policy, or through Risk-Based Access.

  10. A success screen appears, and they may close their browser window.

  11. The verification success appears in the Verify user identity page, and the service call may continue.

NOTE:

All service desk verification events are recorded in the audit/event log for compliance and reporting purposes.