Deploy Device Protection with Iru / Kandji

Use Iru / Kandji to roll out Aikido Device Protection across your organization and protect managed macOS devices with a consistent setup.

Installation

1

What you'll need

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

• The Aikido Device Protection .mobileconfig (downloaded from the Aikido Device Protection dashboard)
• The Aikido Device Protection installer (.pkg file, downloaded from 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

Upload the Aikido Device Protection configuration profile to Iru

1. In Iru, go to the Library.
2. Upload the .mobileconfig file as a Custom Profile.
3. Assign it to the same Blueprint as the app.

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

Upload the Aikido Device Protection installer

1. In Iru, add the Aikido Device Protection .pkg as a custom app.
2. Assign the app to the same Blueprint.

4

Deploy in the right order

Deploy the configuration profile before the installer for a smoother rollout.

1. Deploy the Aikido Device Protection configuration profile
2. Verify it has reached all target devices before continuing. Check status in the Iru console.
3. Deploy the Aikido Device Protection app

5

Reboot devices after installation

Restart your target devices after the agent installation completes. The agent fully activates on the next boot.

6

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