An enterprise organization operates a multi-folder Google Cloud resource hierarchy. To comply with security governance, the organization must aggregate all Admin Activity and Data Access audit logs across all current and future projects in real time into an external SIEM system, while enabling centralized, agentless threat detection across all workloads. Which solution meets these requirements?
- Create an organization-level Cloud Logging aggregated sink routing logs to a Pub/Sub topic connected to the SIEM, and enable Security Command Center Premium with Event Threat Detection.Answer
- BGrant the Owner primitive IAM role to a central service account across all projects to pull logs via the Logging API, and rely on standard Cloud Monitoring metric thresholds for threat detection.
- CConfigure Data Access audit logs in each project, relying solely on IAM permission boundaries to prevent unauthorized data exfiltration to external Cloud Storage buckets.
- DRequire application teams to export audit logs to Cloud Storage encrypted with Customer-Supplied Encryption Keys (CSEK), and schedule batch transfers using Storage Transfer Service.
Answer
Create an organization-level Cloud Logging aggregated sink routing logs to a Pub/Sub topic connected to the SIEM, and enable Security Command Center Premium with Event Threat Detection.
Creating an aggregated log sink at the Google Cloud Organization level ensures all audit logs across all present and future projects within the resource hierarchy are centralized. Exporting these logs to a Pub/Sub topic allows real-time ingestion by an external SIEM system. Combining this with Security Command Center Premium Event Threat Detection enables agentless, real-time threat monitoring directly from audit log streams.
Step-by-Step Solution
Key Concept
Centralized Log Aggregation and Agentless Threat Detection using Cloud Logging and Security Command Center