Skip to main content
Version: 6.2

Anomaly Detection Rules

A detection rule determines which object alerts become an anomaly. Anomalies appear in the anomaly feed.

To open the rules, select Main Menu - User Behavior Analytics - Anomaly Detection Rules.

Anomaly detection rules

Rule List​

The table contains:

  • Rule - the rule name
  • Object Categories - the categories to which the rule applies
  • Type - how the rule groups alerts into an anomaly
  • Condition - the threshold or families
  • Window - the window length

Creating a Rule​

To create a rule:

  1. Open the anomaly detection rule list
  2. Click Create Rule
  3. Fill in Name. Two rules cannot have the same name
  4. Change the description if necessary; see Description
  5. Select the rule type; see Rule Types
  6. Select at least one object category
  7. Set the condition: Anomaly Score At Least for a score threshold, or rule families for a family set or sequence
  8. Set the window to an integer number of minutes, hours, or days
  9. Click Save

New rule


Rule Types​

  • Score Threshold - the anomaly score within the window is at least a threshold from 0 to 100, for example at least 40 over a day
  • Family Set - rules from all selected families trigger within the window, in any order. At least two families are required
  • Family Sequence - rules from all selected families trigger within the window, with their first alerts appearing in the specified order. At least two families are required

For the threshold rule, the anomaly score is calculated in the same way as the object score: from the rules that triggered within the window, using the category's severity weights but excluding watchlist effects.


Description​

The description is the row text in the anomaly feed. Values that differ between anomalies are set with substitutions:

SubstitutionValueRule Type
{{score}}anomaly scoreall
{{alerts_count}}number of alertsall
{{chain}}families ordered by their first alertfamily sequence

Thresholds and condition families are entered as text. A substitution unavailable for the rule type prevents the rule from being saved.

When a rule is created or its type changes, the type's template is inserted. An empty description is also replaced with the template:

Rule TypeDefault Template
Score ThresholdScore {{score}}, alerts: {{alerts_count}}
Family SetAll rule families triggered, alerts: {{alerts_count}}
Family Sequence{{chain}}, score {{score}}