Attribute-based access control: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 22:45, 22 July 2025 edit Frap (talk \| contribs) Extended confirmed users, File movers, Pending changes reviewers, Rollbackers 35,593 edits →Applications ← Previous edit		Latest revision as of 08:50, 25 August 2025 edit undo Citation bot (talk \| contribs) Bots 5,867,154 edits Added bibcode. Removed URL that duplicated identifier. Removed parameters. \| Use this bot. Report bugs. \| Suggested by Headbomb \| Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox \| #UCB_webform_linked 199/1032
(One intermediate revision by one other user not shown)
Line 2: '''Attribute-based access control''' ('''ABAC'''), also known as '''policy-based access control''' for [[Identity management\|IAM]], defines an access control paradigm whereby a subject's authorization to perform a set of operations is determined by evaluating attributes associated with the subject, object, requested operations, and, in some cases, environment attributes.<ref>{{Cite web\|last=Computer Security Division\|first=Information Technology Laboratory\|date=2016-05-24\|title=Attribute Based Access Control {{!}} CSRC {{!}} CSRC\|url=https://csrc.nist.gov/Projects/Attribute-Based-Access-Control\|access-date=2021-11-25\|website=CSRC {{!}} NIST\|language=EN-US}}</ref> ABAC is a method of implementing access control policies that is highly adaptable and can be customized using a wide range of attributes, making it suitable for use in distributed or rapidly changing environments. The only limitations on the policies that can be implemented with ABAC are the capabilities of the computational language and the availability of relevant attributes.<ref>{{Cite journal \|last1=Hu \|first1=Vincent C. \|last2=Kuhn \|first2=D. Richard \|last3=Ferraiolo \|first3=David F. \|last4=Voas \|first4=Jeffrey \|date=February 2015 \|title=Attribute-Based Access Control ~~\|url=https://ieeexplore.ieee.org/document/7042715~~ \|journal=Computer \|volume=48 \|issue=2 \|pages=85–88 \|doi=10.1109/MC.2015.33 \|bibcode=2015Compr..48b..85H \|s2cid=54967881 \|issn=1558-0814~~\|url-access=subscription~~ }}</ref> ABAC policy rules are generated as Boolean functions of the subject's attributes, the object's attributes, and the environment attributes.<ref>{{Cite web \|title=Guide to Secure Web Services: Recommendations of the National Institute of Standards and Technology \|url=https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-95.pdf}}</ref> Unlike [[role-based access control]] (RBAC), which defines roles that carry a specific set of privileges associated with them and to which subjects are assigned, ABAC can express complex rule sets that can evaluate many different attributes. Through defining consistent subject and object attributes into security policies, ABAC eliminates the need for explicit authorizations to individuals’ subjects needed in a non-ABAC access method, reducing the complexity of managing access lists and groups. Line 136: * [http://csrc.nist.gov/projects/abac/ ATTRIBUTE BASED ACCESS CONTROL (ABAC) - OVERVIEW] * [https://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~~https://profsandhu.com/dissert/Dissertation_Xin_Jin.pdf Attribute Based Access Control Models (ABAC) and Implementation in Cloud Infrastructure as a Service] [[Category:Access control]]