icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading Netskope App For Splunk
SHA256 checksum (netskope-app-for-splunk_113.tgz) 1d14f76387e1e29126b510817b4d4945f420a956603e9b8fc3e73b645da63823 SHA256 checksum (netskope-app-for-splunk_112.tgz) 82d257f3dec87ac705e7b697dcc0821e2210bc09bf4c212b30bf44d5e0e4e495 SHA256 checksum (netskope-app-for-splunk_111.tgz) 9d9e662723f21b87e1fc66dc4d8db8a7648102f0756962cc2203426b37547366 SHA256 checksum (netskope-app-for-splunk_110.tgz) 3f7f6b1c6212c3660f87c7ea3cc81f45ba4297ac3cd41232c5d1050e811d5466 SHA256 checksum (netskope-app-for-splunk_105.tgz) ed2667be7c0e9a514a59096779f35eb77cf8089052618da68aa9c1f27a3a81c2
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

Netskope App For Splunk

Splunk AppInspect Passed
Overview
Details
Netskope is the leader in cloud security. We help organizations understand online activities, protect data, stop threats, and respond to incidents. Netskope — security evolved.

Netskope App For Splunk allows a Splunk Enterprise administrator to integrate with the Netskope API and pull security events.

Welcome to Netskope App for Splunks documentation!

Overview

About Netskope App For Splunk

Author Netskope, Inc.
App Version 1.1.3
App Build 230
Vendor Products Netskope API 48
Has index-time operations true
Creates an index false
Implements summarization Currently, the app does not generate summaries

About Netskope App For Splunk

The Netskope App for Splunk integrates with the Netskope service to provide value and insight into your data.

Scripts and binaries

This App provides the following scripts:

bin/netskope.py The Modular Input used to communicate and consume the API data.
netskope_client.py This chunk of Python contains the Modular Input Classes for Netskope.
netskope_url.py Alert Action script for URL lists.
netskope_file_hash.py Alert Action script for file hash lists.
Diag.py Allows diag-targeted collection of information.
ModularInput.py Inheritable Class to create Modular Inputs
RESTClient.py Inheritable Class to create REST clients
Utilities.py Allows utility interactions with Splunk Endpoints

Scripts

Release notes

Version 1.1.3

  • Test and QA

    • [NET-102] - Remove duplicates from default.meta
  • New Feature

    • [NET-93] - Web Dashboard
  • Improvement

    • [NET-98] - Health Application Page
    • [NET-99] - Add alert action to log.cfg
    • [NET-100] - Fix Health Checks
    • [NET-101] - Health Checks for common issues

Version 1.1.2

  • Improvement

    • [NET-89] - Update Tenant URL validator to avoid special characters
    • [NET-91] - Separate calls for applications and page events
    • [NET-92] - Configurable Offset Parameter

Version 1.1.1

  • Bug

    • [NET-87] - Configured inputs dropdown incorrect

Version 1.1.0

  • Bug

    • [NET-84] - TA fails AR in ES IR
  • New Feature

    • [NET-74] - AR - File hash Add/Remove
    • [NET-75] - AR - URL Add/Remove
    • [NET-76] - AR - Usage and Errors Dashboard
    • [NET-77] - AR - Enable ARF
    • [NET-80] - AR - Allow dynamic Field Names
    • [NET-81] - Documentation Update
  • Improvement

    • [NET-78] - AR - Add Proxy support
    • [NET-85] - Alert Actions - Convert CSV lookup to KVstore to better support SHC.
    • [NET-86] - Disable Automatic Tracking of Internal IDs

About this release

Version 1.1.3 of Netskope App For Splunk is compatible with:

Splunk Enterprise versions 7.0, 7.1, 7.2
Platforms Splunk Enterprise
Vendor Platform Netskope API 48

Compatability

Known Issues

Version 1.1.3 of Netskope App For Splunk has the following known issues:

  • None

Version 1.1.0 of Netskope App For Splunk has the following known issues:

  • The macro netskope_configured_inputs is not configured to use a generating command, therefore the dashboards are failing to create the filtering search.

Version 1.0.3 (83) of Netskope App For Splunk has the following known issues:

    • Application Detail and Alert Detail dashboards will not work in Splunk 6.4 due to token incompatibilities.

      • Resolution: Change the count \<option> in the XML and restart Splunk.

Support and resources

Questions and answers

Access questions and answers specific to Netskope App For Splunk at https://answers.splunk.com . Be sure to tag your question with the App.

Support

Support is available via email at support@netskope.com. Responses vary on working days between working hours.

Installation and Configuration

Software requirements

Splunk Enterprise system requirements

Because this App runs on Splunk Enterprise, all of the Splunk Enterprise system requirements apply.

Download

Download Netskope App For Splunk at https://splunkbase.splunk.com/app/3414/.

Installation steps

NOTE: Where referenced, TA-NetSkopeAppForSplunk and IA-NetSkopeAppForSplunk are located on Splunkbase.

Deploy to single server instance

Follow these steps to install the app in a single server instance of Splunk Enterprise:

  1. Download the Netskope App For Splunk package from https://splunkbase.splunk.com/app/3414/
  2. Install the App via the recommended installation methods (CLI, Web GUI)
  3. Restart Splunk.
  4. Navigate to App_Config to setup modular input settings.

Deploy to Splunk Cloud

  1. Have your Splunk Cloud Support handle this installation.

Deploy to distributed deployment

Install to search head

  1. Download the Netskope App For Splunk package from https://splunkbase.splunk.com/app/3414/
  2. Install the App via the recommended installation methods (CLI, Web GUI, Deployment Server)

Install to indexers

  1. Download the TA-NetSkopeAppForSplunk package from https://splunkbase.splunk.com.
  2. Install TA-NetSkopeAppForSplunk onto the indexers per your environment.

Install to universal forwarders

  1. There is no installation to Universal Forwarders.

Install to Heavy Forwarders

  1. Download the IA-NetSkopeAppForSplunk package from https://splunkbase.splunk.com.
  2. Install IA-NetSkopeAppForSplunk onto a heavy forwarder in your environment.
  3. Configure the Modular Input with the required settings.

Deploy to distributed deployment with Search Head Clustering

  1. Place the App into the deploy_apps folder on the Deployer Server.
  2. Deploy the App to the Search Head Cluster. DO NOT install IA-NetSkopeAppForSplunk to the Cluster!

User Guide

Configure Netskope App For Splunk

  • Install the App according to your environment (see steps above)
  • Navigate to App > IA-NetSkopeAppForSplunk > Administration > Application Configuration

Application Configuration Dashboard

To configure the Netskope application you should start on the Application Configuration page (Administration > Application Configuration)*[]:

Application Configuration

On this screen you can set the base index as well as a flag that specifies that the application is configured. In the future there will be additional configurations available.

Proxy Configuration

If you have configured a proxy server you can view the configuration under this tab. These are proxy server configurations that are being used by existing modular inputs for the Netskope application. You can also delete existing proxy configurations on this tab.

Encrypted Credentials

You can view/delete existing credentials on this tab. These are credentials that are being used by existing modular inputs in the Netskope application. These credentials are the credentials used to connect to Netskope appliances.

Netskope

On this screen you can view and make any changes to existing modular inputs. As you make changes and tab between fields the modular input is modified.

Creating New Proxy Configurations

If you need to use a proxy as part of the connection to Netskope, configure it here.

  • To create a new proxy server configuration, click the Create New Proxy button and fill in the following fields:

    • Proxy Name: Name for the proxy configuration. This name will be used as the proxy name in the modular input configuration.
    • Host: Proxy host name or IP.
    • Port: Port used to connect to the proxy server.
    • Username: Username used to connect to the proxy server.
    • Password: Password for the username specified above.
    • Use SSL: Should SSL be used for the proxy configuration?

Creating New Credentials

By default creating a new modular input with a username and password specified will create the necessary encrypted credentials. However if you want to create encrypted credentials manually follow this process:

  • To create a new encrypted credential, click the Create New Credential button and fill in with the appropriate username and password.
  • The realm is the application name where the encrypted credential is created + the username.

NOTE: By default creating a new modular input will automatically create a new encrypted credential so this process is not necessary unless you need a new credential for another purpose.

Creating New Netskope Inputs

NOTE: You will need to configure a new modular input for each Netskope url

    • To create a new modular input configuration click Create New Modular Input.

      • Modular Input Name: Name for the modular input configuration.
      • URL: The URL provided for the Netskope instance without the https:// portion of the address.
      • Limit: The maximum number of events to collect on each interval, with a maximum of 5000.
      • Interval: The number of seconds between data collections.
      • Event Type: The type(s) of event(s) to collect separated by commas. Valid types are connection, alert, audit, infrastructure, and/or application.
      • Encrypted Token: Should the token be encrypted.
      • Token: The API token generated by Netskope for the instance.
      • Use Proxy: Will a proxy server be used.
      • Proxy Name: Name of the stanza configured in the proxy configuration.

This will configure the modular input settings in the SPLUNK_HOME/etc/apps/NetskopeAppForSplunk/local/inputs.conf. These settings are available under the modular input tab on the Application Configuration page as well as the data input page under Settings>Data Inputs>Netskope. If the token is to be encrypted then the encrypted token will be written to the encrypted credential store and the token on the modular input will show the value that used to retrieve the encrypted token.

NOTE: To make sure that the modular input gets enabled properly navigate to Settings>Data Inputs>Netskope> and press Disable then press Enable to enable the modular input.

All proxy, encrypted credential and modular input configurations are available in the tabs on the Application Configuration page.

Netskope and Enterprise Security

Netskope ships with the knowledge objects required for Enterprise Security integration. These objects need to be imported to Enterprise Security. This can be done in two ways:

    • Netskope App

      • If dashboards are required, install the App
      • This will also require app import settings to be updated in the Enterprise Security App Import settings.
    • Netskope TA

      • If dashboards are not required, install the TA.
      • App import settings of Enterprise Security will not need to be modified.
  • Do not install both the App and the TA on the Enterprise Security server. This may cause a precedence import error.

  • The default netskope_idx event type will need to be updated to properly locate the data for the Data Models of Enterprise Security.

Netskope Alert Actions

Netskope App For Splunk v1.0.6 introduces 2 alert actions, File Hash and URL lists. In order to use the Adaptive responses, a corresponding list must be created in the Netskope product. The list must have the same name for both URL and file hash lists.

  1. Configure the Adaptive Response Global configuration under the Application Configuration page of the TA/App.
  2. Click the button labeled Create New Netskope Alert Action Global Configuration and fill out the fields for hostname, token, and list.
  3. Once saved, you can then use the Alert Actions to either add or remove items from the lists. When configuring the Alert Action, you can choose either Add or Remove and the field name that contains the value to update.
  4. Please see the Adaptive Response in Enterprise Security documentation on how to run Adaptive Responses in Enterprise Security.
  5. Please see the Alerts documentation to create your own alerts and corresponding actions.

NOTE: When running adaptive responses from the Incident Review dashboard in Enterprise Security, the results are written to the notable index. If this needs changed, please contact support.

Netskope Time Offset

Netskope App For Splunk v1.1.2 introduces the ability to specify a time offset.This setting allows the user to specify an offset to be used to retrieve events that start further back in time. Example: the modular input runs and pulls events between 6:00 AM and 12:00 PM. Because the Netskope API may not process some events in real-time some events may not be available from the API until a later period. To handle this the Splunk admin can specify a time offset to go backwards to pull events.

  1. Configure the time offset in the inputs.conf configuration file in the local folder of the IA/App.
  2. This offset is only available in the inputs.conf file. To disable the time offset set this value to 0. To specify an offset specify the number of seconds to go back in time. Default is 0.

NOTE: This is an advanced setting and should only be set when directed by support. NetSkope support will guide you with the appropriate setting for your environment.

Customers running Enterprise Security (or any searches using a small timeframe): Some correlation searches in ES only look back 60 minutes. Using an offset may cause the searches in ES (or small timeframe searches) may not work properly. Therefore it may be necessary to tune some correlation searches to account for the offset.

Indexes

By default all events will be written to the main index. You should change the index on the modular input to match your specific index.

Troubleshoot Netskope App For Splunk

  1. Check the Monitoring Console (&gt;=v6.5) for errors
  2. Visit the Application Health dashboard

Another troubleshooting method for the Netskope App For Splunk app is using this search:

sourcetype= NetSkopeAppForSplunk :error

If you are still having problems, use the Command line and run this command:

$SPLUNK_HOME/bin/splunk diag --collect app:NetSkopeAppForSplunk

Send the generated diag file to Netskope App For Splunk support.

Update log.cfg

Copy the log.cfg file from default of the app to the local folder, and edit the settings to reflect which items need increased verbosity.

Upgrade Netskope App For Splunk

Upgrade Netskope App For Splunk by re-installing into your environment per Splunk Documentation and your environment (see steps above).

Full Data Reset

If you experiencing issues, and would like to reset the Netskope Data to factory install, there are few steps to take.

  1. Disable the input.
  2. Clear the indexed data. This is covered in the Splunk documentation
  3. Delete the checkpoint files in $SPLUNK_HOME/var/lib/splunk/modinputs/netskope
  4. Enable the input.

Lookups

Netskope App For Splunk contains no automatically generated lookups.

The following lookup files are generated automatically during Alert Action operations.

  • netskope_file_hash.csv
  • netskope_url.csv

Event Generator

Netskope App For Splunk does make use of an event generator. There are four sample event files supplied for event generation. These samples are found in the samples folder of the app and are:

  • netskope_alert.sample
  • netskope_application.sample
  • netskope_audit.sample
  • netskope_connection.sample

NOTE: To generate events the Eventgen app must be installed. The app and instructions can be found at https://splunkbase.splunk.com/app/1924/. This app should not be installed on a production system unless you understand the ramifications of generated data being mixed with production data.

Release Notes

Version 1.1.3
May 13, 2019

- Test and QA

- [NET-102] - Remove duplicates from default.meta

- New Feature

- [NET-93] - Web Dashboard

- Improvement

- [NET-98] - Health Application Page
- [NET-99] - Add alert action to log.cfg
- [NET-100] - Fix Health Checks
- [NET-101] - Health Checks for common issues

Version 1.1.2
April 5, 2019

[NET-89] - Update Tenant URL validator to avoid special characters
[NET-91] - Separate calls for applications and page events
[NET-92] - Configurable Offset Parameter

Version 1.1.1
Feb. 6, 2019

v1.1.1 fixes a bug in populating searches for Host dropdowns.

Version 1.1.0
Jan. 25, 2019

v1.1.0 introduces Adaptive Response Actions, and improved data collection.

Version 1.0.5
Sept. 11, 2018

v1.0.5
Improvement
[NET-68] - Feature Request - Add infrastructure eventtype
[NET-69] - Update UserAgent
[NET-70] - Implement KVStore Checkpointing (advanced usage)
[NET-71] - Implement "per page" output of events

209
Installs
1,063
Downloads
Share Subscribe LOGIN TO DOWNLOAD

Subscribe Share

AppInspect Tooling

Splunk AppInspect evaluates Splunk apps against a set of Splunk-defined criteria to assess the validity and security of an app package and components.

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
© 2005-2019 Splunk Inc. All rights reserved.
Splunk®, Splunk>®, Listen to Your Data®, The Engine for Machine Data®, Hunk®, Splunk Cloud™, Splunk Light™, SPL™ and Splunk MINT™ are trademarks and registered trademarks of Splunk Inc. in the United States and other countries. All other brand names, product names, or trademarks belong to their respective owners.