A enterprise healthcare company operating on Google Cloud needs to establish a centralized security auditing and log monitoring architecture across all projects under its organization. The compliance policy mandates that all read and write operations on sensitive patient data stored in Cloud Storage must be logged and monitored for suspicious activity, while maintaining strict adherence to the principle of least privilege. Which TWO architectural recommendations should a Cloud Architect make to fulfill these requirements?
- Enable Data Access audit logs (DATA_READ and DATA_WRITE) for Cloud Storage at the GCP Organization resource level.Cevap
- BGrant the primitive Owner role (roles/owner) to the centralized Security Operations Center service account to ensure unrestricted read access across all logs and Security Command Center findings.
- Configure an organization-level aggregated log sink to route audit logs to a centralized Pub/Sub topic or BigQuery dataset.Cevap
- DRely exclusively on IAM roles and Data Access audit logging to prevent authorized internal users from exfiltrating stored log data to external Cloud Storage buckets.
Cevap
The Cloud Architect should recommend enabling Data Access audit logs (DATA_READ and DATA_WRITE) for Cloud Storage at the organization level and configuring an organization-level aggregated log sink to route audit logs to a centralized BigQuery dataset or Pub/Sub topic.
Enabling Data Access audit logs (DATA_READ and DATA_WRITE) for Cloud Storage at the organization level ensures that read and write operations on storage buckets across all projects are captured, as Data Access logs are not active by default for Cloud Storage. Additionally, setting up an organization-level aggregated log sink allows seamless collection and centralization of audit log entries into BigQuery or Pub/Sub for automated threat detection and compliance analysis.
Adım Adım Çözüm
Anahtar Kavram
Centralized Security Audit Logging and Data Access Control