--- title: "Cloning an alert policy exception using the Web UI" slug: "cloning-an-alert-policy-exception-using-the-web-ui" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-09-12T20:42:40Z published: 2026-09-12T20:42:40Z canonical: "docs.trellix.com/cloning-an-alert-policy-exception-using-the-web-ui" --- > ## 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. # Cloning an alert policy exception using the Web UI Follow these steps to clone an alert policy exception using the Web UI. ![NX_APE_clone.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-05fa93ca-228f-24ef-6e7f-3d9bb9d08832.png?sv=2026-02-06&spr=https&st=2026-11-20T02%3A04%3A56Z&se=2026-11-20T03%3A04%3A56Z&sr=c&sp=r&sig=i4fOTQ7GxMgOvPNwEdLrs%2Bb0dubsh99uS8aGxtWoDtI%3D) ### *Prerequisites* - Admin or Operator access to the appliance. **To clone an alert policy exception:** 1. Choose **Settings > Alert Policy Exceptions**. 2. For the exception you want to clone, click the operations icon ( ![NX_APE_list_iconActions.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9c879548-2feb-857e-08ba-80163f77d96c.png?sv=2026-02-06&spr=https&st=2026-11-20T02%3A04%3A56Z&se=2026-11-20T03%3A04%3A56Z&sr=c&sp=r&sig=i4fOTQ7GxMgOvPNwEdLrs%2Bb0dubsh99uS8aGxtWoDtI%3D) ) and choose **Clone**. ![NX_APE_listEntry_operations.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-c2a7ed65-5977-2d22-b2e9-adc944774900.png?sv=2026-02-06&spr=https&st=2026-11-20T02%3A04%3A56Z&se=2026-11-20T03%3A04%3A56Z&sr=c&sp=r&sig=i4fOTQ7GxMgOvPNwEdLrs%2Bb0dubsh99uS8aGxtWoDtI%3D) 3. (Optional) Specify a different policy exception type: **Using Signature ID** In the Signature ID field, enter the eight-digit ID of the alert rule to which the policy exception is to be applied. **Using Signature Name** In the Signature Name field, enter the name of the vulnerability that encompasses all of the alert rules to which the policy exception is to be applied. > [!NOTE] > Note > > To configure a policy exception that matches all signatures, select **Using Signature Name** and enter **ALL** in the Signature Name field. **Using Attack Category** In the Attack Category list, choose the category that encompasses all of the alert rules to which the policy exception is to be applied. 4. (Optional) Specify a different source, destination, or both: - To change the source machine or subnet, use the Source IP/Mask field. Leave the field empty to match any source address. - To change the destination machine or subnet, use the Destination IP/Mask field. Leave the field empty to match any destination address. 5. (Optional) Use the Interface drop-down to specify a different interface: all monitoring port pairs, a single monitoring port pair, or the management interface. 6. (Optional) Use the Action drop-down to specify a different override action. For more information, see [Alert policy exception actions](/network-and-platform/docs/alert-policy-exception-actions). 7. If you changed one or more options, you can also change the note attached to the policy exception. 8. Click **Save**.