Attribute-based access control: Difference between revisions

Revision as of 17:14, 2 October 2023

Revision as of 18:34, 13 October 2023

Line 55:

[[XACML]], the eXtensible Access Control Markup Language, defines an architecture (shared with ALFA and NGAC), a policy language, and a request/response scheme. It does not handle attribute management (user attribute assignment, object attribute assignment, environment attribute assignment) which is left to traditional [[Identity management|IAM]] tools, databases, and directories.

Companies, including every branch in the United States military, have started using ABAC. At a basic level, ABAC protects data with ‘IF/THEN/AND’ rules rather than assign data to users. The US Department of Commerce has made this a mandatory practice and the adoption is spreading throughout several governmental and military agencies.<ref>{{Citecite web |last1=Sanford |first1=Jim |title=Encryption on Steroids – Attribute Based Access Control (ABAC) |url=https://communityblogs.plm.automationsw.siemens.com/t5/Digitalthought-Transformationsleadership/2019/Attribute03/28/attribute-Basedbased-Accessaccess-Controlcontrol-ABACabac-Encryptionencryption-on-Steroidssteroids/ba-p/580836|title=Attribute Based Access Control (ABAC) – Encryption on Steroids|last=Coffey|first=Alisa|date=2019-03-28|website=Siemens PLM Community|language=en|access-date=2019-04-0113 October 2023}}</ref>

==Applications==