An enterprise security compliance reviewer needs to inspect Cloud Audit Logs for sensitive Compute Engine operations within a Google Cloud project named core-infrastructure-prod. The reviewer currently holds the predefined Logs Viewer (roles/logging.viewer) role at the project level. While they can inspect Admin Activity audit logs, they are unable to view sensitive payload details within Data Access audit logs. Following the principle of least privilege, which action will allow the reviewer to view the Data Access audit logs?
- Grant the reviewer the Private Logs Viewer (roles/logging.privateLogViewer) role at the project level.Answer
- BGrant the reviewer the primitive Viewer (roles/viewer) role at the project level.
- CGrant the reviewer the Logs Viewer (roles/logging.viewer) role at the parent Organization level.
- DGrant the reviewer the primitive Editor (roles/editor) role at the project level.
Answer
Grant the reviewer the Private Logs Viewer (roles/logging.privateLogViewer) role at the project level.
In Google Cloud Logging, Data Access audit logs contain detailed API calls and sensitive payload data. The standard Logs Viewer (roles/logging.viewer) role allows viewing Admin Activity logs and standard logs, but access to private logs (which include Data Access audit logs) requires the Private Logs Viewer (roles/logging.privateLogViewer) role. Assigning this role follows the principle of least privilege.
Step-by-Step Solution
Key Concept
Cloud Audit Logs access control requires the Private Logs Viewer role to read Data Access logs containing sensitive metadata.