Netskope is currently in beta
*.goskope.com), not Device Intelligence.
Prerequisites
- A Netskope tenant hostname (for example
company.goskope.comorcompany.eu.goskope.com) - A REST API v2 token from a Service Account whose role has View on:
- Skope IT → Alerts
- Skope IT → Application Events
- Skope IT → Network Events
- Skope IT → Page Events (HTTP connection / page events)
- Administration → Users & Groups
- Settings → Security Cloud Platform → Devices (Netskope Client device status; optional)
- If the tenant uses an IP allowlist (Settings → Administration → IP Allowlist), add Wirespeed egress IPs to the custom list
Create a REST API v2 token
- Log in to the Netskope tenant
- Open Settings → Administration → Administrators & Roles → Roles and create a role with View on the functional areas listed above. Set every other permission to None
- Open the Administrators tab, click Service Account, assign that role, and generate a REST API token
- Copy the token when it is shown. It is not displayed again
/api/v2/events/dataexport/events/alert/api/v2/events/dataexport/events/application/api/v2/events/dataexport/events/page/api/v2/events/dataexport/events/network/api/v2/scim/Users/api/v2/events/datasearch/clientstatus(optional, for device sync)
Add the integration in Wirespeed
- In Wirespeed, navigate to Integrations > Add Integration > Netskope
- Enter the Tenant Hostname (for example
company.eu.goskope.com). A full tenant URL also works - Paste the REST API v2 token
- Submit the integration
What Wirespeed ingests
For event logs, the first sync backfills about 24 hours, then continues from where the previous pull left off. Device sync reads the last 30 days of client status on every run.
Device sync is optional. If the token cannot read
/api/v2/events/datasearch/clientstatus, every other source keeps working and the integration shows a Device Status warning. Wirespeed re-checks access every few hours, so devices start syncing after you grant the permission without reconnecting.
