--- title: "Create an attack definition for numeric enumeration match" slug: "create-an-attack-definition-for-numeric-enumeration-match-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:31:15Z published: 2026-11-19T12:31:15Z canonical: "docs.trellix.com/create-an-attack-definition-for-numeric-enumeration-match-2" --- > ## 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 for numeric enumeration match This scenario is about creating a Custom Attack Definition that uses numeric enumeration match to detect if the HTTP response code is either 302 or 404. In order to write a proper Native Trellix IPS Format Custom Attack for this example, you must identify several key elements: - Application protocol: HTTP - Protocol field: rsp-code - Enumeration value (integer): 302 and 404 Steps to create the attack definition for this example: 1. In the Custom Attack Editor, click ![GUID-F3F18CF8-B95D-4C8C-8DB8-996CDB6087FB-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-e18ed793-87a1-f95c-1c5b-8e24a797ea67(8).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A36%3A50Z&se=2026-11-20T16%3A36%3A50Z&sr=c&sp=r&sig=IxggbyD06B%2F42NnmWNRlF3J7pURhOVNiL0irh8fsGGE%3D). The **New Custom Attack** interface opens. ![GUID-3EB7CCB4-A36F-41F8-BB0D-1EC2405A7B00-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-f5a1cb65-5f7d-cf7b-35d5-c3bc7cfd73b4(7).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A36%3A50Z&se=2026-11-20T16%3A36%3A50Z&sr=c&sp=r&sig=IxggbyD06B%2F42NnmWNRlF3J7pURhOVNiL0irh8fsGGE%3D) 2. Select one of the options from the **State** drop-down menu. 3. You can specify a name such as "Custom Exploit: Numeric Enumeration Match" 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-Custom Exploit: Numeric Enumeration Match" 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 (5)** as the **Severity** because this example scenario does not necessarily involve malicious activity. 6. Select **Advanced Protection Options/Web Application Server** as the **Protection Category**. 7. Select **Custom Exploit (Signature Based)** from the **Detection Type** drop-down menu for the attack. 8. Click **Next**. ![GUID-2C6E7820-F250-404D-BC53-B3A197BA66DA-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-ebf008a0-166b-5790-45c4-20ab36bb6203(7).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A36%3A50Z&se=2026-11-20T16%3A36%3A50Z&sr=c&sp=r&sig=IxggbyD06B%2F42NnmWNRlF3J7pURhOVNiL0irh8fsGGE%3D) 9. Select **Client or Server** as **Attack Target**. 10. Select **Attack Packet Only** as **Blocking (As Applicable)**. 11. In the **Matching Criteria** section, select **Protocol** as the **Criterion** and select **http** as the protocol. 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). ![GUID-1557B147-9214-42B5-B6AC-F6B4D66330F6-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-ca9c754b-9bed-90a1-605f-e4e453bc7c5b(7).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A36%3A50Z&se=2026-11-20T16%3A36%3A50Z&sr=c&sp=r&sig=IxggbyD06B%2F42NnmWNRlF3J7pURhOVNiL0irh8fsGGE%3D) 12. Attack details configuration is complete. Continue to create signature.