Skip to main content

Netskope

Visualize Netskope devices, users, and app instances, map Netskope users to employee entities, and monitor changes through queries and alerts.

Prerequisites​

The Netskope integration authenticates with two separate tokens:

  • API V1 Token (required) — grants access to devices, users, and app instances.
  • API V2 Token (optional) — unlocks additional data types including NPA private apps, publishers, NPA policies, URL lists, discovered/shadow-AI apps, DLP incidents, and SCIM users.

Generate an API V1 Token​

  1. Log in to the Netskope admin console.
  2. Navigate to Settings > Tools > REST API v1.
  3. Click New Token, give it a name, and click Generate.
  4. Copy the token value — you will not be able to view it again.

Generate an API V2 Token (optional)​

The V2 token uses RBAC V3 service-account credentials. Grant it read access to the API domains you want to ingest.

  1. Navigate to Settings > Administration > Administrators.
  2. Select the Service Accounts tab.
  3. Click New Service Account, enter a name, and select Read access for each API domain you want to enable (for example: Steering, Infrastructure, Policy, Events, SCIM).
  4. Click Save, then copy the generated token.

For more information see the Netskope REST API v1 overview and REST API v2 token management.

Configuration in JupiterOne​

To install the Netskope integration in JupiterOne, navigate to the Integrations tab and select Netskope. Click New Instance to begin configuring your integration.

  1. Enter an Account Name to identify this Netskope integration instance in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the toggle is enabled.
  2. (Optional) Enter a Description to help identify the instance.
  3. Set a Polling Interval for automatic data refresh, or leave it as DISABLED to run manually.
  4. Enter your Tenant Name — the subdomain portion of your Netskope tenant URL (example from example.goskope.com).
  5. Enter your API V1 Token.
  6. (Optional) Enter your API V2 Token to enable additional data ingestion (NPA private apps, publishers, NPA policies, URL lists, discovered apps, and DLP incidents).

Click Create to save the instance.

Data Volume Configuration​

Control how much data is ingested from Netskope to manage storage and processing.

Ingestion Windows​

FieldDescriptionDefaultOptions
Event Lookback (days)Rolling lookback window for event-derived steps (DLP incidents and discovered/shadow-AI apps). Longer windows increase the number of events ingested.7 days7 days, 30 days, 90 days

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.