Soru

Zorluk: OrtaViewing and Analyzing Cloud Audit Logs

A security analyst must investigate object access patterns on a sensitive Google Cloud Storage bucket. Place the steps required to grant necessary access, configure audit logging, generate test events, and analyze the resulting logs in the correct sequential order.

  1. 1Grant the security analyst the Private Logs Viewer (roles/logging.privateLogViewer) role on the project.
  2. 2Configure the project's Audit Logs policy in IAM & Admin to enable 'Data Read' Data Access audit logs for the Cloud Storage service.
  3. 3Perform a read operation on objects within the target Cloud Storage bucket.
  4. 4Execute a `gcloud logging read` command filtering for logName matching 'cloudaudit.googleapis.com/data_access' and the target bucket resource.

Cevap

The correct sequence is: 1) Grant the Private Logs Viewer role to the analyst, 2) Enable 'Data Read' Data Access audit logs for Cloud Storage under IAM & Admin Audit Logs, 3) Perform a read operation on the target bucket objects, 4) Execute the `gcloud logging read` command filtering for the data_access logName and bucket resource.
The workflow follows a logical security lifecycle: first establish least privilege permissions (Private Logs Viewer role), second activate the audit logging policy for Cloud Storage Data Read actions, third generate sample traffic by reading bucket objects, and finally retrieve the resulting Data Access audit log entries using gcloud CLI.

Adım Adım Çözüm

1
Ensure IAM access permissions are configured.
The analyst receives permissions to view private audit logs via `roles/logging.privateLogViewer`.
Standard `roles/logging.viewer` cannot view Data Access audit logs containing PII/sensitive details.
2
Enable Data Access audit logging for Google Cloud Storage.
Cloud Storage begins writing DATA_READ audit log entries.
Except for BigQuery, Data Access audit logs are disabled by default in GCP to reduce log storage costs.
3
Trigger bucket access activity.
Cloud Storage generates a `cloudaudit.googleapis.com/data_access` log entry.
Audit events are created only when operations happen after the feature configuration is active.
4
Query the generated logs via gcloud CLI.
The analyst retrieves and reviews the structured JSON audit entries.
Running a filter targeted at `logName` and `resource.type` isolates the specific Cloud Storage Data Access logs.

Anahtar Kavram

Viewing and Analyzing Cloud Audit Logs
Tahmini Süre:1m 30s
Bu soruyu puanla