Attribute-based access control

This is an old revision of this page, as edited by BG19bot (talk | contribs) at 04:31, 20 August 2014 (WP:CHECKWIKI error fix. Section heading problem. Violates WP:MOSHEAD.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Formal Model

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.

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).

ATTRIBUTE BASED ACCESS CONTROL (ABAC) - OVERVIEW

Unified Attribute Based Access Control Model (ABAC) covering DAC, MAC and RBAC

Attribute Based Access Control Models (ABAC) and Implementation in Cloud Infrastructure as a Service