An enterprise architecture team needs to aggregate Cloud Audit Logs across all Google Cloud projects within an organization folder into a central BigQuery dataset for long-term security analysis, while also streaming high-severity security events to a central Pub/Sub topic for real-time alerting. The solution must minimize administrative overhead and avoid creating individual log sinks in every project. Which Cloud Logging architecture should the team implement?
- Create an aggregated Log Router sink at the organization folder level using an inclusion filter for Cloud Audit Logs, set BigQuery and Pub/Sub as targets, and grant the sink's writer identity appropriate access on the destinations.Cevap
- BApply a broad Log Router exclusion filter at the folder level to exclude audit logs from log buckets, assuming excluded log entries are automatically redirected to BigQuery and Pub/Sub.
- CAssign the primitive Owner role to a central service account across all projects to run custom scripts that periodically export log entries into BigQuery and Pub/Sub.
- DRely strictly on project-level IAM permission inheritance without configuring Log Router sinks or VPC Service Controls, assuming IAM grants automatically consolidate logs into a central dataset.
Cevap
Create an aggregated Log Router sink at the organization folder level using an inclusion filter for Cloud Audit Logs, set BigQuery and Pub/Sub as targets, and grant the sink's writer identity appropriate access on the destinations.
Creating an aggregated sink at the folder level automatically collects logs from all child projects under that folder. By specifying inclusion filters for Cloud Audit Logs and setting BigQuery and Pub/Sub as sink destinations, logs are securely routed in real time without per-project configuration.
Adım Adım Çözüm
Anahtar Kavram
Aggregated Log Router Sinks
Tahmini Süre:1m 30s