Attribute-based access control: Difference between revisions

Revision as of 15:19, 5 November 2014

Revision as of 17:34, 10 November 2014

Line 1:

{{Underlinked|date=September 2014}}

'''Attribute-based access control''' (ABAC) defines a new [[access control]] paradigm whereby access rights are granted to users through the use of policies which combine attributes together. The policies can use any type of attributes (user attributes, resource attributes, environment attribute etc.). Attribute values can be set-valued or atomic-valued. Set-valued attributes contain more than one atomic values. Examples are role, project. Atomic-valued attributes contains only one atomic value. Examples are clearance, sensitivity. Attributes can be compared to static values or to one another thus enabling relation-based access control.

==Other models==

Historically, access control models have included mandatory access control ([[MAC]]), discretionary access control ([[DAC]]), and more recently role-based access control ([[RBAC]]). These access control models are user-centric and do not take into account additional parameters such as resource information, relationship between the user (the requesting entity) and the resource, and dynamic information e.g. time of the day or user IP.

ABAC tries to address this by defining access control based on attributes which describe the requesting entity (the user), the targeted object or resource, the desired action (view, edit, delete...), and environmental or contextual information. This is why access control is said to be attribute-based.

==Implementations==