Safeguard Docs
Compliance ConnectorsSetup by categoryMDM

Prey

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

Connect Prey to collect mdm evidence with automated compliance tests, switched on per workspace.

CategoryMDM
Connect withAPI token
What a connection producesAutomated compliance tests
Prey's guideapi.preyproject.com

Connect with an API token

  1. In Prey:

    1. In the Prey Control Panel, go to the Settings tab and click the Developer API button.
    2. Generate your API key, optionally choosing an expiration date so access can lapse.
    3. Copy the key.

    The help-center page returns HTTP 403 to automated fetches; the same article was read through the help center's article API. The Developer API is available for Prey Tracking, Prey Protection and Prey Full Suite. Prey has no narrower grant than the account key. One-time display was not confirmed.

    Source: support.preyproject.com, support.preyproject.com, checked 2026-10-07.

    The permissions Safeguard needs. Prey has no narrower grant for these reads. Safeguard only reads with it.

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

    FieldWhat to enter
    API keyRequired. Stored encrypted and never shown again.
  3. Click Connect with token.

Frameworks

Safeguard's automated tests read Prey 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 testsCC7.12
ISO/IEC 27001Automated testsA.8.1, A.8.8, A.8.92
HIPAA Security RuleAutomated tests164.308(a)(5), 164.310(d)(1)2
PCI DSSAutomated tests6.3.3, 12.5.12
NIST CSF 2.0Automated testsID.AM-01, PR.PS-022

These tests are switched on per workspace by the Safeguard team.

On this page