--- title: "Migration notes for IPS Rules settings" slug: "migration-notes-for-ips-rules-settings" tags: ["Migration", "ENS 10.7.x"] updated: 2026-10-07T18:04:46Z published: 2026-10-07T18:04:46Z canonical: "docs.trellix.com/migration-notes-for-ips-rules-settings" --- > ## 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. # Migration notes for IPS Rules settings During the migration process to Trellix ENS, the Endpoint Migration Assistant moves your migrated **IPS Rules** and **IPS Protection** policy settings into Threat Prevention policies. See the IPS Rules migration appendix for more information about how IPS Rules are migrated to Trellix ENS policies. ## Policy settings that are migrated These settings are migrated: - IPS signatures (Windows and Linux) - IPS Application Protection rules (Windows and Linux) - IPS exceptions (Windows and Linux) - IPS Expert rules ## IPS signatures The **Severity level** and **Log status** settings from the **IPS Rules** policy merge with the **Reaction** setting from the **IPS Protection** policy to determine the **Block/Report** settings for migrated Rules in Threat Prevention. - **IPS custom signatures** IPS custom signatures with IDs in the 4001–6000 range migrate to Access Protection custom rules. - IPS custom signature subrules for files, registry, programs, and services migrate. - Each subrule of a signature migrates as an individual Access Protection custom rule in Threat Prevention. - The same signature settings (name, severity, notes, and description) migrate to all rules created in Threat Prevention for all IPS subrules of the signature. - A signature name is required. If a signature doesn't have name, the rules using the signature don't migrate. - **IPS McAfee-defined signatures** All McAfee-defined signatures supported in the Threat Prevention Exploit Prevention policy are migrated. Most of these are Buffer Overflow and Illegal API Usage signatures. ## Application Protection Rules Excluded applications from Application Protection rules migrate to the Exploit Prevention policy as Application Protection rules. User-defined Application Protection rules for included processes in McAfee Host IPS are not migrated to Exploit Prevention. > [!NOTE] > Important > > Access Protection port-blocking rules, either predefined or user-defined, are not migrated. User-added inclusions and exclusions for predefined rules are also not migrated. ## Exception Rules Exception Rules from the **IPS Rules** policy migrate to the **Access Protection** and **Exploit Prevention** policies as executables under **Exclusions**. | Source Exception | Signature type | Target Trellix ENS policy | Target setting | | --- | --- | --- | --- | | Executables, Caller module, and API | All McAfee-defined signatures supported in the Threat Prevention Exploit Prevention policy (for example, Buffer Overflow and Illegal API Usage signatures) | **Exploit Prevention** | Exclusions | | Executables and Parameters | FILE/REGISTRY/PROGRAM/SERVICE signatures | **Access Protection** | Executables and subrule Parameters | | Executables | No signature | **Access Protection** **Exploit Prevention** | Global Exclusions | | GPEP (General Privilege Escalation Prevention) signature | Severity/reaction signature (ID 6052) | **Exploit Prevention** | Enable General Privilege Escalation Prevention | ## Exception Rules with signatures **IPS Exceptions** can include custom signatures. The executables and parameters from exceptions are appended to the Trellix ENS Access Protection Rule created during signature migration. If all McAfee-defined signatures are added to a subrule exception, the exception migrates as a global exclusion in the **Access Protection** and **Exploit Prevention** policies. ## IPS Expert Rules Expert Rules, created as a subrule in the IPS Rules policy to protect system resources, migrate to the Threat Prevention Exploit Prevention policy. Exploit Prevention uses two different Trellix Technologies in Expert Rules to manage the control of these resources: - McAfee Host IPS-based rules — Prevent buffer overflow and illegal API use, and protects Windows Services. - Arbitrary Access Control (AAC) rules — Protect files, processes, and registry items. Therefore, some Expert Rules defined in Host IPS do not migrate to Endpoint Security and must be re-created using the AAC syntax. | Resource protected (legacy Class type) | Migrated? | Notes | | --- | --- | --- | | Services (valid for Windows 8.0 and earlier) | Yes | No additional action required. Migrated with the source policy where they appear. | | Buffer Overflow | | Illegal API | | File | No | Re-create the rules using AAC syntax. | | Registry | | Program | No | Re-create the rule with a class type of Process using AAC syntax. |