Deploy Aikido Device Protection with SimpleMDM
Use SimpleMDM to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.
Installation
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 (
.pemfile — downloaded in the dashboard)The Aikido Device Protection installer (
.pkgfile — 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.
Add the Aikido Device Protection configuration profile
In SimpleMDM, go to Profiles and click New Profile.
Select Custom Configuration Profile as the profile type.
Give it a name (e.g. "Aikido Device Protection").
Upload the downloaded
.mobileconfigfile, or open it in a text editor and paste its XML contents.Click Create Profile.
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.
Deploy the Aikido Device Protection CA certificate
Convert the Shared Root CA Certificate from
.pemto.crt:
openssl x509 -outform der -in your-cert.pem -out your-cert.crtCreate a
.mobileconfigprofile containing a Certificates payload with the.crtfile embedded. You can do this with Apple Configurator 2 (free from the Mac App Store): open it, create a new profile, add a Certificates payload, import your.crtfile, and export as.mobileconfig.In SimpleMDM, go to Profiles → New Profile → Custom Configuration Profile.
Give it a name (e.g. "Aikido Device Protection Certificate").
Upload the exported
.mobileconfigfile.Click Create Profile.
Create the pre-install token script
SimpleMDM runs scripts separately from package installs, so you must run this script and confirm it completes on all target devices before deploying the package.
In SimpleMDM, go to Scripts and click New Script.
Give it a name (e.g. "Aikido Device Protection Token").
Paste the script below. Replace
AIK_SAFE_CHAIN_TOKENwith your real token.
#!/bin/zsh
# Write the token so the agent registers with the correct user group
echo "AIK_SAFE_CHAIN_TOKEN" > /tmp/aikido_endpoint_token.txt
# Signals the installer to run completely silently, with no user prompts
touch /tmp/aikido_endpoint_mdm_install.txtSet Run As to Root.
Click Save Script.
Upload the Aikido Device Protection installer
In SimpleMDM, go to Apps and click Add App.
Select macOS Package.
Upload the Aikido Device Protection
.pkgfile.Click Save App.
Do not assign this app to your devices yet — wait until the profiles and token script are confirmed deployed in the next step.
Deploy in the right order
Deploy the configuration profile and CA certificate before the installer for a smoother rollout.
Go to Devices → Groups and select your target device group.
On the Profiles tab, assign both the Aikido Device Protection configuration profile and the Aikido Device Protection Certificate profile.
Go to Scripts, open the Aikido Device Protection Token script, and click New Job.
Scope the job to the same device group and run it. Wait for all devices to report a successful run before continuing.
Back in the device group, open the Apps tab and assign the Aikido Device Protection package.
Reboot devices after installation
In SimpleMDM, go to Devices and select each target device.
Click Actions and select Restart.
The Restart action requires devices to be supervised. If your devices are not supervised, trigger a reboot via a script job that runs sudo reboot.
The agent fully activates on the next boot.
Verify the deployment
On a test device, confirm:
The system extension is activated:
systemextensionsctl list | grep aikidoExpect to see the extension marked
[activated enabled].Open System Settings → General → Login Items & Extensions and confirm the Aikido Device Protection entries cannot be toggled off.
Troubleshooting
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
Last updated
Was this helpful?