--- title: "Considerations for rules converted with warnings" slug: "considerations-for-rules-converted-with-warnings-3" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:30:51Z published: 2026-11-19T12:30:51Z canonical: "docs.trellix.com/considerations-for-rules-converted-with-warnings-3" --- > ## 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. # Considerations for rules converted with warnings Some valid rules may convert with conversion result as **Warning**. The conversion result is displayed in the **Validation Results** column. By default, rules with **Warning** are set to **Staged**. There are two reasons why rules convert with a warning. - Rules for which there is an equivalent Trellix IPS signature in the Manager are converted with warnings. The Manager identifies such rules based on the CVE ID mentioned in the rule and the signature. You can click on an excluded attack and change its State to **Published**. You can specify your preference in the Custom Attack Editor so that, going forward, the duplicate Snort custom attacks are published in the corresponding policies by default. For information on how to set this preference, see the section [Check for overlaps with Trellix IPS attacks](/network-and-platform/docs/check-for-overlaps-with-trellix-ips-attacks-2). - Rules that do not have certain rule options are converted with a warning. However, based on your requirement, you can set such rules to **Published** state. It is recommended that you investigate such rules to check if they impact Sensor performance. If so, fix the rules before you publish them in the rule sets.