DAC gives users or delegates more flexibility to modify access, while MAC enforces stricter predefined policy controls. In an RBAC system, DAC is more adaptable but harder to monitor consistently, whereas MAC supports tighter governance and more predictable enforcement. The choice depends on whether the organisation values flexibility or stricter security control.
How DAC and MAC differ as authorization models
DAC and MAC both sit on top of an access-control design, but they make very different assumptions about who can change access. DAC lets the resource owner or a delegate decide who else may access it. MAC removes that discretion and relies on centrally defined policy, labels, or clearance rules that users cannot override.
The practical difference is governance, not just terminology. DAC is usually easier to adapt for fast-moving teams because the owner can grant access quickly, but it can drift as permissions spread. MAC is tighter and more uniform, which makes it better for high-control environments where policy consistency matters more than local convenience.
In an RBAC-based authorization model, both can be layered around roles, but they answer different questions. DAC asks who is allowed to delegate access. MAC asks what the policy permits regardless of individual preference. That is why MAC feels more rigid, while DAC feels more operationally flexible.
Why the distinction matters inside RBAC
RBAC defines access through roles, but it does not by itself settle whether a role holder can further delegate or modify access. That is where DAC and MAC shape the operating model. If role owners can reassign or share access freely, the RBAC design behaves more like DAC. If access decisions are bound to centrally enforced policy and cannot be altered ad hoc, the model behaves more like MAC.
This matters because role design and delegation rules determine how predictable authorization will be in practice. An RBAC implementation with broad delegation can become harder to audit, especially when owners create exceptions outside the intended role structure. An RBAC implementation with mandatory policy constraints is more consistent, but it can slow down legitimate changes if the policy model is too coarse.
For a deeper comparison of RBAC with adjacent models, NHIMG’s Authorisation Models Guide explains how role-based, attribute-based and relationship-based approaches differ when you need finer-grained control than roles alone can provide.
If your RBAC design also has to survive review, certification, and role engineering at scale, the Role Mining and Role Design Guide is useful because role explosion and ambiguous ownership are common failure points when delegation is left too loose.
When to prefer flexibility or stricter control
DAC tends to suit environments where business owners need to move quickly, permissions are relatively low-risk, and local accountability is more valuable than central uniformity. It works best when delegation boundaries are clear and access changes are small enough that informal modification does not create unacceptable exposure.
MAC is the better fit when the main concern is preventing unauthorised override of policy, especially where classification, segregation, or tightly bounded access is important. It reduces the chance that a well-meaning owner can make an access decision that conflicts with organisational policy.
In practice, many organisations end up with a hybrid design: RBAC for the main entitlement structure, DAC-like delegation for limited operational exceptions, and MAC-like constraints for the most sensitive resources. The important point is to decide explicitly which layer gets final authority, rather than assuming RBAC alone will resolve that question.
Risk and Threat Considerations
DAC increases the chance of privilege drift because access can be passed along by people who are close to the work but far from the governance model. That can create uneven enforcement, stale delegations, and a wider blast radius if an owner account is compromised.
Failure mechanism: delegated access accumulates outside central policy, so the organisation loses a reliable view of who can reach sensitive resources and why.
Impact: auditability weakens, access reviews become less trustworthy, and an attacker who compromises a delegate can inherit permissions that were never meant to be broadly shareable.
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 sets 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 | DAC and MAC both govern how access decisions are enforced. |
| AC-5 — Separation of Duties | DAC delegation can blur separation between access owner and approver. | |
| AC-6 — Least Privilege | MAC is typically used to constrain access more tightly than discretionary sharing. | |
| Recommendation — Define and enforce access decisions centrally so role holders cannot bypass policy. Separate request, approval and administration duties for sensitive access. Limit each role to the minimum access needed for its function. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The question is fundamentally about access-control policy choice and enforcement. |
| A.5.18 — Access rights | DAC and MAC affect how access rights are granted, reviewed and revoked. | |
| Recommendation — Document and apply an access-control policy that distinguishes owner discretion from mandatory enforcement. Review and revoke access rights on a defined schedule with clear ownership. | ||
Practitioner Guidance
What to verify: check whether your RBAC implementation allows role holders to grant, transfer, or extend access without a compensating approval path. If it does, treat that as a delegation control, not just an RBAC convenience feature.
Decision rule: use DAC only where local discretion is low risk and can be reviewed quickly; use MAC where policy consistency, segregation, or non-overridable enforcement is the control objective.
Practitioner takeaway: RBAC is the structure, but DAC or MAC determines how much discretion exists inside that structure, and the governance outcome depends on which one is allowed to win when they conflict.
Related resources from NHI Mgmt Group
- What is the difference between RBAC and policy-based authorization for NHIs?
- What breaks when RBAC is the only authorization model in an enterprise app?
- Why does resource-based authorization reduce over-provisioning compared with RBAC?
- How do organisations decide whether to use a policy-based authorization model or keep permissions inside applications?
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 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org