AlienVault® USM Anywhere™

zScaler NSS

When you configure zScaler Nanalog Streaming Service (NSS) to send log data to USM Anywhere, you can use the zScaler NSS plugin to translate raw log data into normalized events for analysis. The table below provides some basic information for the plugin:

Plugin Information
Device Details
Vendor zScaler
Device Type Proxy
Connection Type Syslog

Integrating zScaler NSS

Before you configure the zScaler NSS integration, you must have the IP Address of the USM Anywhere Sensor.

To configure zScaler NSS to send log data over syslog to USM Anywhere

  1. Log in to the administration portal for Zscaler NSS.
  2. In the navigation pane, select Administration > Settings > Nanolog Streaming Service.
  3. From the NSS Feeds tab, click Add NSS Feed.
  4. In Feed Name, enter a name for the NSS feed.
  5. In NSS Type, keep the default: NSS for Web.
  6. From the NSS Server list, select the ZScaler NSS system.
  7. From the Status list, select Enabled.
  8. In SIEM IP Address, enter the IP address of the USM Anywhere Sensor.
  9. In SIEM TCP Port, enter 601.
  10. In Log Type, select Alerts and choose which level(s) alerts you want to send.
  11. Click Save and then activate your changes.

Plugin Enablement

For plugin enablement information, see Manual Integration Management.

Available Plugin Fields

The following plugin fields are important attributes extracted from the syslog message. The USM Anywhere reports use these fields, and you can also reference them when creating custom reports. In addition to reporting, the USM Anywhere correlation rules make use of these fields.

  • access_control_outcome
  • app_name
  • app_type
  • bytes_in
  • bytes_out
  • content_category
  • customfield_0
  • customfield_1
  • destination_address
  • event_name
  • malware_family
  • malware_variant
  • reputation_score
  • request_method
  • request_referrer
  • request_url
  • request_user_agent
  • response_code
  • source_address
  • source_username
  • timestamp_occured
  • timestamp_received
  • transport_protocol


For troubleshooting, refer to the vendor documentation: