Compliance ConnectorsSetup by categoryUser Access Review
ConductorOne
Connect ConductorOne to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your ConductorOne connection as user access review evidence.
| Category | User Access Review |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In ConductorOne:
- In the C1 (ConductorOne) web app, open your profile menu and select API keys.
- Click Create credential.
- Give the API key a name and select whether the key will expire.
- Optionally enter allowed IP addresses in the Limit source IPs field.
- Under Limit Scopes, select Read-Only Administrator.
- Click Create. The client ID and client secret are shown; copy the client secret now, as it won't be shown again.
Where to find the other values:
- Base URL (optional): Use your tenant's C1 web app address; C1 states that API hosts and authentication are tenant-specific.
ConductorOne shows the secret only once, so copy it before you leave the page.
-
On Compliance › Connectors, open ConductorOne, 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
No automated compliance test reads ConductorOne, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- User Access Review 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