Ivanti Neurons

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

Connect with an API token

1. In Ivanti Neurons:

   1. Ivanti Neurons for MDM (API, no UI): sign in to the API as a Tenant Admin, or as a user with the system management or user management role, using Basic authentication.
   2. Ivanti Neurons for MDM: POST to https://<host>/api/v1/oidc/client with a JSON body containing your accountGuid. The response returns clientId and clientSecret.
   3. Ivanti Neurons for MDM: exchange them for an access token by POSTing grant_type=client_credentials to https://<host>/oauth2/token with an Authorization: Basic header of the Base64-encoded client_id:client_secret. The response returns a Bearer access_token (expires_in 3599 seconds).
   4. Ivanti Neurons for ITSM (UI): from the Configuration console, click Configure › Security Controls › API Keys.
   5. Ivanti Neurons for ITSM: on first use, click Add Key Group, enter a Name and Description on the New API Group page, click Save Key Group, then click Back.
   6. Ivanti Neurons for ITSM: select the REST API group in the Key Groups section and click Add API Key.
   7. Ivanti Neurons for ITSM: on the New API Key page, keep Activated checked, enter a Description, choose the user in On Behalf Of and a role in In Role, optionally click Add New IP to allow more IP addresses, and click Save Key.
   8. Ivanti Neurons for ITSM: copy the auto-generated Reference ID; this is the REST API key, sent as the header value rest_api_key={Reference ID}.

   Where to find the other values:

   • Base URL (optional): Your tenant's host: the Neurons for MDM API guide uses https://<host>/; a Neurons for ITSM key works only for the tenant (and IPs) it was created on.
   • Account / Org / Workspace (optional): For Neurons for MDM, the accountGuid of the account; the API guide does not say where the admin UI shows it.

   'Ivanti Neurons' covers several products with different credentials; confirm which one the customer uses. For MDM evidence this is usually Neurons for MDM, whose Integration API uses Basic authentication with a Tenant Admin user. If MFA is configured (User > User Settings > Admin Portal Auth Settings set to Password and PIN), Basic authentication stops working and the token-based OIDC client-credentials flow above is required. The OIDC client is created only through the API (POST api/v1/oidc/client), not in a UI. API calls by a user tied to a GDPR profile return obfuscated personal fields, and results are paged at up to 500 rows. For Neurons for ITSM, REST API keys are static and do not expire; a key works only for the tenant it was created on, and it can be edited later, so the Reference ID stays visible. The ITSM page read is the 2023 admin help, the newest version listed in Ivanti's help sitemap.

   Source: help.ivanti.com, help.ivanti.com, help.ivanti.com, help.ivanti.com, checked 2026-10-07.

2. On Compliance › Connectors, open Ivanti Neurons, 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)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Ivanti Neurons 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