Release Notes
1.2.0 (Requires minimum Cloud Exchange version 6.1.0 and minimum Netskope BWAN Tenant version 1.2.0)
Added
- Added support to new Event Type: Network Event and Alert Type: Alerts (V2).
1.1.0
Changed
- Updated Borderless WAN API for the events endpoint.
1.0.0
Added
- Initial release.
This document explains how to configure the Netskope Borderless WAN v1.2.0 plugin with the Log Shipper module of the Netskope Cloud Exchange platform. This plugin is used to fetch Events (Audit, Authentication, Client, Gateway, System) from the Monitor > Events page, Network Events (Flow/Traffic logs) from the Monitor > Flows page, and Alerts from the Monitor > Alerts(V2) page of the Netskope Borderless WAN Tenant.
Prerequisites
To complete this configuration, you need:
- A Borderless WAN Tenant (or multiple, for example, production and development/test instances).
- A Netskope Cloud Exchange tenant with the Tenant plugin and Log Shipper plugin already configured.
- A 3rd-party plugin (for example, Syslog) already configured.
- Minimum Netskope Borderless WAN Tenant plugin version required 1.2.0 for the plugin configuration.
- Connectivity to the Borderless WAN Tenant host.
Example:https://<tenant>.api.infiot.net - For Secrets Manager configuration, refer to Secrets Manager. To set up Azure Key Vault Secrets Manager, refer to Prerequisites for Azure Key Vault Secrets Manager.
Netskope Borderless WAN Plugin Support
This plugin is used to fetch Events (Audit, Authentication, Client, Gateway, System) from the Monitor > Events page, Network Events (Flow/Traffic logs) from the Monitor > Flows page, and Alerts from the Monitor > Alerts(V2) page of the Netskope Borderless WAN Tenant.
| Data Type | Support |
|---|---|
| Alerts Support | Yes (Alerts (V2)) |
| Event Support | Yes (Audit, Authentication, Client, Gateway, System, Network Events) |
| WebTx Support | Not Supported |
| CE Logs | Not Supported |
Permissions
You need to have these permissions in the Auth Token:
[
{
"rap_resource": "",
"rap_privs": [
"privAuditRecordRead",
"privMonitorAlertRead",
"privTenantRead"
]
}
]
API Details
List of APIs Used
| API Endpoint | Method | Use Case |
|---|---|---|
| /v2/auditevents | GET | Fetch Events (Audit, Authentication, Client, Gateway, System) from the Borderless WAN Tenant. |
| /v2/networkevents | GET | Fetch Network Events (Flow/Traffic logs) from the Borderless WAN Tenant. |
| /v2/alerts | GET | Fetch Alerts (V2) from the Borderless WAN Tenant. |
Note that all the API calls for a source plugin are made from the Tenant plugin, so the user agent will be of the tenant plugin.
Fetch Events
API Endpoint: <BASE URL>/v2/auditevents
Method: GET
Request Headers
| Key | Value |
|---|---|
| Authorization | Bearer <API TOKEN> |
| User-Agent | netskope-ce-7.0.0-tenant-netskope_borderless_wan-v1.2.0 |
Request Parameters
| Key | Value |
|---|---|
| first | 100 |
| after | end_cursor (end cursor from previous response) |
| filter | event_time>='<START TIME>' AND event_time<'<END TIME>' AND (type: <EVENT TYPE>)For example: event_time>='2025-01-29T12:20:42.124910Z' AND event_time<'2025-01-29T12:58:01.122000Z' AND (type: AUDIT OR type:AUTHENTICATION OR type:CLIENT OR type:GATEWAY OR type:SYSTEM) |
Sample API Response
{
"page_info": {
"end_cursor": "WyIyMDI1LTAxLTI5VDEyOjQzOjIyLjAzNVoiLCI2NzlhMjI2YTIyNmUyYTBmYzU2YzJjOGIiXQ",
"has_next": true,
"total_count": 4
},
"data": [
{
"id": "679a226a226e2a0fc56c2c8b",
"actor_nrn": "nrn:bwan:authn:us:5dadf8a91602d141e060c93e:token:6245b39c611790724910338f",
"target_nrn": "nrn:bwan:site:us:5dadf8a91602d141e060c93e:site:673757abb51faf57f043a36a",
"type": "AUDIT",
"subtype": "AUDIT_GATEWAY",
"activity": "SITE_UPDATED",
"note": "",
"event_time": "2025-01-29T12:43:22Z"
},
{
"id": "679a24c905aa7377e0924ab0",
"actor_nrn": "nrn:bwan:authn:us:5dadf8a91602d141e060c93e:user:656e127fd8a92afdc8447576",
"target_nrn": "nrn:bwan:authn:us:5dadf8a91602d141e060c93e:user:656e127fd8a92afdc8447576",
"type": "AUTHENTICATION",
"subtype": "AUTHENTICATION_USER",
"activity": "USER_LOGIN",
"note": "",
"event_time": "2025-01-29T12:53:29Z"
},
{
"id": "679a20d105aa7377e0924931",
"actor_nrn": "nrn:bwan:authn:us:5dadf8a91602d141e060c93e:token:675145c90f1ebb6e8c59983b",
"target_nrn": "nrn:bwan:site:us:5dadf8a91602d141e060c93e:site:675145b90f1ebb6e8c59982a",
"type": "CLIENT",
"subtype": "CLIENT_SYSTEM",
"activity": "SITE_CLIENT_DEVICE_ENROLL_STARTED",
"note": "",
"event_time": "2025-01-29T12:36:34Z"
},
{
"id": "679a259d05aa7377e0924afa",
"actor_nrn": "nrn:bwan:authn:us:5dadf8a91602d141e060c93e:token:67343709ca023562f3b8f02e",
"target_nrn": "nrn:bwan:site:us:5dadf8a91602d141e060c93e:site:6734367c1f66fecb2dff8554",
"type": "GATEWAY",
"subtype": "GATEWAY_UNDERLAY",
"activity": "SITE_LINK_UP",
"note": "wlp0s0",
"event_time": "2025-01-29T12:57:00Z"
},
{
"id": "679a25b439a4bd42a70bb934",
"actor_nrn": "nrn:bwan:authn:us:5dadf8a91602d141e060c93e:token:6245b39c611790724910338f",
"target_nrn": "nrn:bwan:tenant:us:5dadf8a91602d141e060c93e:tenant:5dadf8a91602d141e060c93e",
"type": "SYSTEM",
"subtype": "SYSTEM_SSE_TUNNEL",
"activity": "SITE_NS_TUNNEL_ERROR",
"note": "https://tunnel-test.goskope.com (accountId: 62b3a3e3b7f108a3b8b74815): get tunnels: status: 401 -> Unauthorized\naccountId: 62b3a3e3b7f108a3b8b74815",
"event_time": "2025-01-29T12:57:24Z"
}
]
}
Fetch Network Events
API Endpoint: <BASE URL>/v2/networkevents
Method: GET
Request Headers
| Key | Value |
|---|---|
| Authorization | Bearer <API TOKEN> |
| User-Agent | netskope-ce-7.0.0-tenant-netskope_borderless_wan-v1.2.0 |
Request Parameters
| Key | Value |
|---|---|
| first | 100 |
| after | end_cursor (end cursor from previous response) |
| filter | ended_at>='<START TIME>' AND ended_at<'<END TIME>' |
Sample API Response
{
"page_info": {
"end_cursor": "WyIyMDI2LTEwLTIxVDEyOjE1OjE1Ljk4WiIsIjc5NjRkYzU2MmFiNDViNTQiXQ",
"has_next": true
},
"data": [
{
"id": "M2JlMDZjNzNmOGNlYjM1MXwyMDI2LTEwLTIxVDEyOjE1OjM2LjM2N1p8ODk2NzcxODkxMjQ5NDg1NzgyNw==",
"source_ip": "169.254.3.132",
"destination_ip": "169.254.3.167",
"source_port": 7777,
"destination_port": 7777,
"mac": "00:00:00:00:00:00",
"device_name": "169.254.3.132",
"application_id": "216",
"application_name": "User Datagram Protocol",
"site_id": "69dfd187fdab1797f44a3a92",
"in_interface_logical_name": "GE1",
"out_interface_logical_name": "GE1",
"started_at": "2026-10-09T14:17:03Z",
"ended_at": "1970-01-01T00:00:00Z",
"packets_sent": 50,
"packets_received": 0,
"bytes_sent": 1943,
"bytes_received": 0,
"duration_millis": 1029512888,
"protocol": "UDP",
"peer_type": "INFIOT",
"peer_role": "SPOKE",
"vpn_nat_source_ip": "0.0.0.0",
"vpn_nat_source_port": 0,
"vpn_nat_destination_ip": "0.0.0.0",
"segment_id": 0,
"latency_millis": 0,
"destination_country": "Reserved/Private",
"scheduler_queue": "HIGH",
"rx_loss_percent": 0,
"tx_loss_percent": 0,
"network_latency_millis": 0,
"jitter_millis": 0,
"peer_name": "mgmtgw",
"is_closed": false
},
{
"id": "Nzk2NGRjNTYyYWI0NWI1NHwyMDI2LTEwLTIxVDEyOjE1OjE1Ljk4WnwxMDg2OTkwMzY2MDUwNjA5NTcy",
"source_ip": "169.254.0.53",
"destination_ip": "169.254.2.251",
"source_port": 7777,
"destination_port": 7777,
"mac": "00:00:00:00:00:00",
"device_name": "169.254.0.53",
"application_id": "216",
"application_name": "User Datagram Protocol",
"site_id": "68107a34144df1459e958e47",
"in_interface_logical_name": "GE1",
"out_interface_logical_name": "GE2",
"started_at": "2026-10-19T03:30:28Z",
"ended_at": "1970-01-01T00:00:00Z",
"packets_sent": 245257,
"packets_received": 0,
"bytes_sent": 9509853,
"bytes_received": 0,
"duration_millis": 204287046,
"protocol": "UDP",
"peer_type": "INFIOT",
"peer_role": "SPOKE",
"vpn_nat_source_ip": "0.0.0.0",
"vpn_nat_source_port": 0,
"vpn_nat_destination_ip": "0.0.0.0",
"segment_id": 0,
"latency_millis": 0,
"destination_country": "Reserved/Private",
"scheduler_queue": "HIGH",
"rx_loss_percent": 0,
"tx_loss_percent": 0,
"network_latency_millis": 10,
"jitter_millis": 0,
"peer_name": "mp-vm-spoke",
"is_closed": false
}
]
}
Fetch Alerts (V2)
API Endpoint: <BASE URL>/v2/alerts
Method: GET
Request Headers
| Key | Value |
|---|---|
| Authorization | Bearer <API TOKEN> |
| User-Agent | netskope-ce-7.0.0-tenant-netskope_borderless_wan-v1.2.0 |
Request Parameters
| Key | Value |
|---|---|
| first | 100 |
| after | end_cursor (end cursor from previous response) |
| filter | (opened_at>='<START TIME>' AND opened_at<'<END TIME>') OR (closed_at>='<START TIME>' AND closed_at<'<END TIME>') |
Sample API Response
{
"page_info": {
"end_cursor": "WyI2YWM4MWIyZGEyMTk4M2E1YjVkN2M0ZWQiXQ",
"has_next": true,
"total_count": 972
},
"data": [
{
"id": "6ac81b2d1c9449a3ebdc193a",
"monitor_id": "6ac73666fa4016413e66fe7c",
"labels": {
"site_id": "6a7042ea0dfbcddb54899f92",
"site_name": "mgmtgw"
},
"state": "open",
"severity": "medium",
"opened_at": "2026-10-08T22:37:33Z"
},
{
"id": "6ac81b2da21983a5b5d7c4ed",
"monitor_id": "6ac7dac96ba9932eb61a8e11",
"labels": {
"site_name": "mgmtgw",
"site_id": "6a7042ea0dfbcddb54899f92"
},
"state": "closed",
"severity": "critical",
"opened_at": "2026-10-08T22:37:33Z",
"closed_at": "2026-10-09T11:03:49Z"
}
]
}
Performance Matrix
This performance reading was conducted on a Large Stack in Cloud Exchange with these VM specifications.
| Description | Specifications |
|---|---|
| Stack details | Size: Large RAM: 32 GB CPU: 16 Cores |
| Events pulled from Borderless WAN | ~80k EPM |
User Agent
netskope-ce-7.0.0-tenant-netskope_borderless_wan-v1.2.0
All the API calls for a source plugin are made from the Borderless WAN tenant plugin, so the user agent will be that of the tenant plugin.
Workflow
- Generate an Auth Token on your Borderless WAN Tenant.
- Configure the Borderless WAN Plugin for Log Shipper.
- Configure a Business Rule.
- Configure Log Delivery.
- Validate the Borderless WAN plugin.
Click play to watch a video.
Generate an Auth Token on your Borderless WAN Tenant
-
Log in to the Netskope Borderless WAN Tenant.

-
Go to Settings > API Token and click New Token.

-
Enter the Token Name, Expiration, and Description as per your requirement. For the permissions, refer to Permissions.
-
Click Save and copy the generated token.
The generated token will be used while configuring the Netskope Borderless WAN Tenant in Cloud Exchange.
Configure the Netskope Borderless WAN for Log Shipper Plugin
-
In Cloud Exchange, go to Settings > Plugin Store. Under the CLS category, search for and select the Netskope Borderless WAN v1.2.0 (CLS) plugin.

-
Enter a plugin configuration name and select your configured Borderless WAN tenant:
- Configuration Name: Plugin configuration name.
- Tenant: Tenant to pull alerts from. Select your Borderless WAN tenant.

-
Click Next and enter Configuration Parameters:
- Event Types: Selected types of events will be fetched. At least one Event Type must be selected.
- Initial Range for Events (in hours): Number of hours to pull the events data for the initial run. The value must be between 0 and 8760.
- Alert Types: Selected types of alerts will be fetched. At least one Alert Type must be selected.
- Initial Range for Alerts (in days): Number of days to pull the alerts data for the initial run. The value must be between 0 and 365.

-
Click Save. The plugin configuration will be available on the Log Shipper > Plugins page.

Configure a Log Shipper Business Rule for the Borderless WAN Plugin
-
In Log Shipper, go to Business Rules.
-
By default, there is a business rule that filters all alerts and events. If you want to filter out any specific type of alert or event, click Create New Rule, and configure a new business rule by adding a rule name and filter(s).
If you want to only filter the Borderless WAN events and alerts, create a new rule and select the Borderless WAN types from the following options: bwan_audit, bwan_authentication, bwan_system, bwan_gateway, bwan_client, bwan_network_event, and bwan_alert_v2.

-
Click Save.
Configure Log Delivery for the Borderless WAN Plugin
-
In Log Shipper, go to Log Delivery and click Add Log Delivery Configuration.
-
Select the Source Configuration (your Borderless WAN plugin configuration), the Destination Configuration (Syslog, or as per your requirement), a Business Rule, and then click Save.

-
After the Log Delivery configuration is added, the data will start being pulled from the Borderless WAN tenant, transformed, and ingested into the Destination platform.

Validate the Borderless WAN Plugin
Validate the Pull
In Cloud Exchange, go to Logging and search for the pulled logs.







Validate the Events and Alerts on the Borderless WAN Tenant
-
Log in to your Borderless WAN tenant.
-
Go to Monitor > Events. The plugin pulls the Audit, Authentication, Client, Gateway, and System events from this page.


-
Go to Monitor > Flows. The plugin pulls the Network events from this page.

-
Go to Monitor > Alerts(V2). The plugin pulls the alerts from this page.

Troubleshooting the Borderless WAN Plugin
No events are pulled even though the plugin is enabled
What to do: Verify that the events and alerts are present on the Borderless WAN tenant for the same time frame. For the steps, see Validate the Events and Alerts on the Borderless WAN Tenant.
Known Behaviors
-
You may encounter this error in the logs:
02/05/2025 12:06:59 PM – error Error occurred while sharing analytics using User-Agent with Netskope What to do: Since you are using a Borderless WAN Tenant instead of a Netskope tenant, it will not recognize the User-Agent of Netskope, so it will display this error log.
Limitation
Borderless WAN API Limitations: We have observed inconsistencies in the data returned by BWAN APIs, which may lead to discrepancies in the event counts displayed on the platform versus those received and sent from CE. This is because the BWAN APIs are currently facing the late breaking events issue.

