Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/17 of 83

2.2Ensure that sinks are configured for all log entries

Control family: Logging and Monitoring

Control description

It is recommended to create a sink that will export copies of all the log entries. This can help aggregate logs from multiple projects and export them to a Security Information and Event Management (SIEM).

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Logs kept only in their own project can be deleted along with it, and are scattered when you need them. A sink sends a copy of every log entry to a place you choose: a central log bucket, Cloud Storage, BigQuery or Pub/Sub for a SIEM. An organization-level sink covers every project, including new ones.

Before you start

The same on every cloud, before the steps in the tabs.

  • Decide where exported logs go (a central logging project), which destination fits (log bucket, Cloud Storage, BigQuery or a SIEM through Pub/Sub) and who may read them.
  • Set how long exported logs are kept, to match your logging standard.

Evidence

  • The logging standard: destination, retention and readers

On Google Cloud the tasks create an aggregated sink in Log Router that exports every entry, then watch with Security Command Center.

Task 1Export every log entry with a sink

  1. Sign in to the Google Cloud console at console.cloud.google.com and pick the organization in the project picker (or a project, for a project-level sink).
  2. Open Logging > Log Router and choose Create sink.
  3. Name the sink and choose its destination, such as a Cloud Storage bucket in a dedicated logging project.
  4. At organization level, select the option to include logs from all child resources.
  5. Leave the inclusion and exclusion filters empty, so every entry is exported.
  6. Choose Create sink, then grant the sink's writer identity permission to write to the destination.
  7. Check it: new log files or rows appear at the destination within an hour.

Task 2Keep it checked with the Security Health Analytics finding LOG_NOT_EXPORTED

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category LOG_NOT_EXPORTED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and create a sink for the resource it names.
  4. Check it: after the next Security Health Analytics scan, no active LOG_NOT_EXPORTED finding remains.

Evidence

  • The Log Router sink, with no filter and its destination
  • Recent log entries at the destination
  • Security Command Center, with no active LOG_NOT_EXPORTED finding

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.