Create sticky rules to protect a system reboot

Prev Next

Exploit prevention sticky expert rules boot execution

Trellix Endpoint Security (ENS) protection rules typically require active core background services to enforce policies. During a system reboot, a delay occurs between initial OS boot and complete background service startup. This delay creates an exposure window where non-sticky rules do not enforce policy.

Sticky rules remain active at the driver level during reboot sequences and service downtime. Sticky rules enforce protection commands even when the main protection service is down or starting up.

The protection scope for sticky rules is limited to the arbitrary access control engine (AAC engine). Protection features evaluated in user mode—such as buffer overflow, illegal API monitoring, and service management—do not support sticky rule execution during boot.

Protection enforcement sequence during reboot

  1. System Reboot Event Initiated: The host operating system undergoes a system restart.

  2. Kernel Driver Level Execution: The Access Control (AAC) engine becomes active in kernel mode. Sticky rules evaluate and enforce protection commands immediately without waiting for background services.

  3. User Mode Initialization: The Trellix Endpoint Security Platform service starts up. Non-sticky rules begin enforcement, and user-mode features (Buffer Overflow, Illegal API, and Services) initiate evaluation.

AAC kernel engine versus user mode evaluation limits

The protection engine evaluates rules across two structural layers: kernel mode and user mode. The execution layer determines whether a rule can operate as a sticky rule during service downtime.

Feature / Category

Evaluation Layer

Sticky Rule Support

Enforcement State during Service Downtime

Access Control (AAC)

Kernel Mode

Supported

Enforced immediately

Buffer Overflow (BO)

User Mode

Not Supported

Not enforced

Illegal API

User Mode

Not Supported

Not enforced

Services

User Mode

Not Supported

Not enforced

Configure sticky rules in expert policy options

Configure sticky rules within your expert rule definition text to enforce access rules while protection services start up.

Prerequisites

  • You must have administrator privileges on the target endpoint or management console.

  • Access rules must belong to the Access Control evaluation type.

Procedure

  1. Open the target expert policy rule syntax editor.

  2. Locate the specific rule section requiring boot-level enforcement.

  3. Add the following command string to the rule parameters:

    set IsSticky 1

    Note: The set IsSticky 1 command is case-sensitive. Entering values other than 1 sets the rule to non-sticky mode.

  4. Enforce the policy to target endpoints.

Example to make any expert rule “Sticky”:

Rule {

set IsSticky 1

    Process {

        Include OBJECT_NAME { -v "powershell.exe"}

    }

    Target {

        Match FILE {

            Include OBJECT_NAME { 

                -v "C:\\Program Files\\**.exe"

            }

            Include -access "CREATE EXECUTE WRITE"

        }              

    }

}


Verify sticky rule enforcement using query info XML

Confirm that the system categorizes rules correctly in the client policy configuration file.

Procedure

  1. Generate the query info XML file on the client system.

  2. Open the query info XML file in a text viewer.

  3. Navigate to the Access Control policy section.

  4. Verify the rule attributes:

    • Sticky rules display IsSticky set to true.

    • Non-sticky rules display IsSticky set to false.

  5. Trigger the configured rule event.

  6. Confirm that the system generates the event alert while the service remains stopped.

Sticky rule policy XML element syntax definitions

Look up Access Control XML schema elements used to designate rule execution behavior.

XML Attribute / Element

Accepted Values

Description

set IsSticky 1

1, 0

Command string added to expert rule definitions. Setting to 1 enables sticky mode.