These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Fraud Detection System
- Process
- Detection rule review
Detection rule review
Review rule versions and keep alert links intelligible.
Step by step
-
Register rule Rule Steward
The Rule Steward records a rule name, version and expression in draft. The text should identify the suspicious condition the team wants to examine.
- Captures draft name, version and expression
- Updates Detection rules
-
Review definition Rule Steward
The steward and a second reviewer examine the expression against representative applications before the rule is marked reviewed. They should agree which cases would call for attention.
- Checks rule meaning against case context
- Updates Detection rules, Applications
-
Mark active Rule Steward
The steward records the active status only after the reviewed version is understood and its case owner is clear. A later alert carries a link to the relevant rule record.
- Makes the reviewed rule identifiable to alert reviewers
- Updates Detection rules, Fraud alerts
-
Retire version Rule Steward
When the criteria change, the old rule can be retired while prior alerts continue to point to a readable version. Create a new version for the replacement definition.
- Preserves the rule context of earlier alerts
- Updates Detection rules, Fraud alerts
Who does what
Roles and permissions- Rule Steward
- Maintains the register; Fraud Investigator reviews alerts against the rule; Case Analyst supplies application context; Admin manages access.
Set up Fraud Detection System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.