Mandatory access control is centrally administered, with policy decisions made by security authorities rather than end users. Discretionary access control gives resource owners more freedom to grant or adjust access themselves. MAC offers tighter consistency and governance, while DAC provides flexibility but requires stronger local discipline to avoid permission drift and unintended exposure.
How MAC and DAC differ in who makes the access decision
The core difference is authority. In mandatory access control, the system enforces centrally defined policy, so users and owners cannot simply override it for convenience. In discretionary access control, the resource owner can typically decide who else gets access, which makes the model faster to use but more dependent on local judgement and consistent administration.
That difference matters because the access model shapes how predictable permissions are across an environment. MAC is designed to preserve uniform policy enforcement even when individual users would prefer exceptions. DAC is better when collaboration and ad hoc sharing matter, but it can become inconsistent if owners grant access too broadly or fail to revoke it promptly.
Why the two models produce different security outcomes
MAC and DAC are not just two administrative styles, they create different trust boundaries. With MAC, the security model assumes policy should be harder to bypass than individual preference, so it is useful where rule consistency is more important than convenience. With DAC, the owner of the data or object is part of the control plane, which works well in smaller or more flexible environments but can increase variation in how access is granted.
That is why MAC is usually associated with stronger control and tighter consistency, while DAC is often associated with usability and operational speed. The trade-off is simple: the more freedom you give owners to share data, the more you must rely on them to apply least privilege, keep permissions current, and avoid accidental exposure.
For readers comparing access control models in practice, Classic Security Models Guide explains how MAC fits into the broader family of formal security models and why the reference monitor idea matters.
Where MAC and DAC fit in real environments
MAC is most useful when the organisation wants centrally enforced policy that does not depend on every resource owner making the right decision every time. It is common in environments where data classification, compartmentation, and strict policy consistency are essential. DAC is more common where owners need to grant access quickly, share files or resources informally, and adapt permissions to changing work patterns.
In practice, many environments mix the two. A platform may enforce a stronger system-wide policy at one layer while still allowing owners to manage access at another layer. That hybrid pattern is common because pure MAC can be rigid, while pure DAC can drift over time. For a practical view of how access decisions are structured across roles, attributes, and relationships, see the Authorisation Models Guide.
If you are trying to decide which model better matches a control objective, ask whether the main requirement is central consistency or owner-level agility. Where the answer is consistency, MAC is the better fit. Where the answer is flexibility, DAC may be acceptable, but only if the organisation can tolerate more variance in permission hygiene.
Risk and Threat Considerations
DAC increases the chance of permission drift because access changes can happen locally, informally, or without strong review. That makes over-sharing, stale grants, and privilege creep more likely, especially when many owners manage many resources over time.
Failure mechanism: Access decisions become fragmented across owners, so revoked need-to-know boundaries are not consistently applied and exposures accumulate.
Impact: Unintended access can spread quietly, making data leakage, lateral access, and audit exceptions more likely than in a centrally governed model.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | MAC and DAC both determine how access is enforced. |
| AC-6 — Least Privilege | DAC can drift into broader permissions without tight privilege discipline. | |
| Recommendation — Use AC-3 to enforce access decisions through centrally defined authorization logic. Use AC-6 to limit discretionary grants to the minimum necessary access. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The question compares access control governance models and enforcement style. |
| Recommendation — Define and apply access control rules consistently across systems and users. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Control 6 addresses how organizations grant, revoke, and centralize access governance. |
| Recommendation — Centralize access granting and revocation so permissions do not drift. | ||
Practitioner Guidance
What to prioritise: Treat the model choice as a governance decision, not just a technical one. If the environment contains sensitive data, regulated records, or tightly bounded operational roles, privilege consistency should outweigh convenience.
What to verify: Check whether the effective access process matches the intended one. In DAC-heavy environments, review who can grant access, how revocation happens, and whether owners have visibility into the permissions they have accumulated.
Common mistake: Assuming that a flexible model is automatically easier to manage. Flexibility is only safe when there is a compensating review process, because owner-granted access tends to expand faster than it is removed.
Practitioner takeaway: Choose MAC when policy consistency must dominate, and DAC when business agility matters more, but only if you have enough review discipline to prevent permission drift from becoming the real control plane.
Related resources from NHI Mgmt Group
- Guide: Reference Monitors and Mandatory Access Control Guide
- How should security teams combine mandatory and discretionary access control in modern applications?
- How should security teams implement mandatory access control in environments with shared systems and sensitive data?
- Why does mandatory access control reduce risk in environments where users move across many systems and resources?
- What breaks when discretionary access control is used without strong administrative oversight?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org