Attribute-Based Access Control (ABAC)
What you'll learn: How ABAC uses characteristics of users, resources, and situations to make smart, flexible authorization decisions.
The Core Idea
Imagine a library where instead of just checking "Are you a member?" (like RBAC's role check), the librarian considers multiple factors: "Are you over 18? Is this book marked sensitive? Is it after 6 PM? Are you accessing from inside the building?" ABAC works exactly this way—it evaluates attributes from different sources to decide access.
While Role-Based Access Control (RBAC) asks "What role do you have?", ABAC asks "What are your characteristics, what is being accessed, and what's the context?"
The Three Pillars of ABAC
User attributes: Properties of the requester (department=Finance, clearance_level=3, employment_status=active)
Resource attributes: Properties of what's being accessed (document_classification=confidential, owner=HR, created_date=2024)
Environmental/context attributes: Situational factors (time_of_day=business_hours, location=corporate_network, device_type=managed_laptop)
How It Enables Fine-Grained Control
ABAC policies combine these attributes into rules:
"Allow access if user.department == resource.owner_department AND user.clearance >= resource.sensitivity AND environment.location == 'corporate_network'"
This gives you fine-grained authorization—far more precise than simply "Managers can access all reports." Now you can say "Financial managers can access reports owned by Finance during business hours from approved devices."
ABAC aligns perfectly with Least Privilege and Complete Mediation by evaluating every request against current attributes, not just static roles assigned months ago.
Key Takeaway: ABAC uses multiple attributes about who's asking, what they're requesting, and the current situation to make flexible, context-aware access decisions that adapt to real-world complexity.