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.

Subrule-level settings in migrated IPS Rules

Prev Next

Subrules migrate to Access Protection policies according to these guidelines.

General migration guidelines

  • Only Standard subrules migrate. Expert subrules don't migrate.
  • The signature subrule name is required. It migrates to the subrule name.
  • Subrules with these Rule types migrate: Files, Registry, Programs, and Service.

    Note

    Trellix ENS for Linux supports only the Files Rule type.

  • Subrules with a Rule type of Registry can have a parameter for Registry (Key) and Registry (Value). Its value determines where these subrules migrate in the Access Protection policy.
    • Rules with a Registry (Key) parameter migrate to a Registry Key type rule.
    • Rules with a Registry (Value) parameter migrate to a Registry Value type rule.
    • Rules with both parameters do not migrate.
  • Most operations migrate directly to the corresponding equivalent for their type. Special cases are described in the following sections. If source data is null or missing, it doesn't migrate.

Files subrules (Windows and Linux)

  • File parameter data is required. Subrules must have at least one parameter to migrate.
  • The Destination file parameter migrates only when Rename Operation is enabled.

    Note

    Trellix ENS for Linux also supports the Rename, Symlink, and Hardlink operations.

  • The User name parameter from the IPS subrule migrates to the User Names section in the target Rule.
  • (Windows only) The Drive type parameter migrates to the target subrule parameters list Drive Type as follows:
    • CD or DVD migrates to CD/DVD.
    • Floppy migrates to Floppy.
    • OtherRemovable or USB migrates to Removable.
    • HardDrive migrates to Fixed.
    • Network migrates to Network.

Registry subrules (Windows only)

  • Registry parameter data is required. Subrules must have a least one parameter to migrate.
  • If one subrule has parameters for both Registry (Key) and Registry (Value), the subrule doesn't migrate.
  • The User name parameter from the IPS subrule migrates to the User Names section in the target Rule.
  • Trellix ENS doesn't support the Registry Value Operation setting for Enumerate. If only this operation is defined for a registry subrule, the subrule doesn't migrate.

Programs subrules (Windows only)

  • Program parameter data is required. Subrules must have a least one parameter to migrate.
  • User name moves up to the rule level in Trellix ENS.
  • Caller module doesn't migrate.
  • Target Executable migrates to Process. If the source subrule doesn't specify a value for Target Executable, it doesn't migrate.
  • Trellix ENS doesn't support the Operation setting for Open with Access to wait. If only this operation is defined for a program subrule, the subrule doesn't migrate.

Service subrules (Windows only)

  • Service parameter data is required. Subrules must have a least one parameter to migrate.
  • User name moves up to the rule level in Trellix ENS.
  • Display name and Service name migrate to subrule.

Executables (Windows and Linux)

Executables in Files, Registry, and Programs subrules migrate to Rule-level executables.

Note

Trellix ENS for Linux supports only executables in Files subrules and only executables based on names.

  • Fingerprint migrates to MD5 hash.
  • Signer migrates.
  • File Description doesn't migrate.
  • (Windows only) Target Executable migrates to Process. If the source subrule doesn't specify a value for Target Executable, it doesn't migrate.