Mosyle
Connect Mosyle to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Mosyle 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 |
| Mosyle's guide | business.mosyle.com |
Connect with an API token
-
In Mosyle, create the credential for Access token and Password with
Devices: View,Users: View,API Integration: View, Create. Mosyle's guide: business.mosyle.com. Mosyle's API signs in with an admin's email and password as well as the access token. Create a dedicated admin for Safeguard whose role can only view devices and users, with its own Mosyle password (an admin who signs in only through SSO cannot use the API). Signed in as that admin, create the token under Organization › Integrations › Mosyle API Integration, with Public access or Safeguard's address allowed. Enter all three here yourself: Safeguard stores them encrypted and sends the password only to Mosyle's sign-in. Mosyle's API reference is not public, so Safeguard reads only the fields public integrations confirm. FileVault, the firewall and a Mac's screen lock show a "couldn't read" error, never a pass or a fail, until the first live connection confirms where Mosyle reports them; attest them meanwhile. Until Mosyle's tests are switched on for your workspace, device posture stays an attestation. Safeguard's compliance tests for Mosyle need the credential on the API token tab: an OAuth connection cannot read everything they check. -
On Compliance › Connectors, open Mosyle, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Email Required. Password Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Mosyle 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 | 9 |
| 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 | 9 |
| 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) | 9 |
| PCI DSS | Automated tests | 1.5.1, 3.5.1, 6.3.3, 8.2.8, 12.5.1 | 8 |
| NIST CSF 2.0 | Automated tests | ID.AM-01, PR.AA-03, PR.AA-05, PR.DS-01, PR.IR-01, PR.PS-02 | 9 |
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