Fleet
Connect Fleet to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Fleet to collect mdm evidence with automated compliance tests, switched on per workspace.
| Category | MDM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Fleet's guide | fleetdm.com |
Connect with an API token
-
In Fleet:
- Sign in to Fleet as an admin and go to Settings › Users › Create user.
- Select the API-only option and give the user the Observer role (read-only).
- Or, from the command line as an admin: fleetctl user create --name 'API User' --api-only (the global role defaults to Observer; on Fleet Premium you can limit it to one fleet with --fleet <fleet_id>:<role>).
- Copy the token Fleet prints: "The API token for your new user is: <TOKEN>". To get it again later, use the log in API endpoint.
Where to find the other values:
- Server URL: The https address of your Fleet server (the one you sign in to).
Fleet shows the secret only once, so copy it before you leave the page.
API-only users have no UI access, and their API key does not expire. You can optionally restrict the user to specific API endpoints without widening its role. The CLI shows the token once ('will not be shown again'); it can be retrieved later only through the log in API.
Source: fleetdm.com, checked 2026-10-07.
The permissions Safeguard needs:
API-only user,Observer. -
On Compliance › Connectors, open Fleet, click Connect, choose API token and fill in:
Field What to enter Server URL Required. Your own server: an https address reachable from the internet. API token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Fleet 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.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | C1.1, CC6.1, CC6.2, CC6.5, CC6.6, CC6.8, CC7.1 | 8 |
| ISO/IEC 27001 | Automated tests | A.5.9, A.5.11, A.6.5, A.8.1, A.8.8, A.8.9, A.8.20, A.8.24 | 8 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(5), 164.310(d)(1), 164.312(a)(1), 164.312(e)(1) | 8 |
| PCI DSS | Automated tests | 1.5.1, 3.5.1, 6.3.3, 8.2.8, 12.5.1 | 7 |
| NIST CSF 2.0 | Automated tests | ID.AM-01, PR.AA-03, PR.AA-05, PR.DS-01, PR.IR-01, PR.PS-02 | 8 |
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