Automox

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

Connect with an API token

1. In Automox:

   1. Sign in to the Automox console as the user the key should act as. A key inherits that user's role, so use an account with a read-only role for Safeguard.
   2. Go to Settings › Secrets & Keys.
   3. Select Add, enter a unique name for the key, optionally select an expiration date, and select Create.
   4. Copy the key with the clipboard button (or click Show to decrypt it; it hides again after 10 seconds).

   Where to find the other values:

   • Organization ID: Not shown on the fetched page; it documents only the Account ID (the UUID for the account) on the Secrets Management page.

   Automox's public documentation does not cover every step.

   Each user can have up to 10 organization API keys. Only the key's owner can decrypt it. Creating a read-only Automox user and the location of the Organization ID were not sourced from a fetched page.

   Source: docs.automox.com, checked 2026-10-07.

   The permissions Safeguard needs: read-only administrator.

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

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.
   Organization ID	Required.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Automox 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.

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

Related

• MDM connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks