Adaptive Authentication , an advanced form of Multi-Factor authentication 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 also known as Risk-Based Authentication prompts for Multi- Factor Authentication (MFA) based on the user's behaviour, device IP, and geo-location, resulting in the highest degree of protection. Simply stating, adaptive authentication techniques are changed based on real-time circumstances. Enabling Adaptive Authentication to any of your enterprise applications/websites lessens the security burden enforcing strong authentication where it's needed the foremost. Adaptive Authentication may be used in a variety of ways, including:
Adaptive MFA adjusts to your risk levels, enforcing the right amount of MFA for the given level of user risk, regardless of how you established them.
Appropriate Adaptive Authentication challenges are presented based on the user’s risk profile which forces the them to authenticate using the configured MFA method with improved security.
Adaptive Authentication Engine works on any device supporting a Web Browser. Additionally, we also provide the same functionality using APIs.
Adaptive Authentication restricts user access based on attributes (user’s risk profile) such as IP Address, Device ID, Geo-Location & Time of Access.
Eliminates the need for a fixed approach that forces frequent user authentication. User session attributes (risk profile) are fetched at runtime to calculate the risk and decision result.
Adaptive Authentication collects the user session attributes as risk profile at runtime and calculates the precise decision result on the go with the required MFA prompt.
Fraud Prevention, as a web service, eliminates the need for each custom application to develop specific security access user authentication methods . Additionally, we also provide the same functionality using API's.
Having Adaptive Authentication enabled helps in runtime risk analysis which decreases the chance of an unauthorized user gaining access to corporate sensitive information.
As Adaptive MFA prompts for authentication only when required most, it minimizes user efforts to log in multiple times which helps them to focus on work improving the organization’s productivity.
Adaptive Authentication creates a situation where any successful account breach or fraudulent transaction requires additional efforts and resources
With a miniOrange Adaptive Authentication dynamic setup, you can easily configure any of the restriction methods on any of your devices.
When you have Adaptive Authentication , you’ll have less suspicious activity on user accounts, which means you’ll spend less money on security management.
You can use our Adaptive Authentication APIs to integrate additional security into your applications on any device that supports a web-Browser.
In Adaptive Authentication IP-based restriction method, the admin configures and enlists all IP addresses to allow or deny access. When a user attempts to log into one of the adaptive authentication-enabled apps, his IP address is compared to the preset IP list, and the appropriate action is taken depending on the results (i.e. Allow, Deny or Challenge).
In the Device based Adaptive Authentication 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 person's device has been registered, that person will be able to log in without restriction. If a person's registered device exceeds the admin's total registered device limit, they will be Challenged or Denied, depending on the policy.
In Location-based Adaptive Authentication 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.
One of the most significant components of Adaptive Authentication configuration is time restriction , which begins with the admin establishing a time zone with Start and End Time. Users are either permitted, refused, or challenged based on the timezone and policies defined. When an end-user tries to log in with adaptive authentication enabled, his time zone-related parameters, such as time zone and current system time, are checked against the list defined by the admin, and the user is either permitted, rejected, or challenged, depending on the configuration.
When you decide to implement Adaptive Authentication in your organization, you need to define basic login requirements for users or a user group. These requirements may vary person to person based on location, role, and resource value risk.
Adaptive authentication starts with creating a profile for each client, which includes info around their 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 person 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.
Multi-Factor Authentication (MFA) is an authentication method that requires the user to provide two or more verification factors, such as a username, password, and additional security measure, to gain access to a resource.
On the other hand, Adaptive MFA provides an extra edge to MFA security based on risk and access provided by the security admin to control user access. It detects fraudulent attempts based on predetermined risk criteria and prompts customers to complete an additional authentication step to confirm their identities.
Knowledge Factor (something you know): Includes multiple passwords, PIN codes, and answers to security questions. Anything you can remember, type, say, do, execute, or otherwise recall when needed is considered a knowledge element.
Possession Factor (something you have): Includes a particular object which you possess since it is improbable that a hacker would acquire your password and take anything physical. This category includes smart cards, mobile phones, physical tokens, key fobs, and keychains.
Inherence Factor (something you are): Verified by a fingerprint test on a phone, but it also includes anything that may be a wholly unique identification of your physical body, such as a retinal test, voice or facial recognition, or any other sort of biometrics.
Our Other Identity & Access Management Products
Seamless login for workforce and customer identity to cloud or on-premise appsLearn more
Secure access for identities with an additional layer of authenticationLearn more