Netskope

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

Installation guide

Installation

info

You will need to generate an API V1 Token on Netskope for this integration. See their documentation for more information. You can also request the Token from your Netskope tenant admin.

Configuration in JupiterOne

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

Creating a configuration requires the following:

• The Account Name used to identify the Netskope account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

• Description to assist in identifying the integration instance, if desired.

• Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

• Lastly, your Netskope API V1 Token.

Click Create once all values are provided to finalize the integration.

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.

Netskope data model

Data Model

Entities

The following entities are created:

Resources	Entity _type	Entity _class
App Instance	netskope_app_instance	Application
Device	netskope_device	Device
Tenant	netskope_tenant	Organization
User	netskope_user	User
User Configuration	netskope_user_configuration	Configuration

Relationships

The following relationships are created:

Source Entity _type	Relationship _class	Target Entity _type
netskope_device	HAS	netskope_user
netskope_tenant	HAS	netskope_app_instance
netskope_tenant	HAS	netskope_device
netskope_user	HAS	netskope_user_configuration