An application developer requires access to retrieve secret payloads stored in Secret Manager within project `proj-backend-services` to perform local integration testing. The security team mandates that access must adhere strictly to the Principle of Least Privilege without granting unnecessary permissions or broader hierarchy access. Which IAM role assignment should be granted to the developer?
- Grant the Secret Manager Secret Accessor role (`roles/secretmanager.secretAccessor`) on project `proj-backend-services`.Cevap
- BGrant the Editor primitive role (`roles/editor`) on project `proj-backend-services`.
- CGrant the Secret Manager Secret Accessor role (`roles/secretmanager.secretAccessor`) at the parent Organization level.
- DGrant the Viewer primitive role (`roles/viewer`) at the parent Folder level containing project `proj-backend-services`.
Cevap
Grant the Secret Manager Secret Accessor role (`roles/secretmanager.secretAccessor`) on project `proj-backend-services`.
The Secret Manager Secret Accessor role (`roles/secretmanager.secretAccessor`) bound directly to project `proj-backend-services` provides the exact permission needed (`secretmanager.versions.access`) to read secret payloads without granting unnecessary administrative permissions or expanding access to other projects.
Adım Adım Çözüm
Anahtar Kavram
Applying Least Privilege using Predefined IAM Roles at Project Scope