--- title: "Suricata Snort" slug: "suricata-snort-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:30:36Z published: 2026-11-19T12:30:36Z canonical: "docs.trellix.com/suricata-snort-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. # Suricata Snort The Suricata Snort engine provides a dedicated Snort environment and supports many of the open-source Snort constructs that are available in the public domain. This allows you to import most custom and third-party Snort rules without modification. Trellix IPS uses Suricata Snort version **8.0.5**. The usage of some of the constructs differs in Suricata Snort when compared to the open-source Snort. See [https://docs.suricata.io/en/suricata-8.0.5/rules/http-keywords.html](https://docs.suricata.io/en/suricata-8.0.5/rules/http-keywords.html) for the list of supported constructs. The following is the list of considerations when using the Suricata Snort: - You cannot push the Suricata Reference config file to the Sensor. - You cannot import rule variables from the yaml file from the Emerging Threats. - You cannot exclude a rule for a particular snort engine. - **Alerts for some existing rules stopped on pre-11.1M12 Sensors after the Manager upgrade to 11.1M12**: After the upgrade, all rules are set to **Any** and are checked with the Suricata 8.x validator in the **Custom Attack Editor**. Rules that passed the **Suricata 3.x** check before the Manager upgrade but fail the 8.x check are now marked failed in the **Custom Attack Editor** and hence are no longer deployed to pre-11.1M12 Sensors. Edit each affected rule, set **Supported Suricata Version** to **Suricata 3.X** **Only**, and click **Save**. The rule is then checked with the Suricata 3.x validator at deploy time. - **A new rule fails to deploy on pre-11.1M12 Sensors**: The rule passes the Suricata 8.x check but does not work on Suricata 3.x, so deployment to pre-11.1M12 Sensors fails. Upgrade those Sensors to 11.1M12 (recommended). If you cannot upgrade yet, set the rule to **Suricata 8.X** **Only** so it is deployed only to 11.1M12 Sensors. Deployment to pre-11.1M12 Sensors then succeeds. Then, if possible, add an equivalent rule that works on Suricata 3.x, set it to **Suricata 3.X Only**, and deploy pending changes. This keeps the same attack coverage on pre-11.1M12 Sensors. > [!NOTE] > Note > > Starting from 11.1 Update 12, Suricata snort is available on all the Sensors except NS3100 and NS3200 Sensors.