The new docs.trellix.com features a modernized UI and AI-powered conversational search. Content is currently available in English, with additional languages expected in November 2026. We hope you enjoy the updated experience.

Exceptions

Prev Next

IPS Exception Rules migrate to Access Protection and Exploit Prevention policies according to these guidelines.

Exceptions can have custom signatures, McAfee-defined (canned) signatures, a mixture of both types, or no signature.

  • Custom signature exceptions migrate to the Access Protection policy.
  • McAfee-defined exceptions migrate to the Exploit Prevention policy.
  • Global exceptions migrate to both policies.

Custom signature exceptions (Files/Registry/Programs/Service)

  • Exceptions with custom signatures migrate to the Access Protection Rules that were created during IPS Signature migration.

    Note

    Trellix ENS for Linux supports only the Files type subrules.

  • Executables from IPS Exceptions that have custom Files/Registry/Programs/Service signatures migrate to Executables in the Files/Registry/Programs/Service Rules. If an Exception has more than one executable for a Files/Registry/Programs/Service Rules custom signature, all executables migrate as Executables.
  • Exceptions: Executables migrate to Files/Registry/Programs/Service rules from only custom signatures.
  • Exceptions: Programs signature: Target executables migrate to the Target executable for the Process subrule.
  • For exceptions with Handler Module or Caller Module parameters, only the executables migrate. Handler Module or Caller Module parameters don't migrate.
  • Domain Group parameters don't migrate.
  • Exceptions with two or more of these parameters defined do not migrate:
    • Target Executable
    • Files parameter (Files, dest_file, and/or drive typeFiles)

      Note

      Trellix ENS for Linux supports only the Files parameter (Files, dest_file).

    • Registry (Key)
    • Registry (Value)
    • Service parameter (Display Name or Services)
  • Exceptions migrate to Process Rules when they:
    • Do have Target Executable.
    • Don't have Files parameter (Files, dest_file, and/or drive type).
    • Don't have Registry (Key).
    • Don't have Registry (Value).
    • Don't have Service parameter (Display Name or Services).

    If the exceptions have executables, the executables migrate to Process Rule level, and target executables migrate to Process Rule: Subrule parameters.

  • Exceptions migrate to File Rules when they:
    • Do have the Executable OR Files parameter (Files, dest_file, and/or drive type).
    • Don't have Target Executable.
    • Don't have Registry (Key).
    • Don't have Registry (Value).
    • Don't have Service parameter (Display Name or Services).

    If the exceptions have executables, the executables migrate to the File Rule level. If the exceptions have the Files parameter (Files, dest_file, and/or drive type), they migrate to File Rule: Subrule parameters.

  • Exceptions migrate to Registry Key Rules when they:
    • Do have the Executable OR Registry (Key) parameter.
    • Don't have Target Executable.
    • Don't have Files parameter (Files, dest_file, and/or drive type).
    • Don't have Registry (Value).
    • Don't have Service parameter (Display Name or Services).

    If the exceptions have executables, the executables migrate to the Key Rule level. If the exceptions have the Key parameter, they migrate to Key Rule: Subrule parameters.

  • Exceptions migrate to Registry Value Rules when they:
    • Do have the Executable OR Registry (Value) parameter.
    • Don't have Target Executable.
    • Don't have Files parameter (Files, dest_file, and/or drive type).
    • Don't have Registry (Key).
    • Don't have Service parameter (Display Name or Services).

    If the exceptions have executables, the executables migrate to the Value Rule level. If the exceptions have the Value parameter, they migrate to Value Rule: Subrule parameters.

  • Exceptions migrate to Service Rules when they:
    • Do have the Executable OR Service parameter (Display Name or Services).
    • Don't have Target Executable.
    • Don't have Files parameter (Files, dest_file, and/or drive type).
    • Don't have Registry (Key).
    • Don't have Registry (Value).

    If the exceptions have executables, the executables migrate to the Service Rule level. If the exceptions have the Service parameter (Display Name or Services), they migrate to Service rule: Subrule parameters.

  • User name applies to all three categories, in a similar way to the executables previously described. If User name migrates with the executables to Access Protection Rules, the migrated Access Protection Rules have both the executable and user name.

McAfee-defined signature exceptions

  • All McAfee-defined signatures supported in the Threat Prevention Exploit Prevention policy are migrated (for example, Buffer Overflow and Illegal API Usage).
  • If an exception has more than one executable, handler, or caller module, only the first executable, handler, or caller module migrates.
  • Exploit Prevention doesn't support exclusion name, so Executable name doesn't migrate to Exploit Prevention.
  • Domain Group parameters don't migrate.

Global exceptions

Global exceptions migrate to both the Access Protection and Exploit Prevention policies as global exclusions in a similar way to the exceptions previously described. An exception is considered global if it has no signatures added or has all the Trellix-defined signatures added but no custom signatures.

  • Exceptions with two or more of these parameters defined don't migrate:
    • Target Executable
    • Files parameter (Files, dest_file, and/or drive type)
    • Registry (Key)
    • Registry (Value)
    • Service parameter (Display Name and/or Services)