Access Control Lists (ACLs)
What you'll learn: How Access Control Lists (ACLs) define exactly which users or groups can access specific resources and what they're allowed to do with them.
What Are Access Control Lists?
An Access Control List (ACL) is a table or data structure that specifies permissions for users or groups on particular resources (files, directories, database records, API endpoints, etc.). Think of it like a guest list at an exclusive event—but instead of just "in or out," each entry also describes what each guest can do once inside.
After a system authenticates who you are (as we've learned), ACLs help enforce authorization by answering: "Does this authenticated user have permission to read/write/delete this specific resource?"
How ACLs Work
Each ACL entry typically contains:
- Principal: The user or group (e.g., "user123" or "admins_group")
- Resource: What's being protected (e.g., "/documents/report.pdf")
- Permissions: Specific actions allowed (read, write, execute, delete, modify)
Example Structure
Imagine a file report.pdf with this ACL:
User: alice → Read, Write
User: bob → Read
Group: managers → Read, Write, Delete
User: charlie → (no entry = no access)
When Bob tries to delete report.pdf, the system checks the ACL, finds Bob only has "Read" permission, and denies the request.
ACLs vs Role-Based Access
ACLs are resource-centric—permissions are attached to the resource itself. This offers fine-grained control but can become complex when managing thousands of resources and users.
Key Takeaway: Access Control Lists provide granular, resource-specific permission management by explicitly defining which users or groups can perform which actions on each protected resource.