Deploy Aikido Device Protection with Jamf

Use Jamf Pro to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.

These steps use Jamf Pro. If you use Jamf School, the menus and payload names can differ.

Installation

1

What you'll need

Before starting, make sure you have the following from the Aikido Device Protection dashboard:

• Your Device Protection Token (copied from the user group selector)

• The Shared Root CA Certificate (.pem file — downloaded in the dashboard)

• The Aikido Device Protection installer (.pkg file — downloaded in the dashboard)

If you're missing any of these, go back to the Aikido Device Protection dashboard, click Connect Device, and complete the pre-flight steps.

2

Add the Aikido Device Protection configuration profile

1. Download the Aikido .mobileconfig file.

2. In Jamf Pro, create or upload a Configuration Profile for macOS.

3. Upload the downloaded .mobileconfig file.

4. Scope it to the target devices.

This profile allows the Aikido Device Protection system extension to load silently, enables the network content filter, and stops users from disabling background services in System Settings → Login Items.

3

Deploy the Aikido Device Protection CA certificate

1. In Jamf Pro, go to Computers → Configuration Profiles.

2. Create a new profile, add a Certificates payload, and upload the Shared Root CA Certificate (.pem file).

3. Scope it to the same target devices as the configuration profile.

4

Upload the Aikido Device Protection installer

1. In Jamf Pro, go to Computers → Packages.

2. Upload the Aikido Device Protection .pkg.

3. Confirm the package finishes processing before you use it in a policy.

5

Create the install policy

1. In Jamf Pro, go to Computers → Policies.

2. Create a new policy scoped to the same devices.

3. Add a script that writes the token before the package installs.

4. Add the uploaded Aikido Device Protection package to the policy.

Use this script. Replace AIK_SAFE_CHAIN_TOKEN with your real token.

#!/bin/zsh
echo "AIK_SAFE_CHAIN_TOKEN" > /tmp/aikido_endpoint_token.txt

If you use a recurring check-in trigger, keep the policy available only after the profiles are scoped.

6

Deploy in the right order

Order matters. Both the configuration profile and the CA certificate must reach the device before the pkg. If the pkg installs first, macOS can ask the user for extra permissions.

1. Deploy the Aikido Device Protection configuration profile.

2. Deploy the Aikido Device Protection CA certificate.

3. Verify both have reached all target devices before continuing — check profile and certificate status in the Jamf Pro console.

4. Deploy the Aikido Device Protection install policy.

7

Reboot devices after installation

1. In Jamf Pro, go to Computers → Policies and create a new policy.

2. Add a Restart Options payload and set it to Restart.

3. Scope it to the same target devices and trigger it after the agent package has installed.

The agent fully activates on the next boot.

8

Verify the deployment

On a test device, confirm:

1. The system extension is activated:

   systemextensionsctl list | grep aikido

   Expect to see the extension marked [activated enabled].

2. Open System Settings → General → Login Items & Extensions and confirm the Aikido Device Protection entries cannot be toggled off.

Troubleshooting

Problem	Fix
Users still see the popup	Make sure the configuration profile is scoped correctly and installed before the package policy runs
Extension is waiting for user approval	Check the System Extensions payload and confirm the team ID and bundle ID match exactly
The package installs but the device does not connect	Confirm the token script ran before the package install and that the token was copied correctly
Duplicate extension entries appear	Reboot the device
The content filter is not approved silently	Re-upload the .mobileconfig profile and verify it is installed on the device