Deploy Aikido Device Protection with Miradore
Use Miradore to deploy Aikido Device Protection across your managed macOS fleet with the required permissions in place.
Deploying packages and scripts requires a Miradore Premium or Premium+ subscription.
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 the Miradore admin console, go to Management → Configuration profiles.
Click Add → macOS → Advanced (custom).
Upload the downloaded
.mobileconfigfile.Click Save.
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
In the Miradore admin console, go to Management → Configuration profiles.
Click Add → macOS → Certificate.
Upload the Shared Root CA Certificate (
.pemfile) and click Save.
Create the pre-install token script
Miradore runs scripts as separate application items. Create a script that writes the token to disk before the package installs.
In the Miradore admin console, go to Management → Applications.
Click Add → macOS application → Script → Next.
Give it a name (e.g. "Aikido Device Protection - token").
Paste the script below into the Script field. 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.txtClick Create.
Upload the Aikido Device Protection installer
In the Miradore admin console, go to Management → Applications.
Click Add → macOS application → PKG (Uploaded) → Next.
Click Select file and upload the Aikido Device Protection
.pkg.Fill in the required fields:
Application name (e.g. "Aikido Device Protection")
Bundle identifier (e.g.
dev.aikido.endpoint)Version
Click Create and wait for the package to finish processing before continuing.
Reboot devices after installation
Restart your target devices after the agent installation completes. The agent fully activates on the next boot.
Deploy in the right order using a Business Policy
Use a Business Policy to deploy all five items in the correct order.
In the Miradore admin console, go to Management → Business policies.
Click Add, give the policy a name, and set its status to Disabled.
Add all five items to the policy: the configuration profile, the CA certificate, the token script, the
.pkg, and the restart script.Set the deployment order using item dependencies:
Select the CA certificate, click Actions → Edit item dependency, and set the configuration profile as its dependency.
Select the token script, click Actions → Edit item dependency, and set the CA certificate as its dependency.
Select the
.pkg, click Actions → Edit item dependency, and set the token script as its dependency.Select the restart script, click Actions → Edit item dependency, and set the
.pkgas its dependency.
Assign the policy to your target devices using tags.
Set the policy status to Enabled.
Miradore only supports one dependency per item. The chain must be: configuration profile → CA certificate → token script → package → restart script.
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.
To review deployment status, go to Management → Action log and filter by "Business policy" in the Sender field.
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?