Insights on Crypto Payments, Infrastructure, and Operations

Discretionary Access Control (DAC)

Abbreviation: DAC

Pronunciation: dih-SKRESH-uh-nair-ee AK-sess kun-TROHL (D-A-C)

Also known as: DAC

Definition

Discretionary Access Control (DAC) is an access-control model in which the owner or another authorized principal can decide who receives permissions to a resource. It differs from an ACL because DAC is the governing model, while an ACL is one mechanism that can record permissions. Organizations should constrain delegation, apply least privilege, control inheritance and sharing, review ownership changes, log grants and revocations, prevent confused-deputy behavior, and use stronger mandatory or role-based controls where owner discretion creates unacceptable risk.

Overview

Discretionary Access Control (DAC) is an access-control model in which the owner or another authorized principal can decide who receives permissions to a resource. The control exists to ensure that only appropriately identified and authorized principals can access resources or approve actions at the required level of assurance. It differs from an ACL because DAC is the governing model, while an ACL is one mechanism that can record permissions. It should be interpreted alongside Access Control List (ACL) because the concepts can affect the same decision without representing the same control, event, or risk.

The workflow establishes a trusted identity or service principal, binds authenticators, evaluates context, applies policy, and records the resulting access decision. Authorization must be enforced by the server or resource boundary on every relevant request and should not depend on hidden interface elements or untrusted client claims. In this context, organizations should constrain delegation, apply least privilege, control inheritance and sharing, review ownership changes, log grants and revocations, prevent confused-deputy behavior, and use stronger mandatory or role-based controls where owner discretion creates unacceptable risk.

It should connect the term to Access Token where that relationship changes access, transaction treatment, investigation, communication, or recovery.

Records should capture principal, authenticator or credential type, assurance level, resource, action, policy version, contextual signals, decision, failures, recovery, grants, revocations, and administrative changes. Sensitive secrets and authentication content should not be copied unnecessarily into logs.

Useful measures include enrollment and recovery success, challenge rate, failure rate, unauthorized attempts, privilege age, dormant access, review completion, false rejection, compromise events, and time to revoke access.

The relationship with Asset Inventory should be documented where it affects residual risk or control ownership.

Key Takeaway

Organizations should constrain delegation, apply least privilege, control inheritance and sharing, review ownership changes, log grants and revocations, prevent confused-deputy behavior, and use stronger mandatory or role-based controls where owner discretion creates unacceptable risk.

Sources

  1. Digital Identity Guidelines: Authentication and Authenticator Management, SP 800-63B-4 — NIST (2026-08-03)
  2. Security and Privacy Controls for Information Systems and Organizations, SP 800-53 Rev. 5 — NIST (2026-08-03)
  3. A07:2021 Identification and Authentication Failures — OWASP (2026-08-03)