Attribute-based access control: Difference between revisions

Revision as of 00:21, 10 June 2016

Revision as of 14:33, 4 July 2016

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, object, environment attributeattributes etc.). Unlike Role-Bases Access Control (RBAC), which employs pre-defined roles that carry a specific set of privileges associated with them and to which subjects are assigned, the key difference with ABAC is the concept of policies that express a complex Boolean rule set that can evaluate many different attributes.<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 valuesvalue. Examples are role, and project. Atomic-valued attributes containscontain only one atomic value. Examples are [[Classified_information#Clearance|clearance,]] and 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]

* [https://f5.com/about-us/blog/articles/abac-not-rbac-welcome-to-the-iot-world-of-contextual-security ABAC not RBAC: Welcome to the (IoT) World of Contextual Security, 2015, Lori MacVittie]

== References ==