QuestionQ126

Data management

You must ingest audit logs from your organization’s entire Google Cloud environment into Google Security Operations (SecOps). The ingestion must include Cloud NAT logs for workloads in a designated folder, while minimizing integration complexity. Google Cloud data ingestion into Google SecOps has already been enabled. What should you do next?

  • A Create a custom filter to export the folder-level Cloud NAT logs.
  • B Create a custom filter to export the project-level Cloud NAT logs for each project in the environment folder.
  • C Configure an aggregated log sink at the folder level, and route the Cloud NAT logs to Pub/Sub. Enable the Pub/Sub connector for Google SecOps.
  • D Configure an aggregated log sink at the organization level, and route the Cloud NAT logs to a Cloud Storage bucket. Configure the Cloud Storage connector for Google SecOps.
Explanation

Google SecOps direct ingestion supports Cloud NAT logs through the log_id("compute.googleapis.com/nat_flows") export filter. A custom export filter can be scoped to a folder, allowing the required Cloud NAT telemetry to be sent directly to SecOps without creating an intermediate Pub/Sub or Cloud Storage integration. Ingest Google Cloud logs

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!