Deploy Elastic Defend on macOS with mobile device management

To silently install and deploy Elastic Defend, you need to configure a mobile device management (MDM) profile for Elastic Endpoint—the installed component that performs Elastic Defend's threat monitoring and prevention. This allows you to pre-approve the Elastic Endpoint system extension and grant Full Disk Access to all the necessary components.

This page explains how to deploy Elastic Defend silently using Jamf. First, configure a Jamf MDM profile for Elastic Endpoint. For macOS Ventura (13) and later, also configure Managed Login Items in a separate profile to prevent users from disabling Elastic Agent in Login Items.

In Jamf, create a configuration profile for Elastic Endpoint. Follow these steps to configure the profile:

1. Approve the system extension.
2. Approve network content filtering.
3. Enable notifications.
4. Enable Full Disk Access.

1. Select the System Extensions option to configure the system extension policy for the Elastic Endpoint configuration profile.

2. Make sure that Allow users to approve system extensions is selected.

3. In the Allowed Team IDs and System Extensions section, add the Elastic Endpoint system extension:

   1. (Optional) Enter a Display Name for the Elastic Endpoint system extension.
   2. From the System Extension Types dropdown, select Allowed System Extensions.
   3. Under Team Identifier, enter 2BT3HPN62Z.
   4. Under Allowed System Extensions, enter co.elastic.systemextension.

4. Save the configuration.

×

1. Select the Content Filter option to configure the Network Extension policy for the Elastic Endpoint configuration profile.

2. Under Filter Name, enter ElasticEndpoint.

3. Under Identifier, enter co.elastic.endpoint.

4. In the Socket Filter section, fill in these fields:

   1. Socket Filter Bundle Identifier: Enter co.elastic.systemextension

   2. Socket Filter Designated Requirement: Enter the following:

      identifier "co.elastic.systemextension" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2BT3HPN62Z"
      		

5. In the Network Filter section, fill in these fields:

   1. Network Filter Bundle Identifier: Enter co.elastic.systemextension

   2. Network Filter Designated Requirement: Enter the following:

      identifier "co.elastic.systemextension" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2BT3HPN62Z"
      		

6. Save the configuration.

×

1. Select the Notifications option to configure the Notification Center policy for the Elastic Endpoint configuration profile.

2. Under App Name, enter Elastic Security.app.

3. Under Bundle ID, enter co.elastic.alert.

4. In the Settings section, include these options with the following settings:

   1. Critical Alerts: Enable
   2. Notifications: Enable
   3. Banner alert type: Persistent
   4. Notifications on Lock Screen: Display
   5. Notifications in Notification Center: Display
   6. Badge app icon: Display
   7. Play sound for notifications: Enable

5. Save the configuration.

×

1. Select the Privacy Preferences Policy Control option to configure the Full Disk Access policy for the Elastic Endpoint configuration profile.

2. Add a new entry with the following details:

   1. Under Identifier, enter co.elastic.systemextension.

   2. From the Identifier Type dropdown, select Bundle ID.

   3. Under Code Requirement, enter the following:

      identifier "co.elastic.systemextension" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2BT3HPN62Z"
      		

   4. Make sure that Validate the Static Code Requirement is selected.

   5. Under APP or SERVICE, select SystemPolicyAllFiles and set it to Allow.

3. Add a second entry with the following details:

   1. Under Identifier, enter co.elastic.endpoint.

   2. From the Identifier Type dropdown, select Bundle ID.

   3. Under Code Requirement, enter the following:

      identifier "co.elastic.endpoint" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2BT3HPN62Z"
      		

   4. Make sure that Validate the Static Code Requirement is selected.

   5. Under APP or SERVICE, select SystemPolicyAllFiles and set it to Allow.

4. Add a third entry with the following details:

   1. Under Identifier, enter co.elastic.elastic-agent.

   2. From the Identifier Type dropdown, select Bundle ID.

   3. Under Code Requirement, enter the following:

      identifier "co.elastic.elastic-agent" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = "2BT3HPN62Z"
      		

   4. Make sure that Validate the Static Code Requirement is selected.

   5. Under APP or SERVICE, select SystemPolicyAllFiles and set it to Allow.

5. Save the configuration.

×

After you complete these steps, generate the mobile configuration profile and install it onto the macOS machines. Once the profile is installed, Elastic Defend can be deployed without the need for user interaction.

On macOS Ventura (13) and later, users can disable Elastic Agent in System Settings → General → Login Items. That stops Elastic Agent and can make the host appear offline.

To prevent this, create a separate configuration profile with a Managed Login Items payload, and deploy it only to macOS 13 and later. If you install this payload on an earlier macOS version and later upgrade the Mac, the payload might not take effect.

1. Create a new configuration profile, then select the Managed Login Items payload.

2. Add a rule with the following details:

   1. From the Rule Type dropdown, select Label.
   2. Under Rule Value, enter co.elastic.elastic-agent.

3. Add a second rule with the following details:

   1. From the Rule Type dropdown, select Label.
   2. Under Rule Value, enter co.elastic.endpoint.

4. Save the configuration.

5. Deploy this configuration profile only to hosts running macOS Ventura (13) or later.