CA RiskMinder Administration Guide › Understanding RiskMinder Rule Basics

Understanding RiskMinder Rule Basics

Important! Most of the tasks related to the concepts discussed in this section can only be performed by Global Administrators and Organization Administrators. However, this section is useful for anyone who wants to understand the basics of rules used by RiskMinder.

RiskMinder uses rules to evaluate the risk associated with each transaction. These rules can be broadly categorized into the following categories:

• Evaluation Rules
• Scoring Engine

Irrespective of the category the rule belongs to, every rule in RiskMinder has three specific characteristics that govern how the rule is processed:

• Ruleset: Each rule must belong to a Ruleset. This choice of the Ruleset determines the options that are available for a rule. For more information on working with Rulesets, see "Creating Rulesets".
• Rule Implementation (at global or organization level): This determines whether the rule is applicable at the global level (available as a template to organizations) or at the level of individual organizations.

  See "Managing Global Configurations" and "Managing Organization-Specific RiskMinder Configurations" for implementing rules at global and organization levels, respectively.

• Rule Type: This determines the capability and scope of the rule, and is closely associated with New Rules Added Using the Rule Builder.

  The following figure is a schematic representation of RiskMinder rules and their scoring order.

  

The rules are run in the following phases:

Execution Phase

RiskMinder Server does a first parse of all the rules in the active ruleset. In this phase, the Server:

1. Executes all the rules in the list in the order of execution priority.

   This execution priority is internal, and is defined by the Server.

2. Generates an individual risk score and advice for each rule it executes.

Scoring Phase

RiskMinder Server now does the second parse of the rules. In this phase, the Server:

1. Uses the result for each rule in the first parse, and parses the rules in the ruleset based on the scoring priority.

   The scoring priority is configured by the Global Administrator (GA) through Administration Console.

2. Stops the scoring at the first matched rule.
3. Returns the score and advice of the rule that matched as final.

Note: Depending on when the first rule matched, the second parse may not be run completely.