Access Control Lists (ACLs)
You'll learn how ACLs provide fine-grained, resource-specific permission management by explicitly defining which users or groups can access each resource.
What Are ACLs?
An Access Control List is a table attached to a resource that specifies exactly which users or groups have what permissions on that specific resource. Unlike RBAC (which grants permissions based on roles) or ABAC (which evaluates attributes and policies), ACLs directly associate permissions with individual resources.
Think of ACLs like a guest list at the door of each room in a building. Every room has its own list saying "Alice can enter and rearrange furniture, Bob can only look inside, Carol cannot enter at all." Each room's access is independently managed.
How ACLs Work
Each resource (file, database record, API endpoint, S3 bucket) maintains its own list of entries. Each entry specifies:
- Principal: Who (user ID, group, service account)
- Permission: What they can do (read, write, delete, execute)
- Grant or Deny: Whether the permission is allowed or blocked
When a user attempts to access a resource, the system checks that resource's ACL to determine if the action is permitted.
ACL vs RBAC vs ABAC
ACLs excel when you need per-resource control—like giving specific users access to specific documents without creating roles for every combination. However, they become harder to manage at scale because each resource must be configured individually. You might use ACLs for shared documents, file systems, cloud storage buckets, or database rows where ownership and sharing patterns vary widely.
Key Takeaway: ACLs grant permissions directly on individual resources, enabling precise control at the cost of potentially complex management when scaling to thousands of resources.