Authentication Strength Maps
Authentication strength maps are policy configurations that define which authentication methods are available for different levels of access risk. Administrators can use them to align authentication options with access scenarios involving particular users, devices, applications, locations, networks, and resources. For example, a badge tap may be acceptable for accessing a shared workstation in a controlled environment but not for signing in to a tablet that contains sensitive information. This approach helps organizations apply stronger controls when risk is higher without adding unnecessary friction to every access attempt.
Authentication strength maps can support risk-based access across desktop access, web SSO, remote access, and self-service password reset workflows. Administrators can assign acceptable authentication methods to low-, medium-, and high-risk scenarios. For example, a policy might allow a badge tap for a lower-risk workstation login, require biometric authentication to access a more sensitive application, or require multiple authentication factors for remote access. These policies can help IT teams apply consistent controls across different environments. So, which authentication options are safe for mobile devices and other endpoints? To determine this, an authentication strength test can assess whether an authentication method or configuration meets a particular security requirement or compliance need, but an authentication strength map goes further by defining which methods are available in specific access scenarios in the context of certain permissions.
Authentication requirements may differ according to a person’s role, permissions, and immediate need. What are examples of authentication requirements?
- A frontline worker may use a badge tap or biometric authentication to access a shared workstation
- An administrator with elevated permissions may need two or more authentication factors to access sensitive systems
- A user accessing sensitive information through remote access may need stronger verification than when working inside a trusted facility
- A user resetting a forgotten password may need identity verification before creating a new credential
- A contractor may be limited to specific applications and required to use a stronger authentication method when connecting from an unmanaged device
By mapping authentication strength requirements to access conditions, organizations can reduce reliance on one-size-fits-all policies and avoid treating every login as equally risky. Secure authentication software can help enforce these rules across applications, devices, and workflows while allowing greater visibility and control over access management for IT teams. It can also help administrators manage permissions to systems easily by associating authentication requirements with the resources and actions each user is authorized to access.
Imprivata Enterprise Access Management (EAM) provides customizable authentication strength maps for risk-based access. Administrators can define which authentication methods are allowed for low-, medium-, and high-risk access across desktop access, web SSO, remote access, and self-service password reset workflows. By requiring stronger authentication when risk is higher and reducing friction for lower-risk activities, EAM helps organizations support secure, practical access across the environments where work happens.