Risk-Based Authentication
What is Risk-Based Authentication?
How does Risk-Based Authentication work?
- 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.
What signals can Risk-Based Authentication use?
- 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
How is Risk-Based Authentication different from MFA?
When is identity verification used in Risk-Based Authentication?
- 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
How can Regula help with Risk-Based Authentication?
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.