Skip to main content

Netskope Data Source

The Netskope connector enables you to access Netskope API endpoints to retrieve security alerts, threat intelligence, and security insights. This connector is particularly useful for applications that need to extract security alerts, analyze threat data, integrate security information with SIEM systems, or build security analytics and reporting solutions. Follow the instructions below to create a new data flow that ingests data from a Netskope source in Nexla.
netskope_api.png

Netskope

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Netskope connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Netskope API, and click Next; or, create a new Netskope credential for use in this flow.

  3. In Nexla, Netskope data sources can be created using pre-built endpoint templates, which expedite source setup for common Netskope API endpoints. Each template is designed specifically for the corresponding Netskope API endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Netskope sources can also be configured manually, allowing you to ingest data from Netskope API endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Netskope API endpoints. Each template is designed specifically for the corresponding Netskope API endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Netskope Alert : Anomaly

    This endpoint retrieves anomaly alerts from your Netskope security platform. Use this endpoint when you need to extract anomaly detection alerts, analyze unusual user behavior, or integrate anomaly alerts with SIEM systems.

    • Optionally, enter the start time for alert retrieval in epoch timestamp format in the Epoch Previous field. This specifies the beginning of the time range for alert retrieval.
    • Optionally, enter the end time for alert retrieval in epoch timestamp format in the Epoch field. This specifies the end of the time range for alert retrieval.
    • Optionally, enter the maximum number of alerts to return per page in the Limit field. The default value is typically 1000. You can adjust this value based on your needs and API rate limits.

    This endpoint uses GET requests with pagination through offset-based pagination. The endpoint automatically fetches additional pages using incrementing offset values, ensuring all anomaly alerts within the specified time range are retrieved. For more information about the Netskope Alert : Anomaly endpoint, refer to the Netskope API Documentation.

    Netskope Alerts | Filtered Salesforce

    This endpoint retrieves Salesforce alerts filtered for DLP (Data Loss Prevention) events from your Netskope security platform. Use this endpoint when you need to extract Salesforce-specific security alerts, monitor data loss prevention events, or analyze Salesforce application usage.

    • Optionally, enter the start time for alert retrieval in epoch timestamp format in the Epoch Previous field. This specifies the beginning of the time range for alert retrieval.
    • Optionally, enter the end time for alert retrieval in epoch timestamp format in the Epoch field. This specifies the end of the time range for alert retrieval.
    • Optionally, enter the maximum number of alerts to return per page in the Limit field. The default value is typically 1000. You can adjust this value based on your needs and API rate limits.

    This endpoint retrieves DLP alerts specifically for Salesforce applications. The endpoint uses GET requests with pagination through offset-based pagination. For more information about the Netskope Alerts | Filtered Salesforce endpoint, refer to the Netskope API Documentation.

    Netskope Alert : Legal Hold

    This endpoint retrieves legal hold alerts from your Netskope security platform. Use this endpoint when you need to extract legal hold alerts, monitor compliance events, or integrate legal hold data with compliance systems.

    • Optionally, enter the start time for alert retrieval in epoch timestamp format in the Epoch Previous field. This specifies the beginning of the time range for alert retrieval.
    • Optionally, enter the end time for alert retrieval in epoch timestamp format in the Epoch field. This specifies the end of the time range for alert retrieval.
    • Optionally, enter the maximum number of alerts to return per page in the Limit field. The default value is typically 1000. You can adjust this value based on your needs and API rate limits.

    This endpoint uses GET requests with pagination through offset-based pagination. The endpoint automatically fetches additional pages using incrementing offset values, ensuring all legal hold alerts within the specified time range are retrieved. For more information about the Netskope Alert : Legal Hold endpoint, refer to the Netskope API Documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Netskope data sources can be manually configured to ingest data from any valid Netskope API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Netskope sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Netskope API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API (most Netskope endpoints use GET)

API Endpoint URL​

  1. Enter the URL of the Netskope API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Netskope API endpoints typically follow the pattern https://{tenant}.goskope.com/api/v1/{resource}, where {tenant} is your tenant ID.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint URL should use your tenant ID configured in the credential.

Path to Data​

Optional

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch alerts, the API will typically return alert data along with metadata. By entering the path to the relevant data, you can configure Nexla to extract the specific alerts you need.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records. For Netskope API responses, common paths include $ for the entire response or $.data[*] for arrays of alerts.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.data to access the data array).
    Path to Data Example:

    If the API response is in JSON format and includes alert data, the path to the response would be entered as $ for the entire response or $.data[*] if alerts are nested in a data array.

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. For Netskope, the Authorization header with API key is automatically included from your credential, and you may want to include Accept:application/json,Content-Type:application/json to specify the response format.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Netskope data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.