Sequence Scenario Editor Terminology

The following table provides a list of terms used to define the concepts of the Sequence Scenario Editor.

Table 6-1 Sequence Scenario Editor List of Terms

Term Definition
Augmentation Process that is executed after the completion of a detection job to supplement the information stored and displayed with each match. Augmentation can be added through bindings or matches. Two augmentation mechanisms are available:
  • Binding Augmentation: Adds information for display in the alert highlights.
  • Match Augmentation: Adds references to additional matched records that are shown on the Alerts Details page on the Web Application.
Bound Variable Variables captured in a pattern. Four types of bindings are available:
  • Bind Before: Variable is captured before checking the constraints.
  • Bind After: Variable is captured after checking the constraints.
  • Rebind Before: Previously bound variable is incremented or updated, and completed before checking of constraints.
  • Rebind After: Previously bound variable is incremented or updated, and completed after checking of constraints.
Focus Entity upon which an alert is based.
Pattern Defined set of detection logic that is used to search data for behaviors of interest.
Scenario Entity that represents a behavior of interest within a business.
Scenario Class Group or category of scenarios that represents related behaviors.
Sequence Scenario Editor Tool used within the Scenario Manager that enables Data Miners to build and modify sequence scenarios.