Follow the foundational configuration GCP onboarding wizard to enable audit log collection and asset discovery, and Cortex XSIAM creates a custom authentication template to be deployed in GCP.
Notice
Onboarding Google Cloud Platform (GCP) using the foundational configuration is included with Cortex XSIAM NG SIEM, Cortex XSIAM Enterprise, and Cortex XSIAM Enterprise+ licenses. For more details on the CSP onboarding tiers and licensing, see Understand CSP onboarding tiers and licensing.
This procedure describes foundational onboarding, which includes support of asset discovery and audit log collection. For the procedure describing comprehensive onboarding, see How to onboard Google Cloud Platform.
After completing the prerequisites, follow these instructions to onboard your Google Cloud Platform (GCP) environment to Cortex XSIAM.
In Cortex XSIAM, select → .
On the Data Sources & Integrations page, click + Add New.
On the Add Data Sources or Integrations page, search for Google Cloud Platform (GCP), then hover over it and click Add.
Select the scope for this cloud instance:
Organization: (Default) A collection of GCP projects that are managed centrally.
Folder: A GCP folder can contain projects, folders, or a combination of both projects and folders.
Project: A specific GCP project.
Click Show advanced settings to define the following advanced settings:
Instance Name: Enter a unique instance name or leave it empty to be automatically populated. The automatic naming convention is
GCP-or<projectID>GCP-. Cortex XSIAM does not prevent you from reusing instance names, but it is best practice to use a unique name for every cloud instance.<organizationID>Scope Modifications: Use these settings to fine-tune your GCP scope. You can modify the scope by including or excluding specific regions. Additionally, if you selected an organization or folder as the scope, you can modify the scope by including or excluding specific projects. For more details, see Apply region or account filters.
Additional Security Capabilities: Choose which security capabilities you want to benefit from. Some security capabilities are enabled by default and can be modified. Adding security capability typically requires additional cloud provider permissions. For detailed information on the permissions required, see Cloud service provider permissions.
XSIAM analytics: (Enabled by default) Analyzes your endpoint data to develop a baseline and raise Analytics and Analytics BIOC alerts when anomalies and malicious behaviors are detected.
Automation: Use automation to pre-configure a list of integrations and associated commands to automate security issue responses. Commands can be utilized individually or as part of custom playbooks for issue remediation.
Cloud Tags: Define tags and tag values to be added to any new resource created by Cortex XSIAM in GCP. Note: The
managed_by = paloaltonetworkstag is automatically added to all resources. This tag is mandatory. You cannot edit or remove this tag.Log Collection Configuration: To maximize security coverage, include the collection of audit logs (GCP Pub/Sub). This may require additional cloud service provider permissions. For detailed information on the permissions required, see Cloud service provider permissions.
Click Save. Cortex XSIAM generates a Terraform authentication template based on the settings you configured in the GCP onboarding wizard. Cortex XSIAM creates an instance in the pending state. For details on pending instances, see Lifecycle and expiration.
Click Download Terraform to download the template file and then click Close.
The Terraform authentication template is reusable and can be applied as many times as you want to create new instances with the settings you defined in the GCP onboarding wizard. The Terraform authentication template is valid for seven days from when it was created.
Next step: Deploy the Terraform authentication template in GCP.