A logistics enterprise needs to automatically identify misconfigurations���such as open network firewall rules and publicly accessible Cloud Storage buckets—across all projects in its Google Cloud organization. Furthermore, the compliance team must view administrative audit logs and security findings while strictly adhering to the principle of least privilege. Which architecture and access management strategy satisfies these security requirements?
- Enable Security Command Center Security Health Analytics at the organization level, and grant the compliance team the Security Center Findings Viewer (roles/securitycenter.findingsViewer) and Logs Viewer (roles/logging.viewer) predefined roles.Answer
- BEnable Security Command Center across individual projects and grant the compliance team the primitive Owner role (roles/owner) across all projects so they have full visibility into security findings and audit logs.
- CConfigure Cloud Audit Logs with custom filters and rely exclusively on IAM read permissions to ensure audit log contents cannot be exfiltrated to external Cloud Storage buckets outside the organization.
- DCreate a service account for automated security monitoring and assign it the Service Account Admin role (roles/iam.serviceAccountAdmin) to grant it sufficient permissions to read Security Command Center assets.
Answer
The correct strategy is to enable Security Command Center Security Health Analytics at the organization level and grant the compliance team the Security Center Findings Viewer and Logs Viewer roles.
Enabling Security Command Center Security Health Analytics at the organization level provides automated detection of vulnerabilities such as publicly exposed buckets and open firewalls across all project environments. Combining the Security Center Findings Viewer role with the Logs Viewer role provides the compliance team with precise, read-only access to audit logs and security findings in alignment with least-privilege security principles.
Step-by-Step Solution
Key Concept
Centralized Security Logging and Security Command Center Governance