ManageEngine
Connect ManageEngine to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect ManageEngine 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 |
| ManageEngine's guide | manageengine.com |
Connect with an API token
-
In ManageEngine:
- Go to your Self Client in the API console.
- Open the self client's Generate Code tab and enter the scopes, separated by commas: DesktopCentralCloud.Common.READ,DesktopCentralCloud.DataEncryption.READ.
- Select an expiry time for the authorization code (3 minutes by default), enter a description for the scopes, and click CREATE. If prompted, select the Zoho app and the portal it needs to access, and click CREATE again. Copy the authorization code.
- From the self client's Client Secret tab copy the client ID and client secret, then POST them with grant_type=authorization_code and the code to {accounts-server-url}/oauth/v2/token. The response's access_token is the value for Safeguard's Access token field (valid 1 hour; the refresh_token does not expire).
Where to find the other values:
- Data center: The data center where your Endpoint Central Cloud account (and the self client) is registered; the accounts server URL depends on it.
ManageEngine's public documentation does not cover every step.
Source: manageengine.com, manageengine.com, checked 2026-10-07.
The permissions Safeguard needs:
DesktopCentralCloud.Common.READ,DesktopCentralCloud.DataEncryption.READ. -
On Compliance › Connectors, open ManageEngine, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Data center Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read ManageEngine 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.8, CC7.1 | 6 |
| 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.24 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(5), 164.310(d)(1), 164.312(a)(1) | 6 |
| PCI DSS | Automated tests | 3.5.1, 6.3.3, 12.5.1 | 5 |
| NIST CSF 2.0 | Automated tests | ID.AM-01, PR.AA-05, PR.DS-01, PR.PS-02 | 6 |
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