Safeguard Docs
Compliance ConnectorsSetup by categoryMDM

Jamf

Connect Jamf to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Jamf to collect mdm evidence with automated compliance tests.

CategoryMDM
Connect withAPI token
What a connection producesAutomated compliance tests
Jamf's guidedeveloper.jamf.com

Connect with an API token

  1. In Jamf:

    1. In Jamf Pro, create an API role with the privileges Safeguard needs.
    2. Create an API client, assign it that API role, and generate a client secret. Jamf Pro API client authentication uses the client ID and client secret of that API client.

    Where to find the other values:

    Jamf's public documentation does not cover every step.

    Source: learn.jamf.com, learn.jamf.com, developer.jamf.com, checked 2026-10-07.

    The permissions Safeguard needs: Read Computers, Read Mobile Devices, Read macOS Configuration Profiles.

  2. On Compliance › Connectors, open Jamf, click Connect, choose API token and fill in:

    FieldWhat to enter
    SubdomainRequired. The part before .jamfcloud.com in your address.
    Client IDOptional.
    Client secretOptional. Stored encrypted and never shown again.

    Or, instead: API token (optional).

  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Jamf and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

FrameworkEvidenceControlsTests
SOC2Automated testsC1.1, CC6.1, CC6.2, CC6.5, CC6.6, CC6.7, CC6.8, CC7.19
ISO/IEC 27001Automated testsA.5.9, A.5.11, A.6.5, A.8.1, A.8.7, A.8.8, A.8.9, A.8.20, A.8.249
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(5), 164.310(d)(1), 164.312(a)(1), 164.312(e)(1)9
PCI DSSAutomated tests1.5.1, 3.5.1, 6.3.3, 8.2.8, 12.5.17
NIST CSF 2.0Automated testsID.AM-01, PR.AA-03, PR.AA-05, PR.DS-01, PR.IR-01, PR.PS-01, PR.PS-029

On this page