Attribute-based access control: Difference between revisions

Revision as of 13:44, 7 July 2015

Revision as of 23:30, 7 December 2015

Line 1:

'''Attribute-based access control''' (ABAC) defines an [[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.)<ref>{{Cite web |date=2014 |url=http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-162.pdf |title=SP 800-162, Guide to Attribute Based Access Control (ABAC) Definition and Considerations |format=PDF |publisher=NIST |accessdate=2015-12-08}}</ref>. 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==

Line 13:

* [http://link.springer.com/chapter/10.1007%2F978-3-642-31540-4_4 Unified Attribute Based Access Control Model (ABAC) covering DAC, MAC and RBAC]

* [http://profsandhu.com/dissert/Dissertation_Xin_Jin.pdf Attribute Based Access Control Models (ABAC) and Implementation in Cloud Infrastructure as a Service]

== References ==

{{Reflist}}

[[Category:Access control]]