Netskope Help

MISP Plugin for Threat Exchange

This document explains how to configure the MISP integration with the Cloud Threat Exchange module of the Netskope Cloud Exchange platform. This integration allows for sharing of URLs and file hashes with Netskope that has been identified by MISP or Netskope.

Prerequisites

To complete this configuration, you need:

  • A Netskope Tenant (or multiple, for example, production and development/test instances).

  • Secure Web Gateway subscription for URL sharing.

  • A Netskope Threat Prevention subscription for malicious file hash sharing

  • A Netskope Cloud Exchange tenant with the Threat Exchange module already configured.

  • A MISP Instance.

Workflow
  1. Get your MISP URL and API key.

  2. Configure the MISP Plugin.

  3. Configure sharing between Netskope and MISP.

  4. Validate the MISP Plugin.

Click play to watch a video.

 

Your MISP Instance URL and API key are needed to later configure the MISP plugin in Threat Exchange.

  1. Log in to your MISP Instance.

  2. Copy your MISP Instance URL.

  3. In the Home page left nav panel, click Automation.

  4. Your MISP API key is shown below the first paragraph on the page. Copy your API key.

    image1.png
  1. Choose Settings from the Navigation Pane then Plugins

  2. Select the MISP plugin box to open the plugin creation pages.

  3. Enter the Basic Information on the first page:

    • Configuration Name: Enter a name appropriate for your integration.

    • Poll Interval: Adjust to environment needs. We recommend not to go below 5 minutes for production environments.

    image2.png
  4. Click Next.

  5. Enter the Configuration Parameters on the second page:

    • Base URL: Enter the URL of your MISP Instance.

    • API Token: Enter your MISP API key.

    • Enter appropriate Event Name to be created on MISP for indicators which are shared with this plugin configuration.

    • The rest of this form can remain as default.

    image3.png
  6. Click Save.

    image4.png
  1. Go to Threat Exchange and select Sharing. The Sharing page displays the existing relationships for each sharing configuration in grid view as shown below. The Sharing page also has inputs to configure new sharing from one plugin to another.

  2. Click Add Sharing Configuration, and in the Source Configuration dropdown list, select MISP.

  3. Select a Business Rule, and then select Netskope for the Destination Configuration. Sharing configurations are unidirectional. data obtained from one plugin is shared with another plugin. To achieve bi- or multi-directional sharing, configure each separately.

  4. Select a Target. Each plugin will have a different target or destination for the IoC.

  5. Repeat steps 2-4, but select Netskope as the Source Configuration and MISP as the Destination Configuration.

  6. Click Save.

Adding a new sharing configuration on the active source poll will share the existing IoCs of the configuration to the destination configuration. Whenever a new sharing configuration is built, all the active IoCs will also be considered for sharing if they match the source/destination combination.

Note

Plugins that do not have API for ingesting data cannot receive threat data. This is true of the installed plugin API Source, which provides a bucket associated with an API endpoint for remote 3rd-party systems to push data to. Once a Sharing policy has been added, it takes effect.

After a sharing configuration has been created, the sharing table will show the rule being invoked, the source system providing the potential IoC matches, the destination system that will receive matching IoC, and the target applicable to that rule. Multiple Sharing configurations can be made to support mapping certain IoC to multiple targets even on the system destination system.

Modify, Test, or Delete a Sharing Configuration

Each configuration supports 3 actions:

image10.png
  • Edit the rule by clicking on the pencil icon.

  • Test the rule by clicking on the synchronization icon. This tests how many IoC will actually be sent to the destination system based on the timeframe and the rule.

  • Delete the rule by clicking on the garbage can icon.

In order to validate the integration you must have Netskope Alerts and/or MISP attributes/indicators. Polling Intervals was defined during plugin configuration. You can validate in both Netskope and MISP.

  1. In Cloud Exchange, go to Threat Exchange, and click Threat IoCs. You should see records from your MISP plugin. You can filter based on Source values to check both the Netskope and MISP plugin.

    image10.png
  2. In the Netskope UI, go to Policies > File > Your Custom File Profile and click File Hash.

    image11.png
  3. In the MISP Console, go to Event Actions > List Events and click Id of the event having info same as value of your Event Name configuration parameter.

    image12.png

    The event page will be displayed with the attached indicators as shown in the image below:

    image13.png
  4. If data is not being brokered between the platforms, you can look at the Audit Logs in Cloud Exchange. In Cloud Exchange, go to Logging and ook through the logs for errors.

    image14.png