# 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.

{% hint style="info" %}
These steps use Jamf Pro. If you use Jamf School, the menus and payload names can differ.
{% endhint %}

## Installation

{% stepper %}
{% step %}
**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](https://app.aikido.dev/endpoint-protection/devices), click **Connect Device**, and complete the pre-flight steps.
{% endstep %}

{% step %}
**Add the Aikido Device Protection configuration profile**

1. [Download the Aikido `.mobileconfig` file](https://raw.githubusercontent.com/AikidoSec/safechain-internals/refs/heads/main/docs/aikido-endpoint.mobileconfig).
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.
{% endstep %}

{% step %}
**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 (`.crt` file).
   1. You can convert the **pem file to crt** using the following command `openssl x509 -outform der -in your-cert.pem -out your-cert.crt`
3. Scope it to the same target devices as the configuration profile.
   {% endstep %}

{% step %}
**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.
   {% endstep %}

{% step %}
**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.

```bash
#!/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.txt
```

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

{% step %}
**Deploy in the right order**

The profile and CA certificate must be on the device before the installer, or macOS will prompt users for permission.

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.
   {% endstep %}

{% step %}
**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.
{% endstep %}

{% step %}
**Verify the deployment**

On a test device, confirm:

1. The system extension is activated:

   ```bash
   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.
   {% endstep %}
   {% endstepper %}

## 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                       |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.aikido.dev/aikido-device-protection/deploying-aikido-endpoint/deploy-aikido-endpoint-with-jamf.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.