Identity Confidence Attribute for Authentication Conditions

Document created by RSA Information Design and Development on Apr 14, 2017Last modified by RSA Information Design and Development on Oct 20, 2017
Version 6Show Document
  • View in full screen mode

RSA SecurID Access can establish high or low confidence in a user's identity based on data it collects when users attempt to authenticate over a period of time. You can configure authentication requirements for an application, or allow or deny access, based on identity confidence by using the Identity Confidence attribute in an access policy.

During data collection, RSA SecurID Access learns various attributes about users such as their behavior, the locations from which they attempt to authenticate, the characteristics of devices used for authentication, and other factors that can increase or decrease confidence in each user's identity. Every time a user authenticates, RSA SecurID Access uses the data it has collected over time to calculate an identity confidence score and categorizes the score as high or low. A high score means RSA SecurID Access is confident the user is indeed who he says he is. A low score means RSA SecurID Access cannot identify the user with a reasonable degree of certainty.

The collected data is specific to your company. Data from a large user population collected over a long period of time ensures more reliable results than data from a small user population collected over a short period of time. Identity confidence results can vary from company to company depending on these factors.

Note:  By default, data collection is enabled for your company. To obtain the maximum benefit from identity confidence scores, RSA recommends that you leave data collection enabled. If you need to disable or re-enable it, contact RSA Customer Support.

 

 

 

You are here
Table of Contents > Access Policies > Identity Confidence Attribute for Authentication Conditions

Attachments

    Outcomes