Attribute-Based Access Control (ABAC)
Abbreviation: ABAC
Pronunciation: A-truhb-yoot bayst AK-sehs kun-TROHL (A-B-A-C)
Also known as: Attribute-Based Access Control, ABAC
Definition
Attribute-Based Access Control (ABAC) is a security mechanism or control discipline that dynamically evaluates policies using attributes of the requester, resource, action, and environment before permitting access. Attribute-Based Access Control makes authorization decisions from descriptive attributes rather than relying only on fixed roles. Policies may consider department, account type, resource owner, data classification, transaction value, device trust, location, time, and requested operation.
Overview
Meaning and scope
Attribute-Based Access Control (ABAC) is a security mechanism or control discipline that dynamically evaluates policies using attributes of the requester, resource, action, and environment before permitting access. Attribute-Based Access Control makes authorization decisions from descriptive attributes rather than relying only on fixed roles. Policies may consider department, account type, resource owner, data classification, transaction value, device trust, location, time, and requested operation.
Mechanism and operation
ABAC can express fine-grained and context-sensitive rules, such as allowing finance staff to approve payouts below a limit from managed devices. Its flexibility also creates complexity when attributes are inaccurate, policies conflict, or decision logic becomes difficult to explain. Implementations need trusted attribute sources, clear policy precedence, deny-by-default behavior, testing, version control, and decision logging. Sensitive changes to attributes and policies require strong governance because altering one value can silently expand access across many resources. For Attribute-Based Access Control (ABAC), production scope should name the relevant subjects, authenticators, credentials, roles, policies, sessions, devices, resources, and recovery channels, the decision being supported, the accountable owner, and the time and jurisdiction boundaries.
Practical payment example
A payout system allows an approval only when user role, transaction size, business unit and destination risk collectively satisfy the policy.
Operational checks
ABAC enables precise contextual authorization, but trustworthy attributes and understandable, testable policies are essential to prevent hidden privilege expansion. For Attribute-Based Access Control (ABAC), the trust decision should establish evaluation of policies using attributes of the requester, resource, action, and environment before permitting access and bind the result to the requested action and protected resource.
Distinctions and limits
Teams should test issuance, storage, validation, expiry, revocation, recovery, and privileged override for policies using attributes of the requester, resource, and action, rather than checking only a successful request.
Related reading
Related definitions: authorization, transaction.
Example
A payout system allows an approval only when user role, transaction size, business unit and destination risk collectively satisfy the policy.
Comparison
Attribute-Based Access Control makes authorization decisions from descriptive attributes rather than relying only on fixed roles. Teams should test issuance, storage, validation, expiry, revocation, recovery, and privileged override for policies using attributes of the requester, resource, and action, rather than checking only a successful request.
Key Takeaway
ABAC enables precise contextual authorization, but trustworthy attributes and understandable, testable policies are essential to prevent hidden privilege expansion.
Sources
- European Union Legal Text — European Union (2026-07-30)
- NIST Documentation: Cyberframework — NIST (2026-07-30)