Configure the Gatekeeper Enhancement MPM

The Gatekeeper Enhancement MPM is an enhancement of the macOS gatekeeper functionality which allows apps to run based on their digital signature. The MPM provides an additional layer of protection by extending gatekeeper functionality to child processes to enforce the signature level of your choice (for example by
Apple System
,
Mac App Store
, or
Developers
).
By enforcing the signature level you can prevent attackers from leveraging a logical vulnerability in an existing process to bypass the OS verification of the signature level. You can also choose to allow child processes to run if they match (or exceed) the signature level of the parent process or you can block all child processes regardless of digital signature.
This module is enabled by default for select macOS apps and supported on Mac endpoints.
To configure the Gatekeeper Enhancement EPM, use the following workflow:
  1. Configure a new malware protection rule.
    Select
    Policies
    Malware
    Protection Modules
    .
  2. Select
    macOS
    as the operating system (the Gatekeeper Enhancement MPM is not supported on Windows endpoints).
  3. From the action menu , select
    Add
    .
  4. Select
    Gatekeeper Enhancement
    and configure the rule settings:
    • Activation
      —Select
      On
      to enable the gatekeeper enhancement MPM or
      Off
      to disable it.
    • Action
      —Select the action to take when Traps detects a child process which does not match or exceed the configured signature level: Block the behavior (
      Prevention
      ), or permit the behavior and log the issue (
      Notification
      ). Alternatively, you can choose to
      Inherit
      the behavior from the preceding rule in the rule hierarchy.
      To view additional details about the default policy, select Policies > Malware > Protection Modules, and then select Show Default Rules from the action menu.
    • User Alert
      —Specify the notification behavior when Traps detects a child process which does not match or exceed the configured signature level, either
      On
      to notify the user, or
      Off
      to suppress notifications. Alternatively, you can choose to
      Inherit
      the behavior from the preceding rule in the rule hierarchy.
  5. Select the signature
    Verification Level
    :
    • By Parent
      —(Default) The child process must match the signature level of the parent process.
    • Block All
      —Block all child processes regardless of signature level.
    • Apple System
      —The child process must be signed by Apple.
    • Mac App Store
      —The child process must be signed by the App Store.
    • Developers
      —The child process must be signed by a registered developer.
  6. (
    Optional
    ) Whitelist child processes run from specific locations:
    1. Select the add folder icon .
    2. Enter the full path for the child process, for example:
      /Applications/myapp1.app/Contents
    3. Repeat the process to add any additional child processes, if desired.
    4. Select the
      Whitelist Action
      to
      Merge
      or
      Override
      the child process list with lists defined in other user-defined or default policy rules for the parent process.
      If multiple rules exist for the same parent process that specify
      Whitelist Action: Merge
      , Traps consolidates the
      Whitelist
      . If multiple rules exist for the same parent process that specify
      Whitelist Action: Override
      , only the most recent rule (with the highest ID number) takes precedence.
      If multiple rules exist for the same parent process but use different list behaviors (for example, one as a whitelist and one as a blacklist), only the most recent rule (with the highest ID number) takes precedence.
  7. Select the
    Processes
    tab and
    Add
    one or more source (parent) processes to which Traps will apply the Gatekeeper Enhancement MPM. As you type, the ESM Console provides auto-completion based on the list of processes defined in the ESM Console.
  8. (
    Optional
    ) Add Conditions to the rule. By default, a new rule does not contain any conditions.
    To specify a condition, select the
    Conditions
    tab, select the condition in the Conditions list, and then
    Add
    it to the Selected Conditions list. Repeat this step to add more conditions, as needed. You can also define new Conditions.
  9. (
    Optional
    ) Define the Target Objects to which to apply the rule.
    To define a smaller subset of target objects, select the
    Objects
    tab, and then enter one or more
    AD Users
    ,
    AD Computers
    ,
    AD Groups
    ,
    AD Organizational Unit
    ,
    Existing Endpoints
    , or
    Existing Groups
    in the Include or Exclude areas. The Endpoint Security Manager queries Active Directory to verify the users, computers, groups, or organizational units. The ESM Console also offers autocompletion as you type for existing endpoints and existing virtual groups.
  10. (
    Optional
    ) Review the rule name and description. The ESM Console automatically generates the rule name and description based on the rule details but permits you to change these fields, if needed.
    To override the autogenerated name, select the
    Name
    tab, clear the
    Activate automatic description
    option, and then enter a rule name and description of your choice.
  11. Save the exploit protection rule.
    Do either of the following:
    • Save
      the rule without activating it. This option is only available for inactive, cloned, or new rules. When you are ready to activate the rule, select the rule from the
      Policies
      Exploit
      Protection Modules
      page and then click
      Activate
      .
    • Apply
      the rule to activate it immediately.
    After saving or applying a rule, you can return to the
    Protection Modules
    page at any time to
    Delete
    or
    Deactivate
    the rule.

Recommended For You