Try in Splunk Security Cloud


The analytic is built to identify threats blocked by the Zscaler proxy based on behavior analysis. It filters web proxy logs for entries where actions are blocked and threat names and classes are specified. The search further refines the results to include only those with reasons related to "block". It then aggregates the count, providing a clear view of the threat landscape as handled by the behavior analysis proxy.

  • Type: Anomaly
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2023-10-31
  • Author: Rod Soto, Gowthamaraj Rajendran, Splunk
  • ID: 289ad59f-8939-4331-b805-f2bd51d36fb8




ID Technique Tactic
T1566 Phishing Initial Access
Kill Chain Phase
  • Delivery
  • DE.AE
  • CIS 10
`zscaler_proxy` action=blocked threatname!="None" threatclass="Behavior Analysis" 
| stats count min(_time) as firstTime max(_time) as lastTime by action deviceowner user threatname url src dest 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `zscaler_behavior_analysis_threat_blocked_filter`


The SPL above uses the following Macros:

:information_source: zscaler_behavior_analysis_threat_blocked_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • action
  • threatname
  • deviceowner
  • user
  • urlcategory
  • url
  • dest
  • dest_ip
  • action

How To Implement

You must install the latest version of Zscaler Add-on from Splunkbase. You must be ingesting Zscaler events into your Splunk environment through an ingester. This analytic was written to be used with the "zscalernss-web" sourcetype leveraging the Zscaler proxy data. This enables the integration with Splunk Enterprise Security. Security teams are encouraged to adjust the detection parameters, ensuring the detection is tailored to their specific environment.

Known False Positives

False positives are limited to Zscalar configuration.

Associated Analytic Story


Risk Score Impact Confidence Message
8.0 10 80 Potential Adware Behavior Analysis Threat from dest -[$dest$] on $src$ for user-[$user$].

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 1