--- title: "Create an attack definition" slug: "create-an-attack-definition" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:36Z published: 2026-10-05T15:40:36Z canonical: "docs.trellix.com/create-an-attack-definition" --- > ## 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. # Create an attack definition To create the attack definition for this example: ## Task 1. In the Custom Attack Editor, click ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-F3F18CF8-B95D-4C8C-8DB8-996CDB6087FB-low.png?sv=2026-02-06&spr=https&st=2026-11-22T17%3A38%3A55Z&se=2026-11-22T18%3A38%3A55Z&sr=c&sp=r&sig=EPJZU9vyD8KuOubyMhmrkxQO%2F8g06Lmh7nOSG41VmAg%3D). The **New Custom Attack** interface opens. 2. Select one of the options from the **State** drop-down menu. 3. You can specify a name such as "CGI: Trillion or Trilliant" as the **Name**. The letters "UDS" (user-defined signature) are appended to the front of the name upon completion; thus, this attack appears as "UDS-CGI: Trillion or Trilliant" in the Custom Attack Editor, as well as the attack database when you save in the Manager server. 4. Type a description for your attack. This area can be used for your notes or other specific information pertinent to your new attack. 5. You can select **Medium** as the **Severity** because this example scenario does not necessarily involve malicious activity. 6. Select **Advanced Protection Options/Web Application Server Protection** as the **Protection Category**. 7. Select **URL** from the **Detection Type** drop-down menu for the attack. 8. Enter the **URL** that is to be detected, then click **Add**. 9. In the **Matching Criteria** section, the protocol is automatically selected as **http**. When you subsequently save this attack definition in the Manager server, it will be part of every rule set which includes Medium-severity, HTTP attacks (must match both severity and protocol). 10. Attack details configuration is complete. Continue to create signature.