Skip to main content

Netskope V2

netskope

Version: 1.2
Updated: Nov 5, 2024

Netskope provides unrivaled visibility and real-time data and threat protection when accessing cloud services, websites, and private apps from anywhere, on any device.

Actions​

  • Get Alert (Enrichment) - Get single alert.
  • List Alerts (Enrichment) - Get a list of alerts generated by Netskope.
  • List Events (Enrichment) - Get a list of events generated by Netskope.
  • Get URL Lists (Enrichment) - Get URL lists.
  • Update URL List (Containment) - Edit an URL list.
  • URL List Deploy (Containment) - Apply pending URL list changes.
  • Netskope Get Alert List Daemon (Daemon) - Daemon to extract alerts generated by Netskope.
  • Netskope Get Event List Daemon (Daemon) - Daemon to events alerts generated by Netskope.

Neskope V2 configuration​

Netskope REST APIs use an auth token to make authorized calls to the API. Netskope REST APIs provide access to resources via URI paths. The token must be used in every REST API call for the tenant. The token can be created for use with specified APIs in the Netskope UI by going to Settings > Tools > Rest API v2.

  1. On the REST API v2 page, click New Token.
  2. Enter a token name, the token expiration time, and then click Add Endpoint to select the API endpoints to use with the token.
  3. Specify the privileges for each of the endpoints added. Read privileges include GET, and Read+Write privileges include GET, PUT, POST, PATCH, and DELETE. Endpoint privileges vary. Some endpoints, like alert and audit (and others) only have the Read privilege; whereas, the URL list/file endpoint only has Read+Write privileges. For this Integration following endpoints are required:
    netskope-v2
  4. When finished, click Save.
  5. A confirmation box opens showing whether the token creation was a success. If so, click Copy Token to save it for later use in your API requests.

Important - The only opportunity to copy the token is immediately after you create it. The token is required in your API requests.
netskope-v2

When finished, click OK. After being created, tokens can be managed by clicking the adjacent ... icon for the token and selecting one of these options:
netskope-v2

Configure Netskope V2 in Automation Service and Cloud SOAR​

Before you can use the integration, you must configure it so that the vendor can communicate with Sumo Logic. For general guidance, see Configure Authentication for Integrations.

  1. Access App Central and install the integration.
  2. Select the installed integration in the Integrations page.
    Classic UI. In the main Sumo Logic menu, select Automation and then select Integrations in the left nav bar.
    New UI. In the main Sumo Logic menu, select Automation > Integrations. You can also click the Go To... menu at the top of the screen and select Integrations.
  3. Select the integration.
  4. Hover over the resource name and click the Edit button that appears.
    Edit a resource
  5. In the Add Resource dialog, enter the authentication needed by the resource. When done, click TEST to test the configuration, and click SAVE to save the configuration.
  • Server URL. URL for API V2 REST API (https://<tenant-name>.goskope.com).
  • Token. The Token you copied earlier.
  • Additionally, if need you can populate the query daemons.
    netskope-v2

For information about Netskope V2, see Netskope V2 documentation.

Change Log​

  • December 21, 2022 - First upload
  • July 13, 2023 (v1.1)
    • Changed fields visibility
    • Changed Daemon compatibility
  • November 5, 2024 (v1.2) - Added New action
    • URL List Deploy
Status
Legal
Privacy Statement
Terms of Use

Copyright © 2025 by Sumo Logic, Inc.