Netskope
Integrate Netskope to retrieve the devices enrolled with the Netskope Client and the users of your tenant
The Netskope connector retrieves the devices enrolled with the Netskope Client and the users of your Netskope tenant into OverView, through the Netskope REST API v2.
Objective
The Netskope connector retrieves the following information:
- Devices enrolled with the Netskope Client (hostname, MAC addresses, operating system, manufacturer, model and serial number, client version and status, device classification)
- Users associated with each device
- Users provisioned in the tenant
Prerequisites
- A Tenant Admin account on the Netskope console: it is the only predefined role allowed to create roles and service accounts.
- Where the tenant restricts API access with an IP allowlist, the OverView source addresses must be added to it. Contact OverSOC support to obtain them.
Information to provide in OverView
| Field | Description |
|---|---|
| Tenant URL* | The URL you use to open the Netskope console, without a trailing slash (e.g., https://example.goskope.com or https://example.eu.goskope.com) |
| API Token* | REST API v2 token of the service account created below |
Procedure
Create a read-only role
The role assigned to the service account defines which API endpoints its token can call.
- Sign in to the Netskope console and go to Settings > Administration > Administrators & Roles.
- On the Roles tab, click New.
- Enter a Role Name (e.g.,
OverView Connector). - Set the permission of the two functional areas below to View, and leave every other one at None:
- Access Control > NS Client > Devices
- End User Provisioning > Users & Groups
- Click Save.
Create a service account and its token
- On the Administrators tab, click Service Account.
- Enter a Service Account Name (e.g.,
overview-connector) and select the role created above. - In the REST API Token section, set the expiration of the token. The connector stops working when it expires, so renew it before that date.
- Click Create.
- Copy the token immediately: it is displayed only once.
On a tenant not yet migrated to RBAC V3, the Settings > Tools > REST API v2 page still offers New Token. Enter a name and an expiration, then click Add Endpoint and add the endpoints listed in Required Permissions with the Read privilege.
Configure the Connector in OverView
- In OverView, go to Data Sources Settings > Sources.
- Select Netskope and click Configure.
- Fill in the Tenant URL and API Token, then click Save Configuration.
Required Permissions
The View level grants the read operations of the endpoints below, which is all the connector uses: it never creates, modifies or deletes anything in Netskope. The information icon next to each permission in the role editor lists the endpoints it covers.
| Data retrieved | Endpoint | Permission |
|---|---|---|
| Devices | GET /api/v2/events/datasearch/clientstatus | Access Control > NS Client > Devices |
| Users | GET /api/v2/scim/Users | End User Provisioning > Users & Groups |