Google Cloud

Use Google Cloud data for Cortex AgentiX.

Important

This connector is only available for tenants that onboarded after July 26, 2026. For tenants that onboarded before this date, use Marketplace to access the standalone integration. For more information, see Marketplace.

This connector is available with any active Cortex XSIAM or Cortex AgentiX license.

Integrate with Google Cloud Platform services to manage identity and access, compute, storage, key management, resource management, logging, messaging, and analytics. This connector groups the GCP-IAM, Google BigQuery, Google Cloud Compute, Google Cloud Functions, Google Cloud Storage, Google Key Management Service, Google Resource Manager, Google Vision AI, Google Cloud Logging, Google Cloud Translate, Google Kubernetes Engine, Google Cloud Pub/Sub, and Looker integrations.

This connector includes the following sub-capabilities (Marketplace integrations link to PAN DEV for more information):

• GCP-IAM: Manage identity and access control for Google Cloud Platform resources.

• Google BigQuery: Integration for Google BigQuery, a data warehouse for querying and analyzing large databases.

• Google Cloud Compute: Google Compute Engine delivers virtual machines running in Google's innovative data centers and worldwide fiber network.

• Google Cloud Functions: Google Cloud Functions is an event-driven serverless compute platform.

• Google Cloud Storage: Google Cloud Storage is a RESTful online file storage web service.

• Google Key Management Service: Use the Google Key Management Service API for CryptoKey management and encrypt/decrypt functionality.

• Google Resource Manager: Google Cloud Platform Resource Manager.

• Google Vision AI

• GoogleCloudLogging: Centralize logs in a single location.

• GoogleCloudTranslate: A Google API cloud-based translation service.

• GoogleKubernetesEngine: Build and manage container-based applications in Google Cloud Platform.

• GooglePubSub: A fully-managed real-time messaging service.

• Looker: Query explores, save queries as looks, run looks, and fetch results as incidents.

To configure this connector, follow the steps outlined in the configuration wizard.