The User Not Associated with DeviceID rule evaluates transactions by checking the association between the user and the device, irrespective of the time the association was created. If the user-device association exists, then the transactions receive a low risk score. There might be cases where fraudsters can reset a user's password and associate themselves with the device. In such cases, evaluating the transaction based only on the User-Device association might not be sufficient to rule out fraudulent activity.
The Device User Maturity rule enables setting a level of trust in the device. For example, a User-Device association that has existed for a month, assuming that there has been no fraudulent activity identified for that user or device, should be more trusted than a User-Device association that has been established recently.
It is based on the following parameters:
Denotes the number of successful transactions identified by RiskMinder for a specified User-Device association.
Denotes the time (in days) before which the first successful transaction was identified.
These parameters determine the strength of the User-Device association. The Device User Maturity rule returns True if the user has used the device for at least the specified number of days and the number of successful transactions is greater than or equal to the configured value.
To create the Device User Maturity rule:
The Rules and Scoring Management page appears.
The configuration information for the specified ruleset appears.
The RiskFort Rule Builder page appears.
The changes are not yet active and are not available to your end users.
See "Migrating to Production" for instructions to do so.
See "Refreshing the Cache" for instructions on how to do this.
|
Copyright © 2013 CA.
All rights reserved.
|
|