Attribute-based access control: Difference between revisions

Revision as of 18:53, 19 September 2020

Revision as of 02:28, 24 September 2020

Line 1:

{{cleanup HTML|date=September 2020|tags=tt}}

'''Attribute-based access control''' ('''ABAC'''), also known as '''policy-based access control''' for [[Identity management|IAM]], 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 attributes etc.). This model supports Boolean logic, in which rules contain "IF, THEN" statements about who is making the request, the resource, and the action. For example: IF the requester is a manager, THEN allow read/write access to sensitive data. The NIST framework introduces the main concepts of ABAC as its entities, i.e. PAP (Policy Administration Point), PEP (Policy Enforcement Point), PDP (Policy Decision Point) and PIP (Policy Information Point)<ref>{{Cite web|last=NIST|first=ABAC|date=2014|title=Guide to Attribute Based Access Control (ABAC) Definition and Considerations|url=https://nvlpubs.nist.gov/nistpubs/specialpublications/NIST.SP.800-162.pdf|url-status=live|archive-url=|archive-date=|access-date=|website=}}</ref><ref>{{Cite web|last=NIST|date=2016|title=A Comparison of Attribute Based Access Control (ABAC) Standards for Data ServiceApplications|url=https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-178.pdf|url-status=live|archive-url=|archive-date=|access-date=|website=}}</ref>.

Line 82 ⟶ 81:

* Policy: managers can view transactions in their region

* Reworked policy in a data-centric way: users with <tt>{{code|role == manager</tt>}} can do the action <tt>{{code|== SELECT on table == TRANSACTIONS if user.region == transaction.region</tt>}}

=== Data security ===