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

We are working on something new...

A Fresh New Splunkbase
We are designing a New Splunkbase to improve search and discoverability of apps. Check out our new and improved features like Categories and Collections. New Splunkbase is currently in preview mode, as it is under active development. We welcome you to navigate New Splunkbase and give us feedback.
Log4Shell Vulnerability: Information and guidance for you. Get resources.

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 Google Chrome Add-on for Splunk
SHA256 checksum (google-chrome-add-on-for-splunk_011r573454d.tgz) ba4f6603341b3db3ee2c28aea520968ab44c8e1da73907871c518aaa3105df5a SHA256 checksum (google-chrome-add-on-for-splunk_010r909c06c.tgz) 13b2d1849b290dafa7299f31935e5b4b95b7fcc1ca3a76d26643da6ae9c9af93
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

splunk

Google Chrome Add-on for Splunk

Splunk Labs
This app is NOT supported by Splunk. Please read about what that means for you here.
Overview
Details
Using the Splunk reporting connector for managed Chrome browsers, organizations can get additional visibility on the security posture of their organization's managed browser fleet. This integration between Chrome and Splunk allows IT administrators to send Chrome security events to an HTTP event collector (HEC) endpoint. Chrome administrators can select all or a subset of available Chrome audit events to send to Splunk. Examples of Chrome browser security events include malware transfer, unsafe site visits, password reuse and password change events.

Google Chrome Add-on for Splunk

Background

Using the Splunk reporting connector for managed Chrome browsers, organizations can get additional visibility on the security posture of their organization's managed browser fleet. This integration between Chrome and Splunk allows IT administrators to send Chrome security events to an HTTP event collector (HEC) endpoint. Chrome administrators can select all or a subset of available Chrome audit events to send to Splunk. Examples of Chrome browser security events include malware transfer, unsafe site visits, password reuse and password change events.

Affiliation

While this add-on is designed to integrate with Google Chrome audit data, it is not affiliated with or endorsed by Google. Similarly, usage of the Google Chrome logo in the Splunkbase listing and add-on interface is for informational purposes only.

Prerequisites

Use of this add-on requires:

Setup

Chrome

Please refer to the official Google documentation for more information on setting up Chrome Browser Cloud Management and the Splunk reporting connector.

Splunk

Install

Please target search heads when installing this Add-on. For Splunk Cloud, refer to Install apps in your Splunk Cloud deployment. For customer managed deployments, refer to the standard methods for Splunk Add-on installs as documented for a Single Server Install or a Distributed Environment Install.

Sourcetype

This add-on expects Chrome events to arrive with a sourcetype of google:chrome:json. Please use a dedicated HTTP Endpoint Collector (HEC) token which explicitly sets this sourcetype on incoming events. For more information on setting up HEC tokens and customizing HEC sourcetypes, please refer to HEC setup documentation.

Details

In order to handle event-specific field aliases, each Google Chrome event type is mapped to a child sourcetype. For events which do not match a known Chrome event, the sourcetype will remains google:chrome:json (the original sourcetype associated with the HEC token). Child sourcetypes are listed below:

  • sourcetype::google:chrome:json:password_reuse
  • sourcetype::google:chrome:json:password_changed
  • sourcetype::google:chrome:json:malware_transfer
  • sourcetype::google:chrome:json:bad_navigation
  • sourcetype::google:chrome:json:sensitive_data_transfer
  • sourcetype::google:chrome:json:unscanned_content
  • sourcetype::google:chrome:json:content_transfer

Resources

Release Notes

Version 0.1.1R573454d
May 25, 2022
  • jquery update
Version 0.1.0R909c06c
June 18, 2021

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 from Splunk, our partners and our community. Find an app 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.