Access Control Models: DAC, MAC, and RBAC
What you'll learn: How three fundamental access control models—Discretionary, Mandatory, and Role-Based—decide who can access what, and when to use each.
The Core Idea
Access control models are frameworks that determine who gets access to which resources. Think of them as different philosophies for managing keys to locked rooms in a building.
Discretionary Access Control (DAC)
In DAC, resource owners decide who can access their resources. Like your personal files on a computer—you choose whether to share them and with whom.
- Flexibility: Owners have full control
- Risk: Users might grant access carelessly
- Example: File permissions in Windows or Linux where you set who can read/write your documents
Mandatory Access Control (MAC)
In MAC, a central authority enforces strict rules based on security classifications. No individual user can override these—even if you own the file.
- Rigidity: System-wide policies, not personal choices
- Use case: Military or government systems (remember Bell-LaPadula and Biba models? They're MAC implementations)
- Example: Documents marked "Top Secret" can only be accessed by personnel with that clearance level, regardless of who created them
Role-Based Access Control (RBAC)
In RBAC, access depends on job roles, not individual identity. You get permissions because you're an "accountant" or "manager," not because you're "Jane Smith."
- Scalability: Easy to manage large organizations
- Alignment: Supports Separation of Duties and Least Privilege
- Example: Hospital systems where nurses access patient records, but only doctors can prescribe medications
Choosing the Right Model
- DAC: Flexible environments where users need autonomy
- MAC: High-security environments requiring centralized control
- RBAC: Organizations with clear job functions and many users
Key Takeaway: DAC gives owners control, MAC enforces system-wide rules, and RBAC grants access by job function—pick the model that matches your security needs and organizational structure.