--- title: "Effective policy tuning practices" slug: "effective-policy-tuning-practices" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-09-06T12:33:31Z published: 2026-10-05T15:41:20Z canonical: "docs.trellix.com/effective-policy-tuning-practices" --- > ## 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. # Effective policy tuning practices All Sensors on initial deployment have the 'Default Prevention' policy loaded on all interfaces. Trellix recommends that you use the Default Prevention policy as a starting point, and then customize the policies based on your organization's requirements. The customized policies can be either cloned versions of the default pre-configured policies, or custom-built policies that employ custom rule sets. An appropriately tuned policy will reduce false positives. Though each network environment has unique characteristics, the best practices outlined in this section can make tuning more efficient and effective. > [!NOTE] > Note > > As you interact with Trellix IPS policies, you encounter the term "attack", not "signature". Trellix IPS defines an attack as being comprised of one or more signatures, thresholds, anomaly profiles, or correlation rules, where each method is used to detect an attempt to exploit a particular vulnerability in a system. These signatures and checks may contain very specific means for identifying a specific known exploit of the vulnerability, or more generic detection methods that aid in detecting unknown exploits for the vulnerability.