Login anomalies
Login anomaly notifications help customers identify successful logins from devices or locations that Strivacity does not recognize for their account.
You can configure notifications for new devices and new locations separately. When a notification type is enabled, customers can manage the corresponding notification preference in My Account.
Settings
| Setting | Description | Status |
|---|---|---|
| New device notification | Sends a notification after a successful login from a device that Strivacity does not recognize for the customer. | Enabled by default for new instances. Disabled by default for existing instances. |
| New location notification | Sends a notification after a successful login from a location that Strivacity does not recognize for the customer. | Enabled by default for new instances. Disabled by default for existing instances. |
| Location sensitivity | Defines the level of geographic detail used to determine whether a login comes from a new location. Select Country, Region, or City. | Country by default. |
| Trusted locations | Specifies locations that should be treated as trusted when evaluating new-location logins. | N/A |
Notification templates are managed in the Notifications policy.
New device notification
When New device notification is enabled, Strivacity can notify a customer after a successful login from a device that has not previously been recognized for their account.
The first login to an account does not trigger a new-device notification. After a device is recognized, subsequent successful logins from that device do not trigger additional notifications.
If the customer does not select Keep me logged in, Strivacity does not retain the information used to recognize the browser. A later login from the same device may therefore be treated as a new-device login.
New location notification
When New location notification is enabled, Strivacity compares the location of a successful login with the locations previously associated with the customer.
Use Location sensitivity to define the level at which locations are compared:
- Country: compares the login country.
- Region: compares the country and region.
- City: compares the country, region, and city.
Changing the location sensitivity does not clear previously collected location history. Strivacity uses the available location information at the newly selected level.
If previously stored location information does not contain the level of detail required by the new sensitivity, the login is treated as coming from a new location.
City sensitivity is recommended only for environments that require more precise location detection. IP-based city information can vary because of VPNs, mobile networks, and ISP routing, which can cause legitimate logins to be identified as new locations.
Notification behavior
Login anomaly notifications inform customers about successful logins from new devices or locations. Whether a notification is sent depends on both the Adaptive Access policy and the customer's notification preferences.
Strivacity sends a notification only when an administrator enables the corresponding login anomaly notification in the Adaptive Access policy and the customer enables the corresponding preference in My Account. If an administrator disables a notification type, the corresponding preference is not shown to customers.
Strivacity sends notifications to the customer's verified email address. If no verified email address is available, the notification falls back to SMS sent to a confirmed phone number.
Notifications are sent asynchronously after a successful login and do not interrupt or delay the authentication journey. Delivery failures do not affect the login.
Notification frequency depends on the anomaly type:
- New device: Strivacity sends one notification when a device is first identified as new for the customer. Subsequent successful logins from the same recognized device do not trigger another notification.
- New location: Strivacity sends one notification when a location is first identified as new according to the configured Location sensitivity. Subsequent successful logins from the same recognized location do not trigger another notification.
You can manage notification templates through the Notification policy. Administrators can review sent notifications and their delivery status in Notification history.
Updated about 2 hours ago