Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

About The Device

Cloud Load Balancing:
A load balancer distributes user traffic across multiple instances of your applications. By spreading the load, load balancing reduces the risk that your applications experience performance issues. Cloud Load Balancing is a fully distributed, software-defined managed service.

Cloud Armor:
Google Cloud Armor helps you protect your Google Cloud deployments from multiple types of threats, including distributed denial-of-service (DDoS) attacks and application attacks like cross-site scripting (XSS) and SQL injection (SQLi).

Device Information

 Entity

Particulars

Vendor Name

Google

Product Name

Cloud Load Balancing 
Cloud Armor

Type of Device

Cloud

Collection Method

Log Type

 Ingestion label

Preferred Logging Protocol - Format

Log Collection Method

 Cloud Load Balancing

 GCP_LOADBALANCING

JSON

C2C

Device Configuration

Prerequisite:

Before you can ingest your GCP telemetry into your Chronicle account, you must complete the following steps:

  • Contact your Chronicle representative and obtain the one-time access code you need to ingest your GCP telemetry.

  • Grant the following IAM roles required for you to access the Chronicle section:

    • Chronicle Service Admin (roles/chroniclesm.admin): IAM role for performing all activities.

    • Chronicle Service Viewer (roles/chroniclesm.viewer): IAM role to only view the state of ingestion.

    • Security Center Admin Editor (roles/securitycenter.adminEditor): Required to enable the ingestion of Cloud Asset Metadata.

Granting IAM Roles:

To grant IAM roles using Google Cloud console, complete the following steps:

  1. Log on to the Google Cloud Organization you want to connect to and navigate to the IAM screen using Products > IAM & Admin > IAM.

  2. From the IAM screen, select the user and click Edit Member.

If you are not in the Organization view of IAM, the Edit Member button is disabled and you need to navigate to the organization's IAM screen.

  1. In the Edit Permissions screen, click Add Another Role and search for Chronicle to find the IAM roles.

  2. Once you have assigned the roles, click Save.

Enabling Google Cloud data ingestion:

To enable data ingestion from your Google Cloud organization into your Chronicle account, complete the following steps:

  1. Navigate to the Chronicle page for the Google Cloud console.
    Go to the Chronicle page

  2. Enter your one-time access code in the 1-time Chronicle access code field.

  3. Check the box labeled I consent to the terms and conditions of Chronicle's usage of my Google Cloud data.

  4. Click Connect Chronicle

image-20240301-061250.png
  1. Once Google cloud connected to Chronicle, you need to enable Google Cloud Logging.

image-20240301-062409.png
  1. Once Google Cloud Logging enabled. You need to create a Export Filter to only send Google Cloud Load Balancing logs only. Please follow below page to create Export Filter and send Google Cloud Load Balancing logs to Chronicle.
    Ingest Google Cloud data to Chronicle

  2. Once you complete with Export Filter, click on Save.

Integration Parameters

The integration feed details are not required as service is sending data directly to the chronicle. Please refer device configuration.

  • No labels