Adaptive Authentication (Risk-Based Authentication), an advanced form of multi-factor authentication (MFA) is a process of selecting the right authentication factors depending on a user’s risk profile defined and tends to adapt the type of authorization factors. Adaptive authentication prompts Multi-Authentication Factors counting on the behavior, device IP, Geo-Location of the user which directly improves security level to the very best. Simply stated, the type of authentication methods get adapted based on real-time situations. Enabling Adaptive Authentication to any of your applications/websites lessens the security burden enforcing strong authentication where it's needed the foremost. Adaptive Authentication can be deployed in a way like:
Regardless of how you’ve defined your risk levels, adaptive authentication adapts to that risk level, enforcing the appropriate level of authentication for the given level of user risk.
In the Adaptive IP restriction method, the admin configures and enlists all IP addresses to allow or deny access. When a user tries to login into any of the applications configured with adaptive authentication, his IP address is checked against the configured IP list, and based on that the action is decided as per the configuration (.i.e. Allow, Deny or Challenge).
In this Device restriction Adaptive method, the admin allows end-users to add a fixed number of trusted devices for their account (A device here refers to a Browser Session). Once a device is registered for a user, then that user will be allowed to log in without any Restriction If the user's registered Device exceeds the total registered device limit specified by the admin, in that case, the user will be either Challenged or Denied as specified in the policy by the admin.
In Location-based Adaptive restriction, the admin shortlist and configure a list of Geo-locations where they want to allow end-users to either login or deny based on the location set by the admin. When a user tries to login with adaptive authentication enabled, his Location Attributes such as (Latitude, Longitude, and Country Code) are verified against the Location list configured by the admin, and based on this user will be either allowed, challenged, or denied.
Time Restriction configuration starts with admin configuring a time zone with Start and End Time’s for that time zone and users are either allowed, denied, or challenged based on the condition in the policy. When an end-user tries to login with the adaptive authentication enabled, his time zone-related attributes such as Time-Zone and current System time are verified against the list configured by the admin, and based on the configuration the user is either allowed, denied, or challenged.
When you decide to implement Adaptive (Risk-based) Authentication in your organization, you need to define basic login requirements for users or a user group. These requirements may vary user by user based on location, role, and resource value risk. Adaptive authentication starts with creating a profile for each user or user group, which includes info around the user's geographical location, registered devices, role, and more. Each time a user tries to authenticate, the request is evaluated and assigned a risk score. Depending on the risk score, the user may be required to provide additional authentication factors to prove the identity. For example, if a user tries to access applications via an unregistered device, they may be prompted to register it. If the user logs in from a geographical location other than their office, they may have to answer a security question. Adaptive MFA determines the response to requests with different risk scores. In any given scenario, the user may be allowed to authenticate, may be prevented from accessing, or may even be challenged to prove his or her identity.