> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/developer-machines/installation/script/mdm-deployment/macos/jamf-pro.md).

# Jamf Pro

This guide walks through deploying Dev Machine Guard across your macOS fleet using **Jamf Pro**. The deployment uses a Jamf Pro **script** and a **policy** that runs the loader at every recurring check-in.

Two separate schedules are involved:

* **Jamf Pro recurring check-in frequency** controls how often Jamf Pro runs the loader on each computer. You set this once for your Jamf Pro instance, in Step 3 below.
* **Scan Schedule** controls how often a loader run performs a full scan. You set this once for the whole organization in the StepSecurity dashboard. Between scans, agent launches check in and exit without scanning.

To change how often devices are scanned, update the Scan Schedule in the StepSecurity dashboard. Your Jamf Pro configuration stays the same. See [Adjusting scan frequency](#adjusting-scan-frequency) below.

{% hint style="info" %}
The loader script shown in the StepSecurity dashboard is rendered with your tenant's credentials already embedded and works as-is. Restrict access to the script, and to the Jamf Pro script object that holds it, to authorized administrators. If you need to customize the script (alternative install directory, proxy, etc.), reach out to StepSecurity.
{% endhint %}

### Prerequisites

* Administrator access to Jamf Pro, with permission to manage scripts, policies, and check-in settings.
* macOS computers enrolled in and managed by Jamf Pro.
* A computer group for a pilot rollout, and the computers or computer groups for your full fleet.
* Outbound network access from managed computers to the endpoints listed in [Network requirements](https://docs.stepsecurity.io/developer-machines/installation.md#network-requirements).
* The Dev Machine Guard loader script for your tenant, generated in the StepSecurity dashboard (Step 1 below).

#### Step 1. Generate and copy the loader script

The **Installation Script** page builds the loader in a four-step wizard. The options you select are embedded in the generated script, so complete every step before you copy it.

* Sign in to the [StepSecurity dashboard](https://app.stepsecurity.io/).
* In the sidebar, go to **Developer Machines → Installation Script**.
* **Operating system:** select **macOS**, then select **Continue**.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FqHZyKVU7YfM4VcH4uRON%2FScreenshot%202026-10-19%20at%2012.14.32.png?alt=media&amp;token=e24cb7f5-2c8b-4414-8473-5ec1404a5a55" alt=""><figcaption></figcaption></figure>

* **Deployment pattern:** under **Scale deployment via MDM**, select **MDM-scheduled**, then select **Continue**. With this pattern, your mobile device management (MDM) tool runs the script on a recurring schedule, which is how Jamf Pro runs it in this guide.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2Fdhbjab4EH5qMTo9gW95o%2FScreenshot%202026-10-19%20at%2012.14.45.png?alt=media&amp;token=ae56fedf-85a8-4553-aefa-9e64756d1e6f" alt=""><figcaption></figcaption></figure>

* **Configuration:** set the following, then select **Continue**.
  * **Agent version:** keep **Latest** so the agent resolves the newest release on each run and devices update automatically. Select **Pin specific version** instead if you need change-controlled rollouts. See [Auto-updating](https://docs.stepsecurity.io/developer-machines/installation/script.md#auto-updating).
  * **Update policy override** (optional): holds this script's installs behind new releases. It takes priority over the organization update policy in Settings. Leave it unset to follow the organization policy.
  * **Inactive threshold:** the number of days without telemetry before a device is marked inactive. This value applies to all devices in your organization and is saved to your organization settings when you generate the script.
  * **Advanced configuration** (optional): install location, scan scope, and package scanners. If you plan to grant Full Disk Access with a Privacy Preferences Policy Control (PPPC) profile, set a fixed system-wide install directory here. See [macOS TCC permissions](https://docs.stepsecurity.io/developer-machines/installation/script/mdm-deployment/macos.md#macos-tcc-permissions).
* **Review & generate:** confirm the summary matches your selections (hover a field to edit it), then select **Generate script**.
* Copy the generated loader script, or select **Download** to save it as a file.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2Fnk3XbsJA0By9d5Rfc4Le%2FScreenshot%202026-10-19%20at%2012.14.57.png?alt=media&amp;token=823ae336-474f-43b4-a81f-604ab84d4a88" alt=""><figcaption></figcaption></figure>

#### Step 2. Create the script in Jamf Pro

* In Jamf Pro, go to **Settings → Computer Management → Scripts**.
* Click **New**.
* On the **General** tab, enter a descriptive name, for example `StepSecurity Dev Machine Guard`.
* Open the **Script** tab and select **Shell/Bash** as the language.
* Paste the loader script you copied in Step 1 into the editor. Paste it exactly as generated, without adding variables or settings such as a scan frequency.
* Click **Save**.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2Fanl3i5lfrkt0pRTZKGGL%2F01-jamf-script-editor.png?alt=media&amp;token=f9ea1938-7b66-4a94-9559-3db030b8ddfa" alt=""><figcaption></figcaption></figure>

#### Step 3. Confirm the recurring check-in frequency

Recurring check-in frequency is the interval at which computers check in with Jamf Pro for available policies. It is a Jamf Pro-wide setting, so it applies to every policy that uses the **Recurring Check-in** trigger. The Jamf Pro default is **Every 15 Minutes**, which this guide assumes.

To confirm or change it:

* In Jamf Pro, go to **Settings**.
* Under **Computer Management**, select **Check-in**.
* Click **Edit**.
* Confirm that **Recurring Check-in Frequency** is set to **Every 15 Minutes**.
* Click **Save** if you made a change.

{% hint style="info" %}
Changing the recurring check-in frequency affects every policy in your Jamf Pro instance that uses the Recurring Check-in trigger. Jamf Pro also applies a randomizing factor, so an individual computer can check in up to about 5 minutes before or after the configured interval. See Jamf's guide to [setting recurring check-in for computers](https://support.jamf.com/en/articles/11037893-setting-recurring-check-in-for-computers-in-jamf-pro).&#x20;
{% endhint %}

#### Step 4. Create the deployment policy

* In Jamf Pro, go to **Computers → Policies**.
* Click **New**.
* Under **Options → General**, enter a display name, for example `StepSecurity Dev Machine Guard`.
* Configure the following settings:

| Setting                    | Value              |
| -------------------------- | ------------------ |
| **Enabled**                | Selected           |
| **Trigger**                | Recurring Check-in |
| **Execution Frequency**    | Ongoing            |
| **Target Drive**           | `/`                |
| **Make Available Offline** | Leave unchecked    |

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FAxB0cllnvRpxrGd6x5os%2F02-jamf-policy-options.png?alt=media&amp;token=403b7010-6334-4552-9f33-edbfb7c570ec" alt=""><figcaption></figcaption></figure>

With **Ongoing** selected, the policy runs the loader at every recurring check-in (about every 15 minutes with the default check-in frequency). Continue to Step 5 before you save the policy.

#### Step 5. Add the script to the policy

* In the same policy, go to **Options → Scripts**.
* Click **Configure**, then find the script you created in Step 2.
* Click **Add**.
* Set **Priority** to **After**.
* Leave every **Parameter Values** field empty, from **Parameter 4** onward. Jamf Pro predefines Parameters 1 to 3 (mount point, computer name, and username), and the loader reads its configuration from the script itself.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2F9dNY5n9aRcL6I4OFRpJP%2F03-jamf-script-parameters.png?alt=media&amp;token=abfc3c60-f5a1-4e7f-932c-606b0c8618ee" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Do not enter `install` or any other value in Parameter 4 or any later parameter.
{% endhint %}

#### Step 6. Scope the policy to a pilot group

* Open the policy's **Scope** tab.
* Under **Targets**, add the computer group for your pilot rollout.
* Review any exclusions and adjust them as needed.
* Click **Save**.

#### Step 7. Validate on the pilot group

Each computer in scope runs the loader automatically at its next recurring check-in. **No action is needed on the client devices.**

After 15 to 30 minutes, confirm the following for each pilot computer:

* The policy logs in Jamf Pro show the script ran successfully.
* The device appears in the StepSecurity dashboard under **Developer Machines →** [**Devices**](https://docs.stepsecurity.io/developer-machines/devices.md) with recent telemetry.

When the pilot looks healthy, return to the policy's **Scope** tab, add the computers or computer groups for your full fleet, and click **Save**.

### Adjusting scan frequency

Once the fleet is rolled out, the StepSecurity dashboard controls how often devices run a full scan.

In the dashboard, go to **Developer Machines → Installation → Settings → Scan Schedule** and set **Full scan every (minutes)**. The default is a full scan every 4 hours. A human-readable equivalent appears beside the field, so `240` displays as *4 hours*. Select **Save schedule** to apply.

The setting is organization-wide and applies to every device in your tenant. Agents pick up the change on their next check-in, so you can leave the Jamf Pro script, policy, and check-in frequency as they are. You also do not need to regenerate or redeploy the loader.

To confirm what a specific device is using, open **Developer Machines → Devices**, select the device, and check **Scan Frequency** in the Device Information block.

{% hint style="warning" %} Agents older than **1.15.0** ignore the scan schedule and scan on every launch. With this guide's configuration, that means a full scan at every Jamf Pro check-in. Upgrade to 1.15.0 or later for schedule changes to take effect on a device. {% endhint %}

To scan more aggressively for a limited period, for example during an incident, add a temporary boost on the Scan Schedule panel. See [Settings](https://docs.stepsecurity.io/developer-machines/installation/settings.md) for details.

### Stopping or uninstalling

To stop Dev Machine Guard from running on enrolled computers, either:

* Disable the policy in Jamf Pro, or
* Remove the computers from the policy's scope.

Jamf Pro stops running the loader on those computers. Any locally installed Dev Machine Guard binary and its local configuration remain on the device until cleaned up out-of-band. For the loader-managed uninstall command, see [launchd Troubleshooting](https://docs.stepsecurity.io/developer-machines/installation/script/mdm-deployment/macos/launchd-troubleshooting.md), and see [Devices](https://docs.stepsecurity.io/developer-machines/devices.md) for guidance.

#### Troubleshooting

| Symptom                                                   | Where to look                                                                                                                                                                                 |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The policy does not run                                   | Confirm the policy is enabled, the computer is in scope, **Recurring Check-in** is the trigger, and **Execution Frequency** is **Ongoing**                                                    |
| Jamf Pro reports the policy as failed                     | The policy logs in Jamf Pro for the affected computer                                                                                                                                         |
| The policy succeeds but no device data appears            | Confirm the script saved in Step 2 is the full loader, including the embedded configuration, and that no script parameters are set in Step 5                                                  |
| The agent cannot download or send telemetry               | Confirm the computer can reach every endpoint in [Network requirements](https://docs.stepsecurity.io/developer-machines/installation.md#network-requirements)                                 |
| Devices missing from the StepSecurity dashboard           | Confirm the policy scope covers the expected computers in Jamf Pro                                                                                                                            |
| Devices scanning less often than Jamf Pro check-ins       | Expected when the Scan Schedule interval is longer than the check-in frequency. Check **Scan Frequency** on the device in **Developer Machines → Devices**, then **Settings → Scan Schedule** |
| Devices scanning at every check-in                        | Agents older than 1.15.0 ignore the Scan Schedule. Upgrade the agent                                                                                                                          |
| Files in Documents, Downloads, or Desktop are not scanned | These paths are skipped by default. See [macOS TCC permissions](https://docs.stepsecurity.io/developer-machines/installation/script/mdm-deployment/macos.md#macos-tcc-permissions)            |

For additional support, [contact StepSecurity](https://www.stepsecurity.io/contact).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/developer-machines/installation/script/mdm-deployment/macos/jamf-pro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
