Attribute-Based Access Control (ABAC)
You'll learn how ABAC makes authorization decisions using flexible policies based on user, resource, and environmental attributes.
What is ABAC?
While RBAC assigns permissions based on roles (like "admin" or "editor"), Attribute-Based Access Control (ABAC) evaluates multiple attributes to determine access. Instead of asking "What role does this user have?", ABAC asks "Does this combination of attributes satisfy our policy?"
ABAC policies consider three types of attributes:
- User attributes: department, clearance level, location, employment status
- Resource attributes: classification level, owner, creation date, sensitivity
- Environmental attributes: time of day, IP address, device type, risk score
How ABAC Works
Think of ABAC like a bouncer at an exclusive event who checks multiple criteria: your age (user attribute), the VIP status of your ticket (resource attribute), and whether it's before midnight (environmental attribute). All conditions must align with the policy.
An ABAC policy might state: "Allow access if user.department == 'Finance' AND resource.type == 'financial_report' AND environment.time BETWEEN 9am-5pm."
Why ABAC Matters
ABAC provides fine-grained, context-aware authorization that adapts to complex business rules. It's especially valuable when:
- Access rules depend on dynamic conditions (time, location)
- You need more granularity than simple roles provide
- Compliance requires tracking specific attribute combinations
- Users wear multiple "hats" that aren't cleanly role-based
The trade-off? ABAC policies can become complex and harder to audit than simple role assignments.
Key Takeaway: ABAC enables dynamic, fine-grained authorization by evaluating user, resource, and environmental attributes against flexible policies, offering more context-aware access control than role-based systems.