Attribute-Based Access Control (ABAC)
What you'll learn: How to make access decisions based on flexible attributes rather than fixed roles, enabling granular, context-aware authorization.
The Core Idea
While RBAC (from the previous lesson) groups users into roles with predefined permissions, Attribute-Based Access Control (ABAC) evaluates access requests based on attributes of multiple entities involved in the transaction. Think of it as checking multiple ID cards, environmental conditions, and resource properties all at once before granting access.
ABAC policies consider:
- User attributes: department, clearance level, job title, location
- Resource attributes: classification level, owner, creation date, file type
- Environment attributes: time of day, IP address, device security status, threat level
- Action attributes: read, write, delete, share
How It Works
Instead of "Does this user have the 'editor' role?" ABAC asks: "Is this user from the finance department, accessing a budget document they own, from a corporate network, during business hours, and requesting read access?"
Analogy: Imagine a smart building access system. Instead of just checking if you have an "employee badge" (RBAC), it also checks: Are you entering during your scheduled shift? Is your department authorized for this floor? Is your security clearance sufficient? Are you coming from a secure entrance? That's ABAC—multiple conditions working together.
Benefits and Complexity
ABAC provides extremely fine-grained control and adapts to changing contexts without modifying role structures. However, it requires careful policy design and can become complex to manage. You must define all relevant attributes and the logic that combines them into access decisions.
Key Takeaway: Attribute-Based Access Control evaluates multiple attributes from users, resources, and environmental context to make flexible, fine-grained authorization decisions beyond simple role membership.