A security compliance auditor needs to inspect Data Access audit logs in a Google Cloud project to investigate access patterns for sensitive Cloud KMS keys. The auditor currently holds the Logs Viewer (roles/logging.viewer) role at the project level, but queries in Logs Explorer return no results for Data Access logs. Following the principle of least privilege, which action should you take to enable the auditor to view these logs?
- Grant the auditor the Private Logs Viewer (roles/logging.privateLogViewer) role at the project level.Cevap
- BGrant the auditor the primitive Viewer (roles/viewer) role at the project level.
- CGrant the auditor the Private Logs Viewer (roles/logging.privateLogViewer) role at the resource log bucket level while revoking roles/logging.viewer at the project level to override parent access.
- DGrant the auditor the Owner (roles/owner) role at the parent Organization level.
Cevap
Grant the auditor the Private Logs Viewer (roles/logging.privateLogViewer) role at the project level.
In Google Cloud Observability, Data Access audit logs are restricted because they may contain sensitive user data or API metadata. While the Logs Viewer role allows reading standard system logs and Admin Activity audit logs, reading Data Access audit logs requires the Private Logs Viewer (roles/logging.privateLogViewer) role, which includes the logging.privateLogEntries.list permission.
Adım Adım Çözüm
Anahtar Kavram
Data Access Audit Logs IAM Permissions