Which of the following best describes the least privilege principle when assigning IAM roles in Google Cloud Platform?
Think about security risks of giving too many permissions.
The least privilege principle means giving users only the permissions they need to do their job, reducing security risks.
You have three teams: Developers, QA, and Operations. Each team needs access to different GCP resources. How should you apply the least privilege principle when assigning IAM roles?
Consider how to limit permissions to only what each team needs.
Creating custom roles tailored to each team's needs follows the least privilege principle and improves security.
What is the most likely security risk if a GCP user is assigned the roles/editor role instead of a more restrictive custom role following the least privilege principle?
Think about what permissions the Editor role grants compared to a minimal role.
The Editor role grants broad permissions that can lead to accidental or intentional harmful changes, violating least privilege.
An automated service account is used by a deployment pipeline in GCP. Which practice aligns with the least privilege principle to minimize security risks?
Consider how to limit automated account permissions to only what is necessary.
Limiting service account permissions to only what is needed reduces risk if the account is compromised.
You want to enforce least privilege by restricting a userโs access to a GCP Storage bucket only during business hours (9 AM to 5 PM). Which IAM feature allows you to implement this restriction?
Think about how to automate access restrictions based on time.
IAM Conditions allow you to add rules like time-based access restrictions, supporting least privilege dynamically.