🔐 Access Control — 5 ways to decide “Who can access what?

🔐 Access Control — 5 ways to decide “Who can access what?”

RBAC asks “What is your role?”

ReBAC asks “How are you related?”

PBAC asks “What does the policy say?”

ABAC asks “What are your attributes?”

FGAC asks “Exactly what are you allowed to touch?”

1. RBAC — Role-Based Access Control

Permissions are based on the user’s role.
→ A Developer can access code, while an Admin can manage users.

1. ReBAC — Relationship-Based Access Control

Permissions are based on the relationship between the user and resource.
→ You can edit a GitHub repo because you are its owner.

1. PBAC — Policy-Based Access Control

Access is decided by rules/policies defined by the system.
→ Allow deployment only when the branch is main and tests have passed.

1. ABAC — Attribute-Based Access Control

Access depends on attributes of the user, resource, or request.
→ Allow access if role = developer and environment = staging.

1. FGAC — Fine-Grained Access Control

Permissions are controlled at a very specific level, rather than giving broad access.
→ A developer can edit user.name but cannot access user.password.

Now you know something new, feel free to ask question or search for more information and grow.

Connect:

Github – https://github.com/shani-tiwari

IG – https://instagram.com/shani.develops

X – https://x.com/shanidevelops