Send Netskope logs to LogPulse
Netskope events and alerts through the API v2 data export: cloud app activity, web pages, network traffic, the admin audit log and DLP, malware, UBA and policy alerts.
Configure → Sources → Cloud. LogPulse reads the Netskope REST API v2 data export itself, without an agent. Events land in the web, audit, network indexes with source netskope and fill the Web, Alerts, Change data models.Overview
- Netskope REST API v2 data export to Integration poller
- Integration poller to index=web
- Integration poller to index=audit
- Integration poller to index=network
LogPulse signs in to Netskope with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.
What you need
- A REST API v2 token with read access to the data export
- In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.
1. Create a credential in Netskope
| Field in LogPulse | Where you find it |
|---|---|
| Tenant | The address of your Netskope tenant, such as acme.goskope.com. |
| API v2 token | In Netskope: Settings, Tools, REST API v2. Give it read access to /api/v2/events/dataexport/events and /alerts. Stored encrypted and never shown again. |
2. Add the integration in LogPulse
Go to Configure → Sources → Cloud and choose Netskope. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.
What arrives
| Data source | Index | Source | Sourcetype | What it holds |
|---|---|---|---|---|
| Application events | web | netskope | netskope:application | Cloud app activity: user, app, activity (upload, share, login), object and action. |
| Alerts | web | netskope | netskope:alert | DLP, malware, malicious site, compromised credential, policy, UBA and watchlist alerts. |
| Audit log | audit | netskope | netskope:audit | Admin changes in the Netskope tenant. |
| Page events (off by default) | web | netskope | netskope:page | Every web page a user opened through Netskope. High volume. |
| Network events (off by default) | network | netskope | netskope:network | Private access and cloud firewall sessions. High volume. |
The index is the kind of data and the source is the product, so detection rules for that kind of data find Netskope without changes.
Fields and data models
| Data model | What you get |
|---|---|
| Web | App activity and pages with user, app, URL and action. |
| Alerts | DLP, malware, UBA and policy alerts with severity. |
| Change | Admin changes in Netskope. |
Field names follow the CIM field names. These are the fields LogPulse sets on Netskope events; a field is left out when Netskope did not send a value.
access_methodactionalert_typeappbytescategorydestdest_countrydest_ipdest_portdvcfile_hashfile_namehttp_user_agentidobjectobject_categoryospolicyresultseveritysignaturesignature_idsrc_countrysrc_iptransporturluservendor_action
The original record of Netskope is kept with each event under raw, so nothing the vendor sent is lost.
3. Check the data
The first events arrive within a few minutes. Check what came in:
earliest=-1h index IN (web, audit, network) source IN (netskope)
| stats count by index, source, sourcetypeThe integration page in LogPulse shows when it last read events and the last error, if any.
Troubleshooting
The connection test names what is wrong. These are the answers you are most likely to see.
| What you see | What to do |
|---|---|
| Netskope refused the token. Give it read access to /api/v2/events/dataexport/events and /alerts. | Edit the REST API v2 token under Settings, Tools and add read access to both data export endpoints. |
| tenantUrl is your tenant, e.g. acme.goskope.com | Use the address of your Netskope tenant, without a path. |
| The test passes but no events arrive. | Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Netskope may also simply have had nothing new. |
Frequently asked questions
- How do I send Netskope logs to LogPulse?
- Add the Netskope cloud integration under Configure, Sources, Cloud in LogPulse and fill in Tenant, API v2 token. LogPulse reads the Netskope REST API v2 data export itself, every five minutes by default; there is nothing to install.
- Which permissions does LogPulse need in Netskope?
- A REST API v2 token with read access to the data export. Read access is enough for collecting logs.
- Which index does Netskope data go to?
- The index is the kind of data: web, audit, network. The source is the product: netskope. Each data source has its own sourcetype, listed on this page.
- Which data models does Netskope fill?
- Web, Alerts, Change. Detection rules and dashboards written for a data model work on Netskope without changes.
- Why is Page events and Network events off by default?
- To keep your daily ingest down until you need it: Page events, Network events are high volume or of use to fewer teams. Tick the data source in the integration to switch it on.
- Why are Netskope page and network events off by default?
- They are high volume: every web page and every session. Switch them on in the integration when you need them for web or network detections.