Attribute-based access control: Difference between revisions

Revision as of 10:48, 6 October 2014

Revision as of 12:18, 15 October 2014

Line 2:

'''Attribute-based access control''' 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.

By James Brown

==Implementations==

One standard that implements attribute- and policy-based access control is [[XACML]], the eXtensible Access Control Markup Language. However, XACML only focuses on authorization policy specification. It does not solve attribute management (user attribute assignment, object attribute assignment, environment attribute assignment).