Set up Broker VM on Google Cloud Platform (GCP) - Administrator Guide - Cortex XSIAM - Cortex - Security Operations

Cortex XSIAM Documentation

Product
Cortex XSIAM
Creation date
2024-03-06
Last date published
2024-06-25
Category
Administrator Guide
Abstract

Learn more about how to set up your Cortex XSIAM Broker VM on Google Cloud Platform.

You can deploy the Broker VM on Google Cloud Platform. The Broker VM allows communication with external services through the installation and setup of applets such as the Syslog collector applet.

To set up the Broker VM on the Google Cloud Platform, install the VMDK image provided in Cortex XSIAM.

Danger

  • Download a Cortex XSIAM Broker VM VMDK image. For more information, see the virtual machine compatability requirements in Set up and configure Broker VM.

  • To complete the set up, you must have G Cloud installed and have an authenticated user account.

Perform the following procedures in the order listed below.

From G Cloud, create a Google Cloud Storage bucket to store the Broker VM image.

  1. Create a project in GCP and enable Google Cloud Storage, for example, brokers-project. Make sure you have defined a default network.

  2. Create a bucket to store the image, such as broker-vms.

Open a command prompt and run the following:

gcloud config set project <project-name>

Upload the VMDK image to the bucket, run the following:

gsutil cp </path/to/broker.vmdk> gs://<bucket-name>

You can import the GCP image using either G Cloud CLI or Google Cloud console.

Note

The import tool uses Cloud Build API, which must be enabled in your project. For the import to work, Cloud Build service account must have compute.admin and iam.serviceAccountUser roles. When using the Google Cloud console to import the image, you will be prompted to add these permissions automatically.

When the Google Compute completes the image creation, create a new instance.

  1. From the Google Cloud Platform, select Compute EngineVM instances.

  2. Click Create instance.

  3. In the Boot disk option, choose Custom images and select the image you created.

  4. Set up the instance according to your needs.

    If you are using the Broker VM to facilitate only Agent Proxy, use e2-startdard-2. If you are using the Broker VM for multiple applets, use e2-standard-4.

  1. From the Google Cloud menu, select VPC networkFirewall, and click CREATE FIREWALL RULE.

  2. Set the following parameters for the rule:

    • Name: Name of the rule.

    • Network: Select the applicable network where the Broker VM resides.

    • Direction of traffic: Select Ingress (default).

    • Targets: Select All instances in the network.

    • Source IPv4 ranges: Enter the IP network of computers that will be connecting to the Broker VM. To include all machines, enter 0.0.0.0/0.

    • TCP: Enter port 4443.

  3. Click CREATE.

    The rule is listed under VPC firewall rules.

  1. From the Google Cloud menu, select Compute EngineVM instances.

  2. For the specific Broker VM containing the rule, select the ellipse to display More actions, and select View network details.

  3. In the Firewall and routes details section, select the FIREWALLS tab.

  4. Verify that the firewall rule is listed.

You can now connect to the Broker VM web console using the Broker VM IP address. Connect with https over port 4443 using the format https://<ip address>:4443.