--- title: "Multistage rule workflow (Legacy)" slug: "multistage-rule-workflow-legacy-1" updated: 2026-09-13T08:42:46Z published: 2026-09-13T08:42:46Z canonical: "docs.trellix.com/multistage-rule-workflow-legacy-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Multistage rule workflow (Legacy) The following steps describe the general workflow of a multistage rule. For details on creating multistage rules, see [Creating a multistage rule](/network-and-platform/docs/creating-a-multistage-rule-legacy-1). 1. Create a first-stage rule. This rule must have at least one assertion. First-stage rules can generate alerts. First-stage rules add `detect_*` tags to events as Trellix Helix processes the raw events sent to it. The `detect_*` tags are: - `detect_ruleids` - `detect_rulenames` - `detect_rulematches` You can use these tags to search for events that match rules, without the need to generate alerts for every rule. 2. Optionally, create middle-stage rules. These rules must include at least one assertion and at least one dependency. Middle-stage rules cannot be alerted on and do not add `detect_*` tags to events. 3. Create a final-stage rule. The final-stage rule must have at least one dependency, but no assertions. The final-stage rule cannot be alerted on and does not add `detect_*` tags to events. 4. When the multistage rule is satisfied, a `class=analytics application='multi-stage rules'` event is created. If you want to generate alerts for the multistage rule, you must create another rule that matches on this analytics event. For example, if the final-stage rule has a rule ID of `9999.0.1`, the query for the alerting multistage rule would be: ```plaintext class=analytics application='multi-stage rules' detect_ruleids:9999.0.1 ``` :