--- title: "Assigning multiple instances of Exploit Prevention policy" slug: "assigning-multiple-instances-of-exploit-prevention-policy-8" tags: ["Product Usage", "ENS 10.7.x"] updated: 2026-10-07T17:36:15Z published: 2026-10-07T17:36:15Z canonical: "docs.trellix.com/assigning-multiple-instances-of-exploit-prevention-policy-8" --- > ## 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. # Assigning multiple instances of Exploit Prevention policy Assigning one or more instances of the policy to a group or system in the Trellix ePO - On-prem System Tree provides for single policy multi-purpose protection. Exploit Prevention is a multiple-instance policy. This policy allows the application of more than one policy concurrently on a single client. All other policies in Trellix ENS are single-instance policies. When more than one instance is applied, what results is a union of all instances, called the effective policy. A multiple-instance policy can be useful for an IIS Server, for example, where you might apply a general default policy, a server policy, and an IIS policy, the latter two configured to specifically target systems running as IIS servers. When assigning multiple instances, you are assigning a union of all elements in each instance of the policy. To streamline your deployment, use multi-slot policy assignment. First, define groups of users for the deployment that have an essential property in common that dictates what resources need to be protected and what resources need exceptions to work properly. This property could be based on: - **Department** — Each department should require protection of a unique set of resources and exceptions for a unique set of business activities. - **Location** — Each location can have its own unique security standards or unique set of resources that need to be protected, and exceptions needed for business activity. - **Computer type** — Each type of computer (laptops, workstations, servers) might have a unique set of applications that need to be protected but also allowed to perform essential business functions. Without a multiple-instance IPS Rules policy, a combination of three departments, three locations, and three computer types would require 27 policies; with the multiple-instance approach, only nine are needed. > [!NOTE] > Note > > When the policies are merged, the most restrictive policy settings are combined to become the effective policy. 1. Click **Menu** → **System** → **System Tree** and select a group in the System Tree. 2. Under **Assigned Policies**, select **Endpoint Security Threat Prevention** in the **Product** list. 3. For **Exploit Prevention**, click **Edit Assignment** in the **Action** column. 4. On the **Policy Assignment** page, click **New Policy Instance**, and select a policy from the **Assigned Policies** list for the additional policy instance. 5. Click **Save** to save all changes. To view the effective or combined effect of multiple instance rule sets, click **View Effective Policy** under **Assigned Policies**.