--- title: "Create a snort custom attack — an example" slug: "create-a-snort-custom-attack-an-example-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:27:57Z published: 2026-11-19T12:27:57Z canonical: "docs.trellix.com/create-a-snort-custom-attack-an-example-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 a snort custom attack — an example To write a Snort Custom Attack definition for the scenario explained in the previous section: **Steps:** 1. In the Custom Attack Editor, click **Snort Format** tab. 2. 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-20T13%3A36%3A57Z&se=2026-11-20T14%3A36%3A57Z&sr=c&sp=r&sig=9E%2B5cePo%2Fi%2BYgwigcfkUf84wtp9wmrApcbJ2oHbnCG0%3D). The **New Snort Rule** text box opens. 3. Select one of the options from the **State** drop-down menu. 4. Construct the Snort rule for the scenario, which is the following: alert tcp any any -> 192.168.1.1 80 (msg:"CGI: Trillion or Trilliant";content:"cgi.bin\trilli";http_uri;pcre:"/cgi.bin\trilli(on|ant).[Pp][Ll]/";priority:2;sid:2051;rev:1;) **Add Snort Rule window** ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/image(125).png?sv=2026-02-06&spr=https&st=2026-11-20T13%3A36%3A57Z&se=2026-11-20T14%3A36%3A57Z&sr=c&sp=r&sig=9E%2B5cePo%2Fi%2BYgwigcfkUf84wtp9wmrApcbJ2oHbnCG0%3D) Some points to note regarding the rule: - Specifying the destination IP address improves the performance of the Sensor. - As you are adding the Snort rule directly in the Custom Attack Editor, as a best practice, you need to specify the destination port number. The Sensor then checks only the HTTP request packet for this rule. - You need to specify the msg, priority, SID, and the revision number. 5. Select **Check for Overlap with Trellix IPS Attacks** to verify if the rule matches an existing Trellix IPS attack definition. 6. Select **Advanced Protection Options/Web Application Server Protection** as the **Protection Category**. 7. Select the **Supported Device Types**, from the available options: 1. **Any** 2. **NS-Series Only** 3. **VM-Series Only** 8. Select the **Supported Suricata Version**, from the available options: > [!NOTE] > Note > > By default, ‘**Any**‘ option is selected, if no selection is done for **Supported Device Types** and **Supported Suricata Version**. 1. **Any** 2. **Suricata 3.X Only** 3. **Suricata 8.X Only** 9. Click **Add**. The **Attack** window opens. **Edit Snort Attack window** ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/image(126).png?sv=2026-02-06&spr=https&st=2026-11-20T13%3A36%3A57Z&se=2026-11-20T14%3A36%3A57Z&sr=c&sp=r&sig=9E%2B5cePo%2Fi%2BYgwigcfkUf84wtp9wmrApcbJ2oHbnCG0%3D) 10. Note that the Manager assigns the Attack Name based on the msg option and SID of the rule. 11. Set the severity to Medium. This is because the priority of the rule is 2. 12. Note that the Protocol is set to **http**. This is because the destination port number is 80. 13. Note that the **Benign Trigger Probability** is set to the default value. 14. Close the Attack window. 15. In the **Custom Attacks** window, click **Save** to save the Snort Custom Attack in the Manager server database. 16. Make sure the Snort Custom Attack is saved in the database and also published in the policies.