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.
Cloud Connection
Imprivata Services will enter the Enterprise ID and one-time cloud provisioning code required to establish trust between your Imprivata enterprise and the Imprivata cloud:
-
If you're not on the Cloud Connection page already: In the Imprivata Admin Console, click the gear icon > Cloud connection.
-
Click Test Connectivity.
-
Services will enter your Enterprise ID and cloud provisioning code.
-
Click Establish trust.
The cloud connection must be established by Imprivata Services.
Cloud Connection Status
You can review the status of your enterprise's connection to the Imprivata cloud at any time. Status notifications are displayed on the Imprivata Admin Console, and the cloud connection status of every appliance at every site is also available:
-
In the Imprivata Admin Console, go to the gear icon > Cloud connection.
-
Every appliance host is listed with its status. If there are problems with a connection, recommendations for resolving the problem are displayed here.
A SMTP server must be specified to send email notifications to administrators and end users.
To configure the connection:
-
In the Imprivata Admin Console, go to the gear icon > Settings.
-
In the Email configuration section, click SMTP Server > Modify.
-
SMTP Server — Type the IP address or FQDN of the mail server
-
Optional —By default, the Imprivata appliance secures outgoing email using TLS.
Uncheck Use TLS to disable this functionality. If you choose to leave TLS enabled, consider the following:
-
Imprivata supports TLS versions up to 1.2, but does not enforce any specific version. How your environment is configured determines the required version.
-
Your SMTP server must support TLS, and additional configuration may be required. For more information, see your vendor-specific documentation.
-
-
If required, type the SMTP Server Account Username and Password of an account that is authorized to send email through your server/mail relay.
-
Email messages are from — Enter the sender address.
- Click Save and activate.
The Test button only confirms that the connection can be made to the SMTP server. To test that an email can be sent and received, open the Users page. Select a user, click Notify, and select the type of notification to send as a test.
Feature Configuration
-
In the Imprivata Admin Console, go to Users > Workflow policy.
-
Go to Service desk verification and select authentication and verification method(s) required. Imprivata ID or SMS Code is the default.
-
Associate user policies with the workflow.
-
Optional — Enable Risk-Based Access. See Risk-Based Access.
-
Cilck Save.
Workflow During A Service Desk Call
-
A user calls the service desk. The service desk must confirm a caller's identity before providing support.
-
The service desk logs onto the Imprivata Admin Console. They go to Users > Users and search for the user who is calling.
-
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.)
-
The service desk admin clicks Verify. The Verify user identity page opens.
-
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.
-
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.
-
The service desk admin tells the caller to check for the message.
-
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.
-
The user completes the authentication, either with authentication methods configured in Workflow policy, or through Risk-Based Access.
-
A success screen appears, and they may close their browser window.
-
The verification success appears in the Verify user identity page, and the service call may continue.
All service desk verification events are recorded in the audit/event log for compliance and reporting purposes.