Four of the predefined rules have been deprecated in release 8.0. Alternative rules have been introduced for these deprecated rules. The following table lists the deprecated and new rules and rule mnemonics:
|
Deprecated Rule Name and Rule Mnemonic |
New Rule Name and Rule Mnemonic |
|---|---|
|
DeviceID Known (DEVICEIDCHECK) |
Unknown DeviceID (UNKNOWNDEVICEID) |
|
Device MFP Match (SIGMATCH) |
Device MFP Not Match (MFPMISMATCH) |
|
User Associated with DeviceID (USERDEVICEASSOCIATED) |
User Not Associated with DeviceID (USERDEVICENOTASSOCIATED) |
|
User Known (USERKNOWN) |
Unknown User (UNKNOWNUSER) |
Important! Although these rules have been deprecated, they are still available and you can use after the upgrade. We recommend that you replace each deprecated rule with the corresponding new rule by making the required changes in the rule expression.
For any of the four deprecated rules, if the rule evaluates to No, then the rule is considered to have matched. It is then used for scoring. In contrast, each of the other predefined rules is considered to have matched when they evaluate to Yes.
In each of the four new rules that is introduced in release 8.0, if the rule evaluates to Yes, then the rule is considered to have matched. In this way, the four new rules are consistent with the other predefined rules.
The following table lists examples that highlight the difference between the deprecated rules and new rules:
|
Sample Use Case |
Deprecated Rule |
Deprecated Rule Result |
New Rule |
New Rule Result |
|
User does not exist in the CA Risk Authentication database. |
USERKNOWN |
No |
UNKNOWNUSER |
Yes |
|
DeviceID does not exist in the CA Risk Authentication database. |
DEVICEIDCHECK |
No |
UNKNOWNDEVICEID |
Yes |
|
MFP does not exist in the CA Risk Authentication database. |
SIGMATCH |
No |
MFPMISMATCH |
Yes |
|
User is not associated with the DeviceID. |
USERDEVICEASSOCIATED |
No |
USERDEVICENOTASSOCIATED |
Yes |
Follow these steps:
To modify a rule expression:
Note: For detailed information about migrating a rule to the production environment and refreshing the cache, see the CA CA Risk Authentication Administration Guide.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|