--- title: "Defining attribute-based rules for file execution" slug: "defining-attribute-based-rules-for-file-execution-1" tags: ["Product Usage", "ACC 8.4.x"] updated: 2026-09-01T13:04:56Z published: 2026-09-01T13:04:56Z canonical: "docs.trellix.com/defining-attribute-based-rules-for-file-execution-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. # Defining attribute-based rules for file execution Application Control performs multiple checks to determine whether to allow or block a file's execution. If a file's execution is allowed after the Application Control checks, attribute-based or granular rules, if any are defined, come into play. The rules are based on the concept of fine-grained allow listing and can be created on the attributes of a file. > [!NOTE] > Note > > This feature is also known as Execution Control and it is enabled by default. To disable this feature, use this command: `sadmin features disable execution-control` You can define specific rules using one or more attributes to allow, block, or monitor the file. Rules that allow execution take precedence over rules that block or monitor execution. Attribute-based rules help you allow or block files in different scenarios based on file context and offer flexibility. - Context-based allowing or blocking of files — On a protected system, only allow listed interpreters are permitted to execute. But, in certain scenarios, allow listed interpreters might be misused to execute malicious scripts. For example, a `powershell.exe` script can be used to execute unsolidified scripts and execute file-less scripts by invoking its execution with atypical input arguments. You can prevent misuse of interpreters by defining attribute-based rules to block potentially malicious scenarios. - Flexibility and control — Attribute-based rules provide flexibility to allow or block file execution, as needed. You might need to block a user from running a specific file. If an administrator wants to block the execution of `powershell.exe`for a specific user, a rule can be added to prevent its execution. You can achieve such scenarios using attribute-based rules. Similarly, you might choose to block execution of a certain file in your setup completely, unless when run by a specific parent process. You can achieve this by creating a generic block rule and a parent process-based allow rule for the file. Because the allow rule has precedence over the block rule, it overrides the block rule when applied. Or, you might choose to only observe or monitor a file to determine its execution in your setup. To do this, you can define a monitor rule for the file. > [!NOTE] > Note > > We recommend that before creating a block rule for a file, create a monitor rule to observe the file's use and execution in your setup. After you define the monitoring rule, if no **OBSERVED_FILE_EXECUTION** events are generated for the file over a reasonable time window, you can safely define a block rule for a file. When configuring an attribute-based rule, you can choose to allow, block, or monitor a file. This table describes the behavior of a rule in various supported modes. | Type of rule | Enable | Update | | --- | --- | --- | | Allow | - Allow file execution. - No event is generated. | - Allow file execution. - No event is generated. | | Block | - Block file execution. - The **PREVENTED_FILE_EXECUTION** event is generated. | - Allow file execution. - The **OBSERVED_FILE_EXECUTION** event is generated. | | Monitor | - Allow file execution. - The **OBSERVED_FILE_EXECUTION** event is generated. | - Allow file execution. - The **OBSERVED_FILE_EXECUTION** event is generated. | > [!NOTE] > Note > > The applied rules are ineffective when any process is selected as an updater. Only the events are generated.