Least privilege principle in GCP - Step-by-Step Execution

Process Flow - Least privilege principle

Start: User/Service needs access

↓

Identify minimum permissions needed

↓

Assign only those permissions

↓

User/Service performs tasks

↓

Monitor and adjust permissions if needed

↓

End

The flow shows how to give only the minimum permissions needed for a user or service to do their job, then monitor and adjust as needed.

Execution Sample

GCP

1. Create IAM role with minimal permissions
2. Assign role to user/service account
3. User tries to access resource
4. Access allowed only if permission matches

This example shows assigning a minimal IAM role and how access is granted only if permissions match.

Process Table

Step	Action	Permission Checked	Result	Reason
1	Assign role with 'storage.objects.get' permission	storage.objects.get	Role assigned	Role created with minimal needed permission
2	User tries to read storage object	storage.objects.get	Allowed	User has exact permission needed
3	User tries to delete storage object	storage.objects.delete	Denied	Permission not granted in role
4	Admin reviews permissions	N/A	Adjust if needed	Monitor and update permissions
5	User tries to write storage object	storage.objects.create	Denied	Permission not granted
6	User tries to list storage bucket	storage.buckets.list	Denied	Permission not granted
7	User tries to read storage object again	storage.objects.get	Allowed	Permission still valid

💡 Execution stops as user only has minimal permissions; denied actions show principle of least privilege in effect.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
User Permissions	None	storage.objects.get	storage.objects.get	storage.objects.get	storage.objects.get

Key Moments - 3 Insights

Why is the user denied when trying to delete a storage object?

Because the assigned role only includes 'storage.objects.get' permission, not 'storage.objects.delete', as shown in step 3 of the execution table.

Can the user list storage buckets with the assigned role?

No, the user cannot list buckets because the role does not include 'storage.buckets.list' permission, as shown in step 6.

Why is it important to monitor and adjust permissions after assignment?

Because needs may change, and monitoring ensures permissions stay minimal but sufficient, as shown in step 4 where admin reviews permissions.

Visual Quiz - 3 Questions

Look at the execution table, what permission does the user have after step 1?

A storage.objects.get

B storage.objects.delete

C storage.buckets.list

D storage.objects.create

💡 Hint

Check the 'Permission Checked' column in step 1 of the execution table.

At which step does the user get denied for trying to delete a storage object?

A Step 2

B Step 5

C Step 3

D Step 7

💡 Hint

Look at the 'Result' column for 'Denied' related to 'storage.objects.delete' permission.

If the user needed to write objects, which permission should be added?

A storage.objects.delete

B storage.objects.create

C storage.objects.get

D storage.buckets.list

💡 Hint

Refer to step 5 where 'storage.objects.create' permission is checked and denied.

Concept Snapshot

Least Privilege Principle in GCP IAM:
- Assign only the minimum permissions needed.
- Use custom roles or predefined minimal roles.
- Deny access if permission not granted.
- Monitor and adjust permissions regularly.
- Helps reduce security risks by limiting access.

Full Transcript

The least privilege principle means giving users or services only the permissions they need to do their tasks, nothing more. In GCP, this is done by creating roles with minimal permissions and assigning them. When a user tries to do an action, GCP checks if their role has the needed permission. If yes, access is allowed; if not, it is denied. This keeps systems safer by limiting what users can do. Admins should monitor permissions and update them if needed to keep access tight but functional.