Device Settings for Risk-Based Authentication
For risk-based authentication (RBA), the system uses device history as a factor in determining risk. The device history is a list of user authentication devices from previous, successful logons. The system maintains a device history for each user. Once added to the list, the device is considered to be registered. When the user tries to access an RBA-protected resource using a registered device, the authentication attempt is likely to have a higher assurance level. When the user attempts to logon with an unknown device, the system challenges the user for identity confirmation. If the logon is successful, the new device is added to the user’s device history list.
You specify how the system registers and manages user’s devices for RBA. You can configure the following client device settings.
Setting | Description |
New device registration | AM can register a new device automatically or ask users if they want to register the device. If you expect users to access RBA-protected resources from public or shared devices, allow them to decide which devices they want to register. |
Total registered devices | You can set the maximum number of registered devices preserved in each user’s device history. If the number of registered devices exceeds the limit, the nightly cleanup job deletes the least recently used devices. |
Unregister devices | You can specify when inactive devices are removed from a user’s device history. For example, you can specify that devices are removed from a user’s device history after 60 days of inactivity. Consider the needs of all your users. Although most users might use the same client devices frequently to access RBA-protected resources, some users might only use public client devices infrequently. |
Related Articles
Configure Device History Settings for a Risk-Based Authentication Policy Number of Views How to Disable 'Add Members' button under Role management option for Roles using RSA Via Lifecycle & Governance Number of Views Terminated Users not correctly removed from Roles in RSA Identity Governance & Lifecycle Number of Views Configure a Custom Console Logon Banner Number of Views Imported business descriptions are not updated correctly for groups in different applications having the same name in RSA … Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle
