An enterprise is setting up access control for an automated auditing service account that must inspect resource configurations and IAM policies across all current and future projects inside a department folder. The service account needs to read security configurations without being granted access to view sensitive underlying data inside Cloud Storage buckets or modify any cloud resources. Which strategy fulfills these requirements while adhering to Google Cloud best practices and the principle of least privilege?
- Grant the Security Reviewer role (roles/securityReviewer) to the service account at the department folder level.Cevap
- BGrant the Viewer primitive role (roles/viewer) to the service account at the department folder level.
- CGrant the Service Account Admin role (roles/iam.serviceAccountAdmin) to the service account at the organization level.
- DGrant the Storage Object Viewer role (roles/storage.objectViewer) to the service account at the department folder level, relying solely on IAM to restrict exfiltration.
Cevap
Grant the Security Reviewer role (roles/securityReviewer) to the service account at the department folder level.
Granting the Security Reviewer role (`roles/securityReviewer`) at the department folder level ensures that the automated auditing service account inherits read-only permissions for security configurations and IAM policies across all child projects. It strictly avoids granting access to data payloads inside Cloud Storage buckets, perfectly satisfying least privilege and automated resource hierarchy inheritance.
Adım Adım Çözüm
Anahtar Kavram
Resource Hierarchy IAM Inheritance and Predefined Security Roles
Tahmini Süre:1m 30s