https://wiki.idesg.org/index.php?action=history&feed=atom&title=OASIS_XACML_v3.0 2026-05-11T10:38:12Z Revision history for this page on the wiki MediaWiki 1.38.4 https://wiki.idesg.org/index.php?title=OASIS_XACML_v3.0&diff=4985&oldid=prev 2018-06-28T04:02:25Z

<p>2 revisions imported: Initial Upload of old pages from IDESG Wiki</p> <p><b>New page</b></p><div>&#039;&#039;&#039;Title&#039;&#039;&#039;: eXtensible Access Control Markup Language (XACML) Version 3.0<br /> <br /> &lt;br/&gt;<br /> &#039;&#039;&#039;Category&#039;&#039;&#039;: Access Control<br /> <br /> &lt;br/&gt;<br /> &#039;&#039;&#039;Date&#039;&#039;&#039;: 22 January 2013<br /> <br /> &lt;br/&gt;<br /> &#039;&#039;&#039;Creator&#039;&#039;&#039;: OASIS eXtensible Access Control Markup Language (XACML) TC<br /> <br /> &lt;br/&gt;<br /> &#039;&#039;&#039;URL&#039;&#039;&#039;: http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html<br /> <br /> &lt;br/&gt; <br /> &#039;&#039;&#039;Description&#039;&#039;&#039;: XACML is a general-purpose access control policy language. This means that it provides a syntax (defined in XML) for managing access to resources based on applicable policies combined with asserted facts about (“attributes” of) an authenticated user, the type of access requested, the protected information resource, and the environment or context of the transaction. XACML is used to implement attribute-based access control (ABAC.)<br /> <br /> &lt;br /&gt;<br /> &#039;&#039;&#039;Privacy&#039;&#039;&#039;: Privacy-enhancing.—ABAC as implemented with XACML enhances privacy by: (1) eliminating the need for relying-party systems to maintain user accounts with names and other identifying information; (2) supporting implementations that require only the minimum user information required by an access policy; and (3) enabling consistent and detailed compliance with policies on access to privacy-sensitive data of relying parties.<br /> <br /> &lt;br /&gt;<br /> &#039;&#039;&#039;Security&#039;&#039;&#039;: Secure and resilient.—XACML lets custodians of protected information resources enforce compliance with all policies applicable to access to a protected resource at an arbitrarily precise level, e.g, an individual row in a database or even individual data elements within a record. This can dramatically reduce the damage done by malevolent insiders or other attackers who have obtained an authentication credential.<br /> <br /> &lt;br /&gt;<br /> &#039;&#039;&#039;Interoperability&#039;&#039;&#039;: Interoperable.—Via Profiles (nominated separately), XACMLv3 is used in conjunction with SAMLv2, JSON and REST. Implementers have also deployed XACML-based authorization solutions that leverage User attributes in OAUTH2 tokens.<br /> <br /> &lt;br /&gt;<br /> &#039;&#039;&#039;Terms&#039;&#039;&#039;:<br /> <br /> <br /> <br /> [[Category:Standards]]</div>

Omaerz