Skip to main content

Netskope Help

Integrations

Netskope supports third party integration through Netskope IoT Security UI.

List_of_integration.png
Integrate CrowdStrike with Netskope IoT Security

Follow the procedure to integrate CrowdStrike:

  1. Navigate to the Manage > Integrations menu. Select Create Integration tab. You will see a Create New Integration window.

  2. Set active or inactive state of the integration on creation.

  3. Give a unique name to the integration.

  4. Select the type as CrowdStrike from the dropdown list.

  5. Provide the CrowdStrike Client ID and Client Secret key for CrowdStrike.

  6. Provide CrowdStrike base URL.

  7. The default consumer is compliance to calculate the compliance of the devices. Optionally you can use CrowdStrike for Asset Management.

  8. Click the Create Integration button.

    Crowdstrike_Integratuion.png

    Note

    Click the Cancel button to forbid the action.

Integrate Kaseya VSA with Netskope IoT Security

Follow the procedure to integrate Kaseya VSA:

  1. Navigate to the Manage > Integrations menu. Select Create Integration tab. You will see a Create New Integration window.

  2. Set active or inactive state of the integration on creation.

  3. Give a unique name to the integration.

  4. Select the vendor as Kaseya VSA from the dropdown list.

  5. Provide Kaseya VSA Username and Token to connect from Netskope IoT Security.

  6. Provide Kaseya VSA base URL.

  7. The default consumer is Asset Management to pull assets from Kaseya VSA to Netskope IoT Security. Optionally you can use Kaseya VSA for Tag consumption.

  8. Click the Create Integration button.

Kaseya_VSA_Integration.png
Integrate Mist with Netskope IoT Security

Follow the procedure to integrate Mist:

  1. Navigate to the Manage > Integrations menu. Select Create Integration tab. You will see a Create New Integration window.

  2. Set active or inactive state of the integration on creation.

  3. Give a unique name to the integration.

  4. Select the vendor as Mist from the dropdown list.

  5. Provide Mist API Key to connect from Netskope IoT Security.

  6. Provide Mist base URL.

  7. On correct API Key validation, the Netskope IoT Security will fetch the vendor sites.

  8. The default consumer is Asset Discovery to discover devices from Mist to Netskope IoT Security. Optionally you can use Mist for Tag consumption.

  9. Click the Create Integration button.

Mist_Integration.png
Integrate Meraki with Netskope IoT Security

Follow the procedure to integrate Meraki:

  1. Navigate to the Manage > Integrations menu. Select Create Integration tab. You will see a Create New Integration window.

  2. Set active or inactive state of the integration on creation.

  3. Give a unique name to the integration.

  4. Select the vendor as Meraki from the dropdown list.

  5. Provide Meraki API Key to connect from Netskope IoT Security.

  6. Provide Meraki base URL.

  7. On correct API Key validation, the Netskope IoT Security will fetch the vendor sites.

  8. The default consumer is Asset Discovery to discover devices from Meraki to Netskope IoT Security. Optionally you can use Meraki for Tag consumption.

  9. Click the Create Integration button.

Meraki_Integraton.png
Edit Existing Integration Configuration

You can edit, enable, disable and delete the existing integrations. Follow the procedure to edit the integration:

  1. Navigate to the Manage > Integrations menu.

  2. Select an integration from the list. You will see an Edit Integration <name> window.

  3. You can activate or deactivate the integration configuration.

  4. You can edit the integration name, base URL and consumer fields.

  5. You can update the credentials, base URL, API key, and vendor sites for Mist and Meraki .

  6. You can update the consumers.

  7. Click the Save Integrations” button.

    Edit_Integration.png

    Note

    Click the Cancel button to forbid the action. Click the Delete button to delete the selected integration. You can not delete the integration when it is connected to the integration based compliance configuration.