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 2 Current »

About the Device

Cloud NAT (network address translation) lets certain resources in Google Cloud create outbound connections to the internet or to other Virtual Private Cloud (VPC) networks, on-premises networks, or any other cloud provider networks. Cloud NAT supports address translation for established inbound response packets only. It does not allow unsolicited inbound connections.

Device Information

 Entity

Particulars

Vendor Name

Google

Product Name

Cloud NAT 

Type of Device

Cloud

Collection Method

Log Type

 Ingestion label

Preferred Logging Protocol - Format

Log collection method

Data Source

 Cloud NAT

 GCP_CLOUD_NAT

Prop Vendor API - JSON

 Direct Ingestion

https://cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs

Device Configuration

Before you can ingest your Google Cloud data into your Chronicle instance, 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.

To Enable 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-20240308-121656 (1).png
  1. Your Google Cloud data is now going to be sent to Chronicle.

To Export Filter Settings

By default, your Cloud Audit logs (admin activity and system event) and Cloud DNS logs are sent to your Chronicle account. However, you can customize the export filter to include or exclude specific types of logs. The export filter is based on the Google logging query language.

To define a custom filter for your logs, complete the following steps:

  1. Define your filter by creating a custom filter for your logs using the logging query language.
    The following documentation describes how to define this type of filter: Logging query language  |  Google Cloud .

  2. Navigate to Google SecOps > EXPORT FILTER SETTINGS

  3. Navigate to the Logs Explorer using the link provided on the EXPORT FILTER SETTINGS tab, copy your new query into the Query field and click Run Query to test it.

  4. Use below query to export Cloud NAT logs

log_id("compute.googleapis.com/nat_flows")
  1. Verify that the matched logs displayed in the Logs Explorer are exactly what you intend to export to Chronicle.

Complete the following steps from the Export Filter Settings tab:

  1. When the filter/query is ready, click the edit icon and paste the filter/query in the Export filter field.

  2. Click Save Custom Filter. Your new custom filter works against all new logs exported to your Google Security Operations account.

  3. You can reset the export filter to the default version by clicking Reset to Default. Be sure to save a copy of your custom filter first.

To Enable GCP Logs

  1. Under Security Tab, navigate to Detections and Controls > Google SecOps.

  1. Select the project which Cloud NAT logs you want to monitor.

  1. Enable Google Cloud Logging

Integration Parameters

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

  • No labels