--- title: "AAC rule structure" slug: "aac-rule-structure" tags: ["Product Usage", "ENS 10.7.x", "Endpoint Security"] updated: 2026-09-14T20:39:07Z published: 2026-09-14T20:39:07Z canonical: "docs.trellix.com/aac-rule-structure" stale: true --- > ## 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. # AAC rule structure Rules define the boundaries of acceptable behavior and tell AAC how to react when the filtered action matches the rule specifications. > [!NOTE] > Note > > Exploit Prevention is not supported in the ARM architecture. The `Rule` command at the root level defines the rule. Each Expert Rule identifier can contain only one rule definition and multiple subrules. The `Match` command defines subrules, each of which has an assigned role: `Initiator` or `Target`. Because `Initiator` subrules always apply to PROCESS objects, the `Process` command provides a shortcut method for defining `Initiator` sections. > [!NOTE] > Note > > Commands for building AAC rules are case sensitive. Here is the basic structure of AAC-based rules: ``` Rule { Initiator { Match … { Include … { … } Exclude … { … } } } Target { Match … { Include … { … } Exclude … { … } } } } ``` > [!NOTE] > Note > > Endpoint Security doesn't support signatures with multiple rules.