Discretionary Access Control (DAC)
What you'll learn: How DAC empowers resource owners to decide who can access their resources.
The Core Idea
Discretionary Access Control (DAC) is an access control model where the owner of a resource has the authority to grant or revoke access permissions to other users at their discretion. Unlike Mandatory Access Control (MAC), where a central authority enforces rigid security policies, DAC gives individual resource owners flexibility and control.
How DAC Works
Think of DAC like owning a house. As the homeowner, you decide who gets a key, who can visit, and who's not allowed in. You have complete discretion—you can change your mind anytime and give or take away access.
In computing systems:
- When you create a file, you become its owner
- You can set permissions (read, write, execute) for yourself and others
- You can grant specific users or groups different levels of access
- You can modify or revoke these permissions whenever you choose
Common DAC Examples
Unix/Linux file permissions are a classic DAC implementation. When you create a file, you control whether other users can read, modify, or execute it. Access Control Lists (ACLs) extend this by allowing more granular, user-specific permissions.
Key Characteristic: Owner Control
The defining feature of DAC is discretionary control—the owner's judgment determines access. There's no mandatory security label or centralized policy enforcing who can access what. This flexibility makes DAC user-friendly but also creates security risks: owners might accidentally grant excessive permissions or share sensitive resources inappropriately.
Key Takeaway: Discretionary Access Control puts access decisions in the hands of resource owners, offering flexibility and user autonomy but requiring owners to make responsible security choices.