Ingesting Cloud Assets from Google Cloud Platform requires a Cortex XDR Pro per TB license.
Cortex XDR provides a unified, normalized asset inventory for cloud assets in Google Cloud Platform (GCP). This capability provides deeper visibility to all the assets and superior context for incident investigation.
To receive cloud assets from GCP, you must configure the Collection Integrations settings in Cortex XDR using the Cloud Inventory data collector to configure the GCP wizard. The GCP wizard includes instructions to be completed both in GCP and the GCP wizard screens. After you set up data collection, Cortex XDR begins receiving new data from the source.
As soon as Cortex XDR begins receiving cloud assets, you can view the data in → , where All Assets and Specific Cloud Assets pages display the data in a table format.
To configure the GCP cloud assets collection in Cortex XDR.
Open the GCP wizard in Cortex XDR.
Select→ → → .
In the Cloud Inventory configuration, click Add Instance to begin a new configuration.
Click Google Cloud Platform.
Define the Configure Account screen of the wizard.
Setting the connection parameters on the right-side of the screen is dependent on certain configurations in GCP as explained below.
Select the Organization Level as either Project (default), Folder, or Organization. The Organization Level that you select changes the instructions.
Register your application for Cloud Asset API in Google Cloud Platform, Select a project where your application will be registered, and click Continue.
The Cloud Asset API is enabled.
Click Continue to open the GCP Cloud Console.
On the main menu, select the project menu.
In the window that opens, perform the following.
From the Select from menu, select the organization that you want.
The next steps to perform in Google Cloud Platform are dependent on the Organizational Level you selected in Cortex XDR - Project, Folder, or Organization.
Project or Folder Organization Level—In the table, copy one of the following IDs that you want to configure and paste it in the designated field in the Configure Account screen in Cortex XDR . The field in Cortex XDR is dependent on the Organizational Level you selected.
-Project—Contains a project icon () beside it, and the ID should be pasted in the Project ID field in Cortex XDR.
-Folder—Contains a folder icon () beside it, and the ID should be pasted in the Folder ID field in Cortex XDR.
When you are finished, click CANCEL to close the window.
Organization is the Organization Level—Select the → . In the Settings page, copy the Organization ID for the applicable organization that you want to configure and paste it in the Organization Id field in the Configure Account screen in Cortex XDR.
Select the→ → → .
You can either use an existing bucket from the list or create a new bucket. Copy the Name of the bucket and paste it in the Bucket Name field in the Configure Account screen in Cortex XDR.
Define the following remaining connection parameters in the Configure Account screen in Cortex XDR.
Bucket Directory Name—You can either leave the default directory as Exported-Assets or define a new directory name that will be created for the exported assets collected for the bucket configured in GCP.
Cortex XDR Collection Name—Specify a name for your Cortex XDR collection that is displayed underneath the Cloud Inventory configuration for this GCP collection.
Define the Account Details screen of the wizard.
Download the Terraform script. The name of the file downloaded is dependent on the Organizational Level that you configured in the Configure Account screen of the wizard.
Login to the Google Cloud Shell.
Click Continue to open the Cloud Shell Editor.
Select Open the Terraform script that you downloaded from Cortex XDR.→ , and
Use the following commands to upload the Terraform script, which you can copy from the Account Details screen in Cortex XDR using the copy icon ().
terraform init—Initializes the Terraform script. You need to wait until the initialization is complete before running the next command as indicated in the image below.