# Netskope

Netskope is a security service edge (SSE) platform that protects users and data accessing cloud services, websites, and private applications against web threats, data exfiltration, and risky cloud activity. Connecting Netskope forwards alerts and events to Radiant Security through the Netskope REST API v2. Radiant uses the alerts and events for AI triage, giving analysts cloud and web activity context alongside other security telemetry.

At the end of this configuration, you provide Radiant Security with the following values:

* **Tenant URL**
* **API token**

### Prerequisites

* [ ] Admin access to Netskope

### Generate an API token in Netskope

{% stepper %}
{% step %}

#### **Enable the REST API**

Sign in to the Netskope console with an admin account. Navigate to **Settings > Tools > REST API v2**. If the **REST API** toggle is off, click the **Pencil** button, enable the toggle, and click **Save**.

<div align="left"><figure><img src="/files/rA73wl9dnCJxmrxoiMLB" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

<div align="left"><figure><img src="/files/5VwUugPsyHIjDhKhWdby" alt="" width="375"><figcaption></figcaption></figure></div>

#### **Create the token**

Click **New Token**. Enter `RadiantConnector` as the **Token Name** and select **12 Months** under **Expire In**.

<div align="left"><figure><img src="/files/gJM2bv0Xgu5dQrB9gQqE" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
If you set an expiration on the token, update the token value in the Radiant Security connector before it expires to prevent disruptions in data collection.
{% endhint %}
{% endstep %}

{% step %}

#### **Grant endpoint access**

Click **Add Endpoint** and select the following API endpoints:

* All entries that start with `/api/v2/events/dataexport/events`
* All entries that start with `/api/v2/events/dataexport/alerts`
* `/api/v2/incidents/uba/getuci`
* `/api/v2/incidents/dlpincidents`
* `/api/v2/events/data/alert`

<div align="left"><figure><img src="/files/hsAZSAn2pUM0fW1gyjIP" alt="" width="563"><figcaption></figcaption></figure></div>

Under **Privilege**, select **Read**.
{% endstep %}

{% step %}

#### **Copy the token**

Click **Save** and copy the token shown in the popup. This is the only opportunity to copy the token. Store it securely.
{% endstep %}
{% endstepper %}

### Add the data connector in Radiant Security

1. Sign in to [Radiant Security](https://app.radiantsecurity.ai/).
2. From the navigation menu, select **Settings** > **Data Connectors** and click **+ Add Connector**.
3. Search for and select **Netskope API v2**, then click **Data Feeds**.
4. Under **Select your data feeds**, select **Netskope API v2** and click **Credentials**.
5. Under **Credential Name**, enter a descriptive name (e.g., `Netskope Token`).
6. In the **Tenant URL** field, enter the URL you use to access the Netskope console (for example, `https://companyName.goskope.com`).
7. In the **API Token** field, paste the token you generated in Netskope.
8. Click **Add Connector** to save the configuration.

### Verify ingestion

After Netskope begins forwarding, confirm alerts and events are reaching Radiant.

1. In Radiant, navigate to [Log Management](https://app.radiantsecurity.ai/logs).
2. Filter by `rs_connectorType:"netskope_api_v2"`.
3. Confirm recent alerts and events appear.

{% hint style="info" %}
Allow several minutes for alerts and events to be parsed, indexed, and available for search.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.radiantsecurity.ai/radiant-connectors/data-connectors/netskope.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.