Google Cloud Platform Integration Guideπ
The following instructions are for configuring an integration of Google Cloud Platform (GCP) to facilitate log ingestion into Secureworks® Taegis™ XDR. XDR receives logs from GCP via the Pub/Sub messaging service.
Supported Google Cloud Platform Log Typesπ
-
- Admin Activity
- Data Access
- System Event
- Policy Denied
- GKE Dataplane V2
- Security Command Center Findings
Before You Beginπ
Ensure the following prerequisites are met before proceeding:
- An active Google Cloud account with an administrator role
- A Google Cloud Project
Important
This guide assumes these prerequisite steps are complete before beginning setup.
Data Provided from Integrationsπ
Normalized Data | Out-of-the-Box Detections | Vendor-Specific Detections | |
---|---|---|---|
Google Cloud Platform | CloudAudit | Netflow | Thirdparty |
Note
XDR detectors are not guaranteed to be triggered, even if a data source's logs are normalized to a schema associated with a given detector. However, you can create Custom Alert Rules to generate alerts based on normalized data from a data source.
Configure Log Forwarding Using the GCP Web Interfaceπ
Create Pub/Sub Topicπ
-
Navigate to Pub/Sub > Topics and select Create Topic.
-
Enter a Topic ID, then select Create.
Create Pub/Sub Subscriptionπ
-
Navigate to Pub/Sub > Subscriptions and select Create Subscription.
-
Enter a Subscription ID and select the topic created in Step 2.
-
Set the Acknowledgement deadline to 300 seconds and select Create.
Create Sinkπ
Tip
To collect organization- and folder-level logs, follow the vendor documentation to create aggregated sinks.
-
Navigate to Logging > Log router and select Create Sink.
-
From Sink details, enter a Sink name and description, then select Next.
-
From Sink destination, select Cloud Pub/Sub topic as the sink service, then select the Pub/Sub topic created in Step 2.
Select Sink Service Type and Pub/Sub Topic Note
See Select Logs to Send to XDR to create inclusion filters that determine which logs are sent to the sink.
-
Select Create sink.
Create a Service Account with Permissions to Read from the Pub/Sub Topicπ
-
Navigate to IAM & Admin > Service Accounts and select Create Service Account.
-
Enter a Service account name and description. Copy the Service account ID email address for use in a subsequent step and select Done.
-
Navigate to Pub/Sub > Subscriptions and select Edit for the subscription created in Step 5.
-
Select Add Principal.
-
Enter the service account email copied in Step 11 in the New principals field, and then select the Pub/Sub Subscriber Role.
-
Select Save.
Grant Monitoring Permission for the Service Accountπ
Create a Custom Role on GCPπ
-
Navigate to IAM & Admin > Roles. Click on Create Role.
-
Fill in the required details:
- Title (any descriptive string)
- ID (any descriptive string)
-
Select General Availability as the Role launch stage
-
Select Add Permissions.
-
Select the monitoring.timeSeries.list permission from the list of permissions.
-
Click the Add button.
-
Click the Create button to complete creation of the Role.
Add the Custom Role to the Service Accountπ
Note
Customers with an existing GCP integration do not need to generate a new service account and key for the service account. The custom role can be granted to an existing service account.
-
Navigate to IAM & Admin > IAM.
-
Click on Grant Access.
-
In the New principals text box, enter the service account email created previously in the Create a Service Account with Permissions to Read from the Pub/Sub Topic section.
Click the Role drop-down and select βCustomβ and then select the custom role created in the above step.
-
Click Save.
Create a Service Account Keyπ
-
Open the Service account created in the preceding section and navigate to the Keys tab.
-
Select Add Key, choose the JSON type, and then select Create. Save the key in a secure location for use in Step 30.
Complete the Integration in XDRπ
-
Log in to XDR and navigate to Integrations → Cloud APIs.
-
Select Add an Integration from the top of the page.
-
From the Optimized tab, select Google Cloud and enter the following in the configuration panel:
- Taegis Integration Name — Any user-friendly name to uniquely identify this integration
- Project ID — The GCP Project ID
- Subscription ID — The GCP Subscription ID
-
Upload the JSON key generated in Step 27
Select Logs to Send to XDRπ
Reference the Google Cloud resource hierarchy to form the log inclusion filters.
To select the logs to be sent to XDR, refer to the Create Sink section and update the inclusion filter using the following Cloud Audit Logs, VPC Flow Logs, Google Kubernetes Engine (GKE) Dataplane V2, and Security Command Center Findings sections.
Cloud Audit Logsπ
For more information on Cloud Audit Logs, see the Google documentation.
Configurationπ
-
In the Google Cloud console, navigate to IAM & Admin > Audit Logs. Select the services for which Data Access audit logs should be enabled.
-
Create an inclusion filter to determine which logs are sent to the Pub/Sub topic. Refer to the following table to assist in the building of the inclusion filter for Cloud Audit logs.
Admin Activity Data Access System Event Policy Denied Projects projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Factivity
projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Fdata_access
projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Fsystem_event
projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Fpolicy
Folders folders/FOLDER_ID/logs/cloudaudit.googleapis.com%2Factivity
folders/FOLDER_ID/logs/cloudaudit.googleapis.com%2Fdata_access
folders/FOLDER_ID/logs/cloudaudit.googleapis.com%2Fsystem_event
folders/FOLDER_ID/logs/cloudaudit.googleapis.com%2Fpolicy
Organization organizations/ORGANIZATION_ID/logs/cloudaudit.googleapis.com%2Factivity
organizations/ORGANIZATION_ID/logs/cloudaudit.googleapis.com%2Fdata_access
organizations/ORGANIZATION_ID/logs/cloudaudit.googleapis.com%2Fsystem_event
organizations/ORGANIZATION_ID/logs/cloudaudit.googleapis.com%2Fpolicy
VPC Flow Logsπ
For more information on VPC Flow Logs, see the Google documentation.
Considerationsπ
-
VPC Flow logs can be enabled/disabled on a subnet level.
-
When enabled on a subnet, logs will be collected for all the virtual machines within that subnet.
-
Both the inbound and outbound network traffic will be sampled for log generation for TCP, UDP, ICMP, ESP, and GRE protocols. To learn more about sampling, see the Google documentation.
Configurationπ
-
In the Google Cloud console, navigate to VPC Network > VPC Networks, select the network for which you would like to enable VPC Flow Logs, and then select the Subnets tab.
-
On the subnet for which VPC Flow Logs are to be enabled, enter Edit mode. Under the Flow Logs section, select On.
-
To route Flow Logs to the Log Router Sink created in the Create Sink section, edit the Sink and then update the Inclusion Filter.
Example Inclusion Filter:
logName="projects/gcp-dataflow-poc/logs/compute.googleapis.com%2Fvpc_flows"
Google Kubernetes Engine (GKE) Dataplane V2π
For more information on GKE Dataplane V2, see the Google documentation.
Configurationπ
-
Refer to the Google documentation to create a GKE cluster.
Important
GKE Dataplane V2 can only be enabled when creating a new cluster.
-
Refer to the Google documentation to enable network policy logging.
-
To route Flow Logs to the Log Router Sink created in the Create Sink section, edit the Sink and then update the Inclusion Filter.
Example Inclusion Filter:
logName="projects/gcp-dataflow-poc/logs/policy-action"
Security Command Center Findingsπ
For more information on Security Command Center, see the Google documentation.
Configurationπ
- Security Command Center can be activated at the Organization and Project levels.
Organization Levelπ
Refer to the Google documentation to activate Security Command Center for an organization.
Project Levelπ
Refer to the Google documentation to activate Security Command Center for a project.
-
In the Google Cloud console, navigate to Security > Security Command Center > Overview and select Edit Settings.
-
Select the Continuous exports tab.
-
Select Create Pub/Sub Export. Enter a user-friendly name and then select the Pub/Sub topic created in the Create Pub/Sub Topic section.
-
Select Save.