icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading App for Web Proxies
SHA256 checksum (app-for-web-proxies_129.tgz) 812ab9be74c8574c2684c81ca288a1f7b7f348bbc546bf4ddb2093fe0a865012 SHA256 checksum (app-for-web-proxies_128.tgz) 1a36fb73b6aa77bc6aa9e4a78ac10bf960baca1a12dcf03351d699776c05f211 SHA256 checksum (app-for-web-proxies_127.tgz) 23233adfe766c05e37a876154e5e062b62a30dc5062ca457c66e82bbd486ee3a SHA256 checksum (app-for-web-proxies_126.tgz) 7856cbfaa85a33b75b5eada489c4c15a50c536694533ccf0554a6f961c062c96 SHA256 checksum (app-for-web-proxies_125.tgz) d623fe510c6d2fbcb4706dac931a05246866e5beb246b7649a22371d302962f0 SHA256 checksum (app-for-web-proxies_124.tgz) 7af5db4fa0a0749bd8b9c269a84725ff8feaccbf9fcd5029cf4ad19a7fcfca9c SHA256 checksum (app-for-web-proxies_123.tgz) f77d36dd3029cdd5f200737057430bb0e93d5d08137ddfbe443bb691f79677e0 SHA256 checksum (app-for-web-proxies_122.tgz) 9eed9539bad6fc3a09ed154f675b6c4c25a42946d6e42f256397ccd92c55f28c SHA256 checksum (app-for-web-proxies_121.tgz) c4a412161de167661af8e249af67abec2bbb521b753f9b61d2efc45711fc0a48
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

App for Web Proxies

Splunk Cloud
This app is NOT supported by Splunk. Please read about what that means for youhere.
Deprecation Warning!!!
This app has been deprecated. There will be no new development or bug fixes. It has been replaced by the Aplura Web Proxies App for Splunk: https://splunkbase.splunk.com/app/4231/

App for Web Proxies

Deprecation Warning!!!

This app has been deprecated. There will be no new development or bug fixes. It has been replaced by the Aplura Web Proxies App for Splunk.


In many organizations, web proxies separate users from the Web at large. User web activity can often be a good indicator of possible compromise, phishing attempts, abuse, and outdated software. This app provides Splunk dashboards, forms, and reports which can be used to explore your web proxy events, and make sense of what can often be a large volume of data.

To do this, the app relies on the Splunk Common Information Model (CIM) for Web events. This means that the app can report on any web proxy data, as long as it has been on-boarded properly, and is available through the Web data model.

A note on Splunk Data Model Acceleration and Disk Space

This app requires data model acceleration, which will use additional disk space. If you are using the Splunk App for Enterprise Security, this is already enabled, and should have been factored into your retention policies. If not, you should review the documentation on data model acceleration, how it uses disk space, and how to plan for it. This documentation can be found here: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Acceleratedatamodels#Data_model_summary_size_on_disk

A note on the Splunk Common Information Model

As mentioned above, the app uses the CIM for web events. The CIM allows you to take events from a number of sources or products, and report on them in one cohesive manner, using a common set of names for fields and event types.

Available Dashboards and Forms

These are the dashboards and forms currently present in the app:

Proxy Traffic Overview

This dashboard serves as a jumping-off point for exploring your web proxy data. It includes panels for traffic over time, categories, top talkers, and users. Clicking on panels in this dashboard will drill down to the appropriate profile page for further exploration.

User Profile

This form provides panels based on a user's activity, including source IP addresses, category history, and destinations. By focusing on a particular user, you can see browsing activity, generate a report for HR, or see where a user may have become infected.

Source Profile

This form provides panels based on source IP addresses, often the user's computer or servers. This includes activity over time, categories, users, user agents, and destinations. Use this form when you need to see what sites a particular IP has been visiting, which is useful if you find an un-authenticated session which is attempting to visit different sites.

Category Profile

This form provides panels based on a category. This includes requests over time, destinations, users, and sources. If particular categories are of concern for your organization, you can use this form to find users or systems which have visited the category.

Destination Profile

This form provides panels based on destination, which may be a hostname or IP address. This includes URLs, categories, users, and sources. Using this form allows you to see what users visited a particular site, and which URLs are popular with your users. On sites which are categorized based on different URLs, you can see all of the categories for visits to the destination.If you know of a compromised site (such as a watering hole attack), you can use this form to quickly find users and systems which may have visited it.

Policy Exceptions

This dashboard shows users going to "bad" categories, showing the categories and user activity. Note that the selection of "bad" categories, which often changes from organization to organization, can be customized by following the steps in the section titled "Customizing Categories for Policy Exceptions". Using this dashboard can highlight users which may be violating your organization's usage agreement or systems which may be compromised.

User Agents

This dashboard provides analysis of the user-agent strings present in the web proxy events. To do this, the dashboard searches use a lookup which parses the user-agent strings. There are other lookups which perform this function, but TA-user-agents is used by default. For information on customizing the lookup being used, see the section titled "Customizing user-agent lookups". Using this dashboard will help you find outdated or unauthorized browsers/software in your environment. Additionally, because some malware either modifies user-agent strings, or have their own, you may find compromised systems on your network.

Proxy Event Search

This form provides an easy way to search proxy events for particular activity.If you already know what you are looking for, this form makes it easy to generate a search that return the events you need. Don't forget that you can use the "search" icon at the bottom of the events panel to open the search in the Splunk search interface.


A simple HTML version of this document.


Splunk Versions

This app has been tested with Splunk versions 6.0.x, 6.1.x, and 6.2.x. This app should be installed on the same search head on which the web data model has been accelerated.

Splunk Common Information Model Add-on

This app depends on data models included in the Splunk Common Information Model Add-on, specifically the "Web" data model. Information on installing and using the Splunk Common Information Model Add-on can be found here: http://docs.splunk.com/Documentation/CIM/latest/User/Install. Information on configuring the acceleration on the data model can be found here: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Acceleratedatamodels#Enable_persistent_acceleration_for_a_data_model.

The Splunk Common Information Model Add-on can be downloaded from here: https://apps.splunk.com/app/1621/

This app has been tested with versions 3, 3.1, and 4.1 of the CIM add-on.

Data model Acceleration on the Web data model

In order to make the app respond and load quickly, accelerated data models are used to provide summary data. For this data to be available, the Web data model must be accelerated. Information on how to enable acceleration for the Web data model can be found here: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Managedatamodels#Enable_data_model_acceleration

User-agents Add-on

User-agent strings are very difficult to parse efficiently using regular expressions. To make this easier and faster, an external lookup is used. Be default, the TA-user-agents is used, as it requires no additional data download or internet access. TA-user-agents can be downloaded from here: https://apps.splunk.com/app/1843/

The user-agent lookup being used can be customized. See the section titled "Customizing user-agent lookups" for more information.


This app should be installed on a search head where the Web data model has been accelerated. More information on installing or upgrading Splunk apps can be found here: http://docs.splunk.com/Documentation/Splunk/latest/Admin/Wheretogetmoreapps

Note: This app will require a restart of Splunk.

Simple Installation Process

  1. Make sure the field extractions and tags on your proxy events are correct.
  2. Install the Splunk Common Information Model Add-on (skip if you are installing on an ES search head).
  3. Install the TA-user-agents Add-on.
  4. Install the App for Web Proxies. Restart Splunk.
  5. Enable accelerations on the Web data model (skip if you are installing on an ES search head).
  6. Wait for the accelerations to start. After the acceleration searches have run, you should start seeing the dashboards populate.

Customizing Categories for Policy Exceptions

Not all organizations are the same, so there is a good chance that the default "bad" categories will need to be customized to meet the needs and policies of your organization. Additionally, customizations may be required based on the type of web proxy device generating the events.

Adjusting the lookup for the vendor and product

Different web proxy vendors is different category names, so one list wouldn't cover all vendors. To enable support for different vendors, a macro named wfa_lookup is used.

Currently this app comes pre-configured with lookups for 7 different products:

  • Barracuda: barracuda_wfa
  • Bluecoat (default): bluecoat_wfa
  • Cisco WSA: cisco_wsa_wfa
  • McAfee Web Gateway: mcafee_wg_wfa
  • Palo Alto Firewalls: palo_alto_wfa
  • URLBlacklist: urlblacklist_wfa
  • Websense: websense_wfa

These lookup files can be found in $SPLUNK_HOME/etc/apps/web_proxies/lookups.

To configure the app to use the correct lookup for your data, edit the wfa_lookup macro to match the vendor from the list above. More information on editing Splunk macros can be found in the Splunk documentation: http://docs.splunk.com/Documentation/Splunk/latest/Search/Usesearchmacros.

Note: While Splunk has configuration layering for configuration files, it does not have the same layering for lookup files. This means that if you customize one of these lookup files instead of creating your own, you need to make sure to back it up before upgrading this app, as it may be overwritten.

Creating your own lookup, or customizing an existing one

Because your organizations policies may differ from what is represented in the provided lookups, or you may be using a product which is not listed above, you may wish to use your own custom lookup for Policy Exceptions. A custom lookup for Policy Exceptions should have two columns, "category" and "wfa". The category column should match the name of the category produced by your proxy device to which visits from clients are not allowed, or need to be reviewed. The second column, "wfa", should always have a value of "TRUE". You can always look at the existing lookups for an example. More information on create a lookup in Splunk can be found here: http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Addfieldsfromexternaldatasources.

Once you have created your lookup, edit the wfa_lookup macro with the name of the lookup you have created. Information on editing macros in Splunk can be found here: http://docs.splunk.com/Documentation/Splunk/latest/Search/Usesearchmacros.

Using Wildcards in category lookups

The use of wildcards for the lookup file is not configured out of the box, however, it can by copying the transforms.conf file from the /default directory to the /local directory and adjusting the configuration of the web_proxies_wfa lookup. More information can be found here: http://answers.splunk.com/answers/52580/can-we-use-wild-characters-in-lookup-table.html#answer-52581

Customizing user-agent lookups

By default, this app uses an external lookup to provide analytics on user-agent string. The default lookup used is the TA-user-agents lookup, however, this can be customized to use another lookup which may be more accurate or provide more fields for customizing the dashboard.

To customize the lookup, download and installed the other lookup. Copy the
macros.conf file from the /default directory of the web_proxies app to a web_proxies/local directory (which you may need to create). Edit the macros.conf file, and edit the user_agent_lookup macro to be the name of the custom lookup, and then edit the ua_family_field to match the high-level product name (for example "IE" or "Firefox"). The use of the macros expect that the field being used for the lookup will be the CIM-compliant http_user_agent. If the lookup is expecting something else, then the dashboard will need to be customized to match.

About support for this app

Support for this app is provided on a best-effort basis. We have released this app for free, and want to help solve issues, and add features, but we also have day-jobs.

Need help? Use the Splunk community resources! I can be found on many of them:

The git repo for this app is located here.



  • Added deprecation warning and link to replacement.


  • Fix typos in about.xml
  • added "allow_old_summaries" to tstats macros. Defaults to "true"


  • Corrected the search behind the distinct users per source on the Source Profile page (thanks, Thomas!)


  • Certification changes
  • removed linkView tags from XML views


  • Added Checkpoint lookup
  • Fixed issue with spaces in usernames
  • Adjusted Palo Alto lookup


  • Typo fix in the README.md


  • Reduced default search range to 24 hours (from 7 days) to prevent searching too much data
  • Corrected metadata (permissions) to remove the local.met
  • Added "About" page
  • Added docs section "A note on Splunk Data Model Acceleration and Disk Space"
  • Added more information about the individual forms, views, and dashboards


Initial release


Small bug fixes


Removal of OSX files for App Certification


Fixed a typo in the websense lookup for waste fraud and abuse.


Added more support into the the README for Splunk App Certification


Splunk Common Information Model


Web Proxy Categories


This app was created by David Shpritz of Aplura, LLC. http://www.aplura.com/consulting.html

Thanks to other members of the Splunk Professional Services team, as well members of the #splunk IRC on effnet http://wiki.splunk.com/Community:IRC

Icon made by Freepik from http://www.flaticon.com is licensed under CC BY 3.0.

Release Notes

Version 1.2.9
Sept. 4, 2019

Version 1.2.8
July 9, 2018

* Fix typos in about.xml
* added "allow_old_summaries" to tstats macros. Defaults to "true"

Version 1.2.7
Dec. 26, 2017

* Corrected the search behind the distinct users per source on the Source Profile page (thanks, Thomas!)

Version 1.2.6
Jan. 27, 2017

* Certification changes
* removed linkView tags from XML views

Version 1.2.5
Nov. 23, 2016

* Added Checkpoint lookup
* Fixed issue with spaces in usernames
* Adjusted Palo Alto lookup

Version 1.2.4
June 28, 2016

Added more support into the the README for Splunk App Certification

Version 1.2.3
May 21, 2015

Fixed a typo in the websense lookup for waste fraud and abuse.

Version 1.2.2
May 14, 2015

Removed files for app certification.

Version 1.2.1
Jan. 20, 2015

Initial Public Version


Subscribe Share

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
Splunk, Splunk>,Turn Data Into Doing, Data-to-Everything, and D2E are trademarks or registered trademarks of Splunk Inc. in the United States and other countries. All other brand names,product names,or trademarks belong to their respective owners.