CA RiskMinder Administration Guide › Managing Global Configurations › Managing Global Rule Configurations › Editing Rule Definitions Using the Rule Builder › Configuring User Velocity

Configuring User Velocity

The User Velocity Check rule keeps a check on the number of transactions from a user within a specified period of time. It is based on the following parameters:

• Number of Risk Evaluations per User

  Denotes the number of transactions (N) performed by RiskMinder for a specified user, irrespective of the Advice or Risk Score.

  The default value for this parameter is 5.

• Time Interval

  Denotes the time period (T) in which the number of transactions are tracked.

  The default value for this parameter is 60.

• Unit for Time Interval

  Denotes the unit in which the time period (T) is measured.

  The default value for this parameter is Minutes.

To configure the User Velocity Check rule:

1. Ensure that you are logged in as a GA.
2. Activate the Services and Server Configurations tab.
3. Under the Rules Management section on the side-bar menu, click the Rules and Scoring Management link.

   The Rules and Scoring Management page appears.

4. From the Select the Ruleset list, select the ruleset for which this configuration is applicable.

   The configuration information for the specified ruleset appears.

5. In the RULENAME column, click the User Velocity Check link.

   The RiskFort Rule Builder page appears.

6. Specify a value for the number of risk evaluations per user in the Greater than field.
7. Specify the time interval.

   This value denotes the maximum number of transactions (within the specified time interval) that is considered safe for a user. If the actual number of transactions within the specified time exceeds this number, then RiskMinder will track it as a risk, which will result in the matching of the User Velocity rule.

8. Select the unit for the time interval from the drop-down list.
9. Click Update to build the rule fragment.
10. Click Update at the bottom of the Rule Builder page to save the changes.

    The changes are not yet active and are not available to your end users.

11. To make the changes active, you must migrate them to production.

    See "Migrating to Production" for instructions to do so.

12. Refresh all deployed RiskMinder Server instances.

    See "Refreshing the Cache" for instructions on how to do this.