SOTI MobiControl
Connect SOTI MobiControl to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your SOTI MobiControl connection as mdm evidence. Automated collection is not available for this provider yet.
| Category | MDM |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In SOTI MobiControl:
- Sign in to the SOTI MobiControl console as a user with the Manage API Clients permission.
- Go to Global Settings › Services › API Client.
- Select the Add API Client button.
- In the Add API Client panel, enter a name for the new API client and select Generate.
- Copy and store the client ID and client secret shown on the generated client details screen; after this dialog closes you cannot retrieve the client secret.
- Select OK. The new API client now appears on the API Client screen.
Where to find the other values:
- API token / Personal access token: The client ID and client secret on the generated client details screen of Global Settings › Services › API Client › Add API Client.
- Base URL (optional): The address of your own SOTI MobiControl server (MobiControl is self-hosted or SOTI-hosted per customer); not stated on the fetched page.
SOTI MobiControl shows the secret only once, so copy it before you leave the page.
Steps are from the SOTI MobiControl v2024.0 help. The client ID and secret are generated automatically and cannot be modified, and the grant type is fixed to 'Password', so API access tokens are obtained with the client ID/secret plus a MobiControl console user's credentials; SOTI documents no read-only API client, so access follows that console user's permissions. Older MobiControl versions (before v2024.0) register API clients from the server command line with MCAdmin.exe APIClientAdd instead of the console (per search results; not fetched this run). The token endpoint and API base URL path were not confirmed from a fetched SOTI page.
-
On Compliance › Connectors, open SOTI MobiControl, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
SOTI MobiControl publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.8, CC7.1 | 1 |
| ISO/IEC 27001 | Attestation | A.8.1 | 1 |
| HIPAA Security Rule | Attestation | 164.310(d)(1) | 1 |
| PCI DSS | Attestation | 12.5.1 | 1 |
| NIST CSF 2.0 | Attestation | ID.AM-01, PR.PS-02 | 1 |
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