Language

Risk-Based Authentication

What is Risk-Based Authentication?

Risk-based authentication (RBA) is an authentication approach that adjusts access requirements according to the risk associated with a login attempt, transaction, or other user action. Instead of applying the same checks to every interaction, the system evaluates contextual signals and determines whether to allow the action, request stronger authentication, or block it.
For example, a customer signing in from a familiar device and location may use the standard authentication method. If the same account attempts a high-value transfer from a new device in another country, the system may require an additional factor or identity check. Risk-based authentication is also called adaptive authentication because the authentication process adapts to the circumstances of the request.

How does Risk-Based Authentication work?

A typical RBA process includes the following steps:
  • Collect signals. The system gathers information about the user, device, network, session, requested action, and previous behavior.
  • Evaluate risk. Rules or a risk engine assess whether the signals are consistent with the account’s established profile.
  • Assign a risk level. The request may be classified as low, moderate, or high risk, or receive a numerical risk score.
  • Apply the appropriate response. The system allows the action, requests additional authentication, sends it for review, or blocks it.
  • Record the outcome. Authentication results and related signals are logged for monitoring, investigation, and future risk decisions.
Risk is evaluated for a particular request, not assigned permanently to the user. A person may complete a low-risk action without additional checks but face stronger requirements when attempting a sensitive account change.

What signals can Risk-Based Authentication use?

The signals depend on the service and the action being protected. Common examples include:
  • Whether the device has been used with the account before
  • Device security status and application integrity
  • IP address, network type, and geolocation
  • Time of access and differences from usual activity
  • Impossible travel between recent sessions
  • Browser, operating system, and session metadata
  • Multiple failed login or authentication attempts
  • Unusual typing, navigation, or transaction behavior
  • Value and type of the requested transaction
  • Changes to passwords, contact details, beneficiaries, or payout accounts
  • Previous fraud alerts or account-recovery events
No single signal necessarily proves fraud. An unfamiliar device may simply mean that the customer bought a new phone. RBA evaluates the combination of signals and the potential consequences of granting the requested access.

How is Risk-Based Authentication different from MFA?

Multi-factor authentication (MFA) requires factors from at least two different categories, such as a password and a registered device. Risk-based authentication determines when a particular authentication method or additional check should be required.
The two approaches can work together. An RBA system may allow a low-risk interaction after the standard authentication process but require biometric MFA or a security key when risk increases. For a particularly sensitive recovery request, it may trigger renewed identity verification instead.

When is identity verification used in Risk-Based Authentication?

Identity verification is generally reserved for situations in which ordinary authenticators no longer provide enough confidence. Common triggers include:
  • Account recovery after the user loses access to an authenticator
  • Suspected account takeover
  • A request to replace or reset MFA
  • Changes to payout or banking details
  • Addition of a new beneficiary or payment method
  • Privilege elevation or access to sensitive records
  • Conflicting identity, device, or session information
The purpose is not to repeat the entire onboarding process whenever a signal changes. The additional evidence should address the specific uncertainty created by the risk event.

How can Regula help with Risk-Based Authentication?

Regula provides document and biometric verification technologies that can support higher-risk authentication and account-recovery workflows.
Regula Face SDK performs a 1:1 comparison between a current facial capture and a trusted reference, such as a portrait collected during verified onboarding. Liveness detection helps determine whether a real person is present rather than a photograph, mask, or replayed video.
Regula Document Reader SDK can verify an identity document and extract its data when stronger identity reverification is required. Regula IDV Platform allows organizations to configure workflows that apply document verification, face matching, liveness detection, screening, or manual review according to their own risk rules.
The organization’s authentication and risk systems remain responsible for collecting contextual signals, calculating risk, selecting the required checks, and deciding whether access should be granted.

FAQ

Is Risk-Based Authentication the same as adaptive authentication?

The terms are commonly used interchangeably. Both describe an authentication process that changes according to the risk and context of an interaction. Some vendors may use the terms differently, so organizations should examine the actual signals, rules, and responses supported by a particular system.

Can Risk-Based Authentication replace MFA?

Not necessarily. RBA determines which authentication controls should apply, while MFA requires more than one independent factor. An organization may use RBA to trigger MFA only in higher-risk situations or require MFA by default and use RBA to add further checks.

Does a high-risk score automatically mean fraud?

No. A risk score indicates that the request differs from expected conditions or could have serious consequences. The user may have a legitimate explanation, so the system can request stronger authentication or refer the case for review instead of rejecting it automatically.

Can biometrics be used in Risk-Based Authentication?

Yes. Face verification can serve as an additional authentication step when a session or action presents elevated risk. Face matching should use a trusted enrolled reference, while liveness detection helps protect the capture against presentation attacks.

How does Risk-Based Authentication improve the user experience?

It can reduce unnecessary friction by reserving stronger checks for situations that warrant them. Routine interactions can follow a simpler path, while unusual or sensitive actions receive additional protection. Poorly calibrated rules can still create false alerts, so organizations should monitor outcomes and adjust their thresholds.

On our website, we use cookies to collect technical information. In particular, we process the IP address of your location to personalize the content of the site

Cookie Policy rules