Adaptive rules
On the Adaptive rules tab, you can customize adaptive rules to determine how Adaptive Access responds to customer behavior during authentication. You can block access, require an additional authentication factor, or let customers skip MFA.
Blocking rules apply independently of the selected rule mode. For the remaining authentication decisions, select either Basic rules or Risk policy.
Blocking rules
Blocking rules deny registration, authentication, and certain token operations based on IP addresses, geographic locations, or detected threats.
You can configure restricted geographical locations at the city, state, or country level.
Once a geographical location or subnet is blocked, step-up or step-down rules can't be applied to lower-level locations or subnets because they are already blocked.
You can configure exceptions when it would take longer to list all restricted IP addresses or geographical locations.
Token lifecycle events
IP address and location blocking rules also apply to token lifecycle events, including token issuance, refresh, exchange, and delegation requests.
If a request matches a blocking rule, Strivacity denies the token request. If no blocking rule matches, token processing continues normally.
Only blocking rules apply to token lifecycle events. Step-up and step-down actions are not supported for these requests.
Block detected risky behaviors
Blocking rules can also respond to detected risks that are not tied directly to a configured IP address or location.
Depending on your security practices, you can choose to block the following suspicious behaviors:
Anonymous proxy/Tor
This feature detects requests coming from anonymous proxy servers or Tor exit nodes. When enabled as part of a blocking rule, Anonymous proxy/Tor detection allows access to your applications only for customers whose online presence can be traced back.
Bot detection
Bot detection evaluates incoming requests for signs of automated activity and known fraudulent activity associated with the IP address.
Select one of the following:
- Block only highest risk scores: Blocks activity with the highest likelihood of coming from a non-human actor. This has a lower probability of blocking legitimate customer activity.
- Block high and highest risk scores: Also blocks traffic from a lower risk tier. This provides stronger protection but increases the risk of false positives.
- Do not block when any bot risk is detected: Does not block based on bot detection.
Rule modes
Under Rule mode, select how Adaptive Access determines authentication actions after blocking rules have been evaluated:
- Basic rules: Use the built-in Adaptive Access step-up and step-down controls.
- Risk policy: Use a risk policy to determine the authentication action.
Basic mode
Step-up rules
If no blocking rule is triggered, step-up rules determine whether the customer must complete an additional authentication factor.
You can configure step-up rules for specific IP addresses and geographical locations.
You can also step up authentication based on detected risks.
Improbable travel event
An improbable travel event occurs when the distance between two login locations could not reasonably have been travelled in the time between the login attempts.
Enable Improbable travel event to require an additional authentication factor when this condition is detected.
Anonymous proxy/Tor
Enable Anonymous proxy/Tor to require an additional authentication factor when the customer accesses the application from an IP address associated with an anonymous proxy server or Tor exit node.
Bot detection
Bot detection can require an additional authentication factor when automated activity is suspected.
Select one of the following:
- Step-up only highest risk scores: Steps up activity with the highest likelihood of coming from a non-human actor. This has a lower probability of stepping up legitimate customer activity.
- Step-up high and highest risk scores: Also steps up traffic from a lower risk tier. This provides stronger protection but increases the risk of false positives.
- Do not step-up when any bot risk is detected: Does not step up authentication based on bot detection.
Once step-up is applied to a geographical location or subnet, step-down rules can't be applied to lower-level locations or subnets because step-up already applies.
Step-down rules
If no blocking or step-up rule is triggered, step-down rules determine whether the customer can skip an otherwise required MFA step.
You can step down authentication:
- From geographical locations or IP addresses you trust.
- From recognized devices.
- When the customer's behavior is consistent with their previous authentication activity.
In a passwordless journey, customers are asked for their password at login if step-down applies.
In the IP address and Location sections, configure the IP ranges and geographical locations where customers can skip MFA.
Device recognition
Enable Device recognition to allow customers to skip a required second factor on recognized devices.
| Setting | Description |
|---|---|
| Device recognition | Allows customers to select Remember my device. A remembered authenticator is stored for the configured period or until the device session is deleted. |
| Number of days to remember the device | Specifies how long the device is recognized. After this period, the device no longer triggers a step-down action. The period does not reset when the customer accesses the application. |
| Enable remember my device by default | Selects the Remember my device checkbox by default during MFA. |
Behavior analytics
Behavior analytics identifies authentication behavior that is usual for a customer. When trusted behavior is detected, the customer can skip an otherwise required MFA method.
| Setting | Description |
|---|---|
| Location | Collects location information from authentication sessions and determines whether the login location is usual for the customer. |
| Day of time/week | Monitors authentication times to determine whether the customer typically logs in at similar times of day or days of the week. |
If behavior analytics determine that the customer is logging in from their usual location or at their usual time, authentication is stepped down from an otherwise required factor.
Risk policy
Risk policy mode uses a configured risk policy to determine the authentication action after the customer has been identified.
Blocking rules continue to apply when Risk policy mode is selected.
To configure risk policy mode:
- Under Rule mode, select Risk policy.
- Under Authentication, select a Risk policy.
- For each Policy result, select the corresponding action:
- Step-up
- Step-down
- Block
- Under On evaluation error, select the action to take if the risk policy cannot be evaluated successfully.
- Select Save.
The available policy results are defined by the selected risk policy. Each result can be mapped independently to an Adaptive Access action.
Selecting a risk policy is optional.
For information about configuring risk policies, see Create a risk policy.
Use On evaluation error to determine what Adaptive Access should do when the selected risk policy cannot complete its evaluation successfully.
Updated about 17 hours ago

