Netskope Alerts and Events (via Codeless Connector Framework)
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | NetskopeAlertsEvents |
| Publisher | Netskope |
| Used in Solutions | Netskopev2 |
| Collection Method | CCF |
| Connector Definition Files | NetskopeAlertsEvents_ConnectorDefination.json |
| DCR Definition Files | NetskopeAlertsEvents_DCR.json |
| CCF Configuration | NetskopeAlertsEvents_Poller.json |
| CCF Capabilities | APIKey |
| Microsoft Learn | View on Learn |
Netskope Security Alerts and Events
Tables Ingested
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
NetskopeAlerts_CL |
✓ | ✓ | ✓ |
NetskopeEventsApplication_CL |
? | ✓ | ? |
NetskopeEventsAudit_CL |
? | ✓ | ? |
NetskopeEventsConnection_CL |
? | ✓ | ? |
NetskopeEventsDLP_CL |
? | ✓ | ? |
NetskopeEventsEndpoint_CL |
? | ✓ | ? |
NetskopeEventsInfrastructure_CL |
? | ✓ | ? |
NetskopeEventsNetwork_CL |
? | ✓ | ? |
NetskopeEventsPage_CL |
? | ✓ | ? |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions:
- Workspace (Workspace): Read and Write permissions are required.
Custom Permissions:
- Netskope organisation url: The Netskope data connector requires you to provide your organisation url. You can find your organisation url by signing into the Netskope portal.
- Netskope API key: The Netskope data connector requires you to provide a valid API key. You can create one by following the Netskope documentation.
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. STEP 1 - Create a Netskope API key.
Follow the Netskope documentation for guidance on this step.
2. STEP 2 - Enter your Netskope product Details
Enter your Netskope organisation url & API Token below:
Organisation Url: Enter your organisation url
API Key: (password field)
Netskope Alerts Remediation (select)
- Yes
- No
Netskope Alerts Uba (select)
- Yes
- No
Netskope Alerts Security Assessment (select)
- Yes
- No
Netskope Alerts Quarantine (select)
- Yes
- No
Netskope Alerts Policy (select)
- Yes
- No
Netskope Alerts Malware (select)
- Yes
- No
Netskope Alerts Malsite (select)
- Yes
- No
Netskope Alerts DLP (select)
- Yes
- No
Netskope Alerts CTEP (select)
- Yes
- No
Netskope Alerts Watchlist (select)
- Yes
- No
Netskope Alerts Compromised Credentials (select)
- Yes
- No
Netskope Alerts Content (select)
- Yes
- No
Netskope Alerts Device (select)
- Yes
- No
Netskope Events Application (select)
- Yes
- No
Netskope Events Audit (select)
- Yes
- No
Netskope Events Connection (select)
- Yes
- No
Netskope Events DLP (select)
- Yes
- No
Netskope Events Endpoint (select)
- Yes
- No
Netskope Events Infrastructure (select)
- Yes
- No
Netskope Events Network (select)
- Yes
- No
Netskope Events Page (select)
- Yes
- No OPTIONAL: Specify the Index the API uses.
Configuring the index is optional and only required in advanced scenario's. Netskope uses an index to retrieve events. In some advanced cases (consuming the event in multiple Microsoft Sentinel workspaces, or pre-fatiguing the index to only retrieve recent data), a customer might want to have direct control over the index.
- Index: NetskopeCCP
3. STEP 3 - Click Connect
Verify all fields above were filled in correctly. Press the Connect to connect Netskope to Microsoft Sentinel.
- Click 'connect' to establish connection
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊