Skip to main content

OneTrust

Visualize OneTrust users, groups, risk, and vendors, and monitor changes through queries and alerts.

Installation​

Requirements​

  • User must have an active OneTrust account with API access.
  • User must have permission in JupiterOne to install new integrations.

Configuration in OneTrust​

Generate OAuth 2.0 Client Credentials and collect Host URL​

  1. Log in to your OneTrust account.
  2. Click the gear icon in the upper-right corner to access Global Settings.
  3. From the Global Settings menu, select Access Management > Client Credentials. The Credentials screen appears.
  4. Click the Add button. The Add Client Credential screen will open.
  5. In the Name field, enter a name for the client credential.
  6. (Optional) In the Description field, provide a description for the client credential.
  7. In the Access Token Lifetime field, set the duration of the access token to 1 hour.
  8. (Optional) Enable the Restrict IP Addresses setting to restrict incoming communication to specific IP addresses. If enabled, enter the allowed IP addresses. You can add multiple IPs by clicking the Add icon.
  9. Click Next. The Scope section appears.
  10. Select following Scopes
    • RISK_READ: To fetch Risk Data
    • SCIM: To fetch User and Group Data
    • INVENTORY_READ: To fetch Vendor Data
  11. Click Create. The Client ID and Client Secret section will appear.
  12. Click Download to save the .txt file containing your Client ID and Client Secret to a secure location.
  13. Click Close to finish.
  14. Note down your OneTrust Host URL from URL bar (e.g., https://customer.my.onetrust.com).

Configuration in JupiterOne​

  1. From the top navigation of the J1 Search homepage, select Integrations.
  2. Search for OneTrust and select it.
  3. Click on the Add Instance button and configure the following settings:
  • Enter the OneTrust Host URL.
  • Enter the OneTrust Client ID.
  • Enter the OneTrust Client Secret.
  • Enter the Account Name by which you'd like to identify this OneTrust instance in JupiterOne. Ingested entities will have this value stored in tag.AccountName when Tag with Account Name is checked.
  • Enter a Description to help your team identify the integration instance.
  • Select a Polling Interval that fits your monitoring needs. You may leave this as DISABLED and manually execute the integration.
  1. Click Create Instance once all values are provided.

Next steps​

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.