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 SCC Add-on For Splunk
SHA256 checksum (google-scc-add-on-for-splunk_100.tgz) f5253c8ed00522b85b5d3d0f40f534fd7af867034ac4c2b074c61bbfb6c386dc
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

splunk

Google SCC Add-on For Splunk

Splunk Cloud
This app is NOT supported by Splunk. Please read about what that means for you here.
Overview
Details
The Add-on typically imports and enriches data from Google SCC SDK, creating a rich data set ready for direct analysis or use in an App. The GoogleSCC Add-on for Splunk will provide the below functionalities:
- Collect sources data, findings data, assets data and audit logs from Google SCC SDK and store in Splunk indexes.
- Categorize the data in different sourcetypes.
- Parse the data and extract important fields

Splunk Technology Add-on for GoogleSCC

OVERVIEW

  • The Add-on typically imports and enriches data from Google SCC SDK, creating a rich data set ready for direct analysis or use in an App. The GoogleSCC Add-on for Splunk will provide the below functionalities:

    • Collect sources data, findings data, assets data and audit logs from Google SCC SDK and store in Splunk indexes.
    • Categorize the data in different sourcetypes.
    • Parse the data and extract important fields
  • Author - Google, Inc.

  • Version - 1.0.0
  • Prerequisites:
    • If installing Add-on in a Non-Cloud Environment, Users need to provide Service Account JSON which has the IAM permissions to configure the account.
    • If installing Add-on in a Non-GCP-Cloud (AWS, Azure) Environment, Users need to provide Workload Identity Federation Credentials JSON and make sure the account linked with the VM has all the IAM permissions.
    • If installing Add-on in GCP-Cloud Environment, Make sure the Service account linked with the VM has all the IAM permissions.
    • Google SCC Organization Id is required for account configuration.
    • Google SCC Project Id and Subscription Id for data collection.
  • Compatible with:
    • Splunk Enterprise version: 8.2.X, 8.1.X
    • OS: Linux, Windows
    • Browser: Chrome, Firefox

Permission For Service Account

For CAI creating Feed and fetching data of Assets

  • Cloud Asset Owner (roles/cloudasset.owner)

For SCC fetching data using api and creating Notification config

  • Organization Viewer (on organization level)
  • Security Centre Admin Viewer (on organization level)
  • Security Center Notification Configurations Editor (roles/securitycenter.notificationConfigEditor)

RECOMMENDED SYSTEM CONFIGURATION

TOPOLOGY AND SETTING UP SPLUNK ENVIRONMENT

This Add-On can be set up in two ways:

  1. Standalone Mode:
    • Install the Add-on app on a single machine. This single machine would serve as a Search Head + Indexer + Heavy forwarder for this setup.
  2. Distributed Environment:
    • Install Add-on on search head and Heavy forwarder (for REST API).
    • Add-on resides on search head machine need not require any configuration here.
    • Add-on needs to be installed and configured on the Heavy forwarder system.
    • Execute the following command on Heavy forwarder to forward the collected data to the indexer.
      $SPLUNK_HOME/bin/splunk add forward-server <indexer_ip_address>:9997
    • On the Indexer machine, enable event listening on port 9997 (recommended by Splunk).
    • Add-on needs to be installed on search head for CIM mapping

INSTALLATION

Follow the below-listed steps to install an Add-on from the bundle:

  • Download the App package.
  • From the UI navigate to Apps->Manage Apps.
  • In the top right corner select Install app from file.
  • Select Choose File and select the App package.
  • Select Upload and follow the prompts.

OR

  • Directly from the Find More Apps section provided in Splunk Home Dashboard.

CONFIGURATION

  • From the Splunk Home Page, click on GoogleSCC Add-on for Splunk and navigate to the Configuration section.
  • In the Google Account tab, Provide Service Account JSON of Google SCC (On Non-Cloud environment), Provide Credentials configuration (On AWS, Azure cloud environment), Organization Id and click on Save to save the configuration.
  • If all the details are correct, an Account is created.
  • To use a proxy as part of the connection to Google SCC, go to the Proxy tab in the Configuration section and provide the required details. Don't forget to check the Enable option.
  • To configure the Log Level, go to the Logging tab.
  • Now go to the Input section for creating modular input.
  • Click on the Create New Input button to configure a new Input.

GoogleSCC Sources Input

  • Enter the required details like:
    • Name (To uniquely identify input in Splunk),
    • Interval (Minimum and Default Value is 300s and Maximum Value is 900s),
    • Index
  • click on Add to save the configuration.
  • If all the details are correct, Input is created.
  • To manage the Modular Inputs, navigate to the Inputs section.
  • User can edit, delete, disable/enable and clone Modular Input by selecting specific Action.

GoogleSCC Findings Input

  • Enter the required details like:
    • Name (To uniquely identify inputs in Splunk),
    • Interval (Minimum and Default Value is 300s and Maximum Value is 900s),
    • Index,
    • Project Id,
    • Findings Subscription Id (created on GCP under your project),
    • Maximum Fetching (maximum fetch limit to pull findings from GoogleSCC api, Minimum and Default Value is 500 and Maximum Value is 5000)
  • Click on Add to save the configuration.
  • If User has already configured account, Project Id field will be automatically fetched from Service Account on Non-cloud and GCP instances.
  • If all the details are correct, Input is created.
  • To manage the Modular Inputs, navigate to the Inputs section.
  • User can edit, delete, disable/enable and clone Modular Input by selecting specific Action.

GoogleSCC Assets Input

  • Enter the required details like:
    • Name (To uniquely identify inputs in Splunk),
    • Interval (Minimum and Default Value is 300s and Maximum Value is 900s),
    • Index,
    • Project Id,
    • Assets Subscription Id (created on GCP under your project),
    • Maximum Fetching (maximum fetch limit to pull findings from GoogleSCC api, Minimum and Default Value is 500 and Maximum Value is 5000)
  • Click on Add to save the configuration.
  • If User has already configured account, Project Id field will be automatically fetched from Service Account on Non-cloud and GCP instances.
  • If all the details are correct, Input is created.
  • To manage the Modular Inputs, navigate to the Inputs section.
  • User can edit, delete, disable/enable and clone Modular Input by selecting specific Action.

  • NOTE : Project Id will be considered only while fetching data from pubsub.

GoogleSCC Audit Logs Input

  • Enter the required details like:
    • Name (To uniquely identify inputs in Splunk),
    • Interval (Minimum and Default Value is 300s and Maximum Value is 900s),
    • Index,
    • Project Id,
    • Audit Logs Subscription Id (created on GCP under your project),
    • Maximum Fetching (maximum fetch limit to pull findings from GoogleSCC api, Minimum and Default Value is 500 and Maximum Value is 5000)
  • Click on Add to save the configuration.
  • If User has already configured account, Project Id field will be automatically fetched from Service Account on Non-cloud and GCP instances.
  • If all the details are correct, Input is created.
  • To manage the Modular Inputs, navigate to the Inputs section.
  • User can edit, delete, disable/enable and clone Modular Input by selecting specific Action.

TROUBLESHOOTING

The input or configuration page is not loading.

  • Check log file for possible errors/warnings: $SPLUNK_HOME/var/log/splunk/splunkd.log

Data is not getting collected in Splunk

  • Check the log file related to data collection is generated under $SPLUNK_HOME/var/log/TA_GoogleSCC/ta_googlescc_<input>.log.
  • If there is credential related error in the log then reconfigure the creds.
  • To get the detailed logs, in the Splunk UI, navigate to GoogleSCC Add-on For Splunk. Click on Configuration and go to the Logging tab. Select the Log level to DEBUG.
  • Disable/Enable the input to recollect the data.
  • Check the logs. They will be more verbose and will give the user insights on data collection.
  • Check by pulling data to your subscription id under your project on GCP. (In case of assets, findings and audit logs data).

Unable to detect GCP, AWS or Azure cloud instances in the Add-on UI

  • If the Add-on is installed on of AWS or Azure instances and UI is not able to auto detect the instance make sure that $SPLUNK_HOME/etc/apps/TA_GoogleSCC/local/ta_googlescc_settings.conf is properly configured with following values and Splunk is restarted after the changes.
[additional_parameters]
scheme = http
  • Make sure that the KV Store is enabled on the Splunk. reference

Events are mismatching of assets and findings

  • Make sure that you have entered the same project id while configuring the assets and findings input.

UNINSTALL ADD-ON

  • To uninstall add-on, user can follow below steps:
    • SSH to the Splunk instance -> Go to folder apps($SPLUNK_HOME/etc/apps) -> Remove the TA_GoogleSCC folder from apps directory -> Restart Splunk

COPYRIGHT INFORMATION

(C) 2022 Google

SUPPORT

RELEASE NOTES

Version 1.0.0

  • Added support for Data Collection of Sources, Findings, Assets and Audit logs.
  • Added support of CIM v5.0.0 for Audit logs events.
  • Added support for Data Collection on cloud instances (GCP, AWS, Azure).

Binary file declaration

  • google_auth - This binary file is provided along with google module and source code for the same can be found at https://pypi.org/
  • googleapis_common_protos - This binary file is provided along with google module and source code for the same can be found at https://pypi.org/
  • google_api_python_client - This binary file is provided along with google module and source code for the same can be found at https://pypi.org/

Release Notes

Version 1.0.0
May 5, 2022
  • Provided data collection support for Audit logs
  • CIM Mapping for Audit logs
  • Supported service account json from the GCP instance
  • Supported short lived token (Workload Identity federation)

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.