Integrating Threat Detection with XDR in Google Cloud

Aug 03, 2021
4 minutes
54 views

Introduction

The recently announced Google Cloud IDS is a next-generation and cloud native intrusion detection service (IDS) that provides threat detection for intrusions, malware, spyware and command-and-control attacks. The native Google Cloud service – built with Palo Alto Networks threat detection technology – catches signature-based threats at the network level, gains complete Layer 7 visibility into intra- and inter-VPC application traffic, and helps you to meet compliance requirements with ease.

Until now, detecting threats in traffic between workloads within the trust boundary of a VPC has been a significant hurdle for security teams. Furthermore, taking action on those threats was even more challenging as information from hosts and endpoints was difficult to access at scale, preventing teams from quickly responding.

With the introduction of Cloud IDS, cloud network security teams finally have a native threat detection service for their Google Cloud environments. Further integration with the Google Cloud Logging service enables threat logs generated from the service to be sent to the Google Cloud Pub/Sub messaging service. Accordingly, if you use the Pub/Sub messaging service from Global Cloud, you can now send logs and data from your Google Cloud instance to Cortex XDR. This enables data and information from Google Cloud to be searchable in Cortex XDR, providing additional detail and context for threat investigations.

Cortex XDR delivers holistic protection by integrating all key security data to stop sophisticated attacks. It simplifies threat investigation by correlating logs from Cloud IDS to reveal threat casualties and timelines. This enables you to easily identify the root cause of every alert.

With the integration of this new IDS service and XDR application, you have the unique ability to perform immediate response actions from threat data. Beyond reactive behavior, you can look to the future and define indicators of compromise (IOCs), or behavior-based indicators of compromise (BIOCs) for detection and response around malicious activity.

Cortex XDR platform

 

How to configure the integration

Create a Pub/Sub topic and subscription

  1. Log in to your Google CloudGCP account.
  2. Select LoggingLogs > Logs Router.
  3. Select Create SinkCloud Pub/Sub topic and then click Next.

screenshot of how to configure the integration

 

  1. To filter only specific types of data, select the filter or desired resource. You can set a filter to select Cloud IDS threat logs.

Google cloud platform screenshot, logs explorer

 

  1. In the Edit Sink configuration, define a descriptive Sink Name.
  2. Select Sink DestinationCreate new Cloud Pub/Sub topic.
  3. Enter a descriptive Name that identifies the sink purpose for Cortex XDR, and then click Create.
  4. Choose Create Sink and then Close when finished.
  5. Select the hamburger menu in G Cloud, and then select Pub/SubTopics.
  6. Select the name of the topic you created in the previous steps. Use the filters if necessary.
  7. Create SubscriptionCreate > Subscription.
  8. Enter a unique Subscription ID.
  9. Choose Pull as the Delivery Type.
  10. Create the subscription.
  11. In the subscription details, identify and note your Subscription Name.

Create a service account and authentication key

  1. Select the hamburger menu, and then select IAM & AdminService > Accounts.
  2. Create a Service Account.
  3. Enter a Service account name and then Create.
  4. Select a role for the account: Pub/SubPub/Sub > Subscriber.
  5. Click Continue > Done.
  6. Locate the service account by name, click the Actions menu identified by the three dots in the row for the service account, and then Create Key.
  7. Select JSON as the key type, then Create, and save to your local compute.

In Cortex XDR, set up Data Collection

  1. Select Settings Configurations > Data Collection > Collection Integrations.
  2. In the Google Cloud Platform configuration, click the here link.

  1. Enter the subscription and upload the json file you created for the service account. Subscription sample: projects/<project_name>/subscriptions/<subscription_id>

Edit GCP Pub/Sub Log configuration screen shot

  1. Test the provided settings and, if successful, proceed to Enable log collection.

 

  1. Go to Menu, Investigation > Query Builder.

 

  1. Select XQL Search.

  1. Enter your query in the XQL-Query-90 box to get the logs from GCP Pub/Sub subscription. For example:

dataset = google_cloud_logging_raw 

screenshot

  1. You can further filter for more specific logs you want. For example:

dataset = google_cloud_logging_raw | filter logName = "projects/xxxxxxx/logs/ids.googleapis.com%2Fthreat"

Combining cloud threat detection inside a VPC with an integrated response solution provides a powerful option for securing additional layers of your cloud environment. This is a unique offering made possible by the joint vision, design and engineering of Google Cloud and Palo Alto Networks.

You can learn more about Google Cloud IDS and sign up for access to the preview or take a deeper look at how Cortex XDR can protect your cloud operations.

 


Subscribe to Security Operations Blogs!

Sign up to receive must-read articles, Playbooks of the Week, new feature announcements, and more.