Loading

Google Security Command Center

<div class="condensed-table">
| | |
| --- | --- |
| Version | 1.7.0 (View all) |
| Compatible Kibana version(s) | 8.13.0 or higher |
| Supported Serverless project types
What’s this? | Security
Observability |
| Subscription level
What’s this? | Basic |
| Level of support
What’s this? | Elastic |

</div>

The Google Security Command Center integration allows users to monitor finding, audit, asset, and source. Security Command Center Premium provides comprehensive threat detection for Google Cloud that includes Event Threat Detection, Container Threat Detection, and Virtual Machine Threat Detection as built-in services.

Use the Google SCC integration to collect and parse data from the Google SCC REST API (finding, asset, and source) or GCP Pub/Sub (finding, asset, and audit). Then visualize that data through search, correlation, and visualization within Elastic Security.

The Google SCC integration collects four types of data: finding, audit, asset, and source.

Finding is a record of assessment data like security, risk, health, or privacy, that is ingested into Security Command Center for presentation, notification, analysis, policy testing, and enforcement. For example, a cross-site scripting (XSS) vulnerability in an App Engine application is a finding.

Audit logs created by Security Command Center as part of Cloud Audit Logs.

Asset lists assets with time and resource types and returns paged results in response.

Source is an entity or a mechanism that can produce a finding. A source is like a container of findings that come from the same scanner, logger, monitor, and other tools.

This module has been tested against the latest Google SCC API version v1.

  • Elastic Agent must be installed.
  • You can install only one Elastic Agent per host.
  • Elastic Agent is required to stream data from the GCP Pub/Sub or REST API and ship the data to Elastic, where the events will then be processed via the integration’s ingest pipelines.

You have a few options for installing and managing an Elastic Agent:

With this approach, you install Elastic Agent and use Fleet in Kibana to define, configure, and manage your agents in a central location. We recommend using Fleet management because it makes the management and upgrade of your agents considerably easier.

With this approach, you install Elastic Agent and manually configure the agent locally on the system where it’s installed. You are responsible for managing and upgrading the agents. This approach is reserved for advanced users only.

You can run Elastic Agent inside a container, either with Fleet Server or standalone. Docker images for all versions of Elastic Agent are available from the Elastic Docker registry and we provide deployment manifests for running on Kubernetes.

There are some minimum requirements for running Elastic Agent and for more information, refer to the link here.

The minimum kibana.version required is 8.8.0.

  • Create Google SCC service account Steps to create.

  • Permissions required for Service Account:

    • Cloud Asset Viewer at Organization Level
    • Pub/Sub Subscriber at Project Level
    • Security Center Admin Editor at Organization Level
  • Security Command Center API and Cloud Asset API must be enabled.

This integration will make use of the following oauth2 scope:

  • https://www.googleapis.com/auth/cloud-platform

Once Service Account credentials are downloaded as a JSON file, then the integration can be setup to collect data.

If installing in GCP-Cloud Environment, No need to provide any credentials and make sure the account linked with the VM has all the required IAM permissions. Steps to Set up Application Default Credentials.

NOTE:

  • Sink destination must be Pub/Sub topic while exporting audit logs to GCP Pub/Sub.
  • Create unique Pub/Sub topic per data-stream.
  1. In Kibana go to Management > Integrations.

  2. In "Search for integrations" search bar, type Google Security Command Center.

  3. Click on the Google Security Command Center integration from the search results.

  4. Click on the Add Google Security Command Center Integration button to add the integration.

  5. While adding the integration, if you want to collect logs via Rest API, turn on the toggle and then put the following details:

    • credentials type

    • credentials JSON/file

    • parent type

    • id

    • To collect asset logs, put the following details:

      • content type

        or if you want to collect logs via GCP Pub/Sub, turn on the toggle and then put the following details:

    • credentials type

    • credentials JSON/file

    • project id

    • To collect asset, audit, or finding logs, put the following details:

      • topic
      • subscription name

This is the Asset dataset.

This is the Finding dataset.

This is the Source dataset.

This is the Audit dataset.