Netskope Logs connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Netskope Logs from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Netskope Logs ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports a set of Netskope event tables (such as audit, application, and network) and alert tables (such as alert_dlp, alert_malware, and alert_uba). For the full list and schemas, see Supported source tables.
Which authentication method does the connector support?
The connector supports a Netskope REST API v2 token only. OAuth and basic authentication aren't supported.
Should I use a personal Netskope account or a service account?
Use a Netskope service account. Netskope's documentation recommends creating REST API v2 tokens for a service account. If the individual user who created the token leaves your organization, the connector might stop working.