<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ABAC + RBAC = ARRRRR-BAC</title>
	<atom:link href="http://smokingmonkey.org/?feed=rss2&#038;p=13" rel="self" type="application/rss+xml" />
	<link>http://smokingmonkey.org/?p=13</link>
	<description>Ponderings on Identity Management</description>
	<lastBuildDate>Mon, 30 Aug 2010 12:25:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mat Hamlin</title>
		<link>http://smokingmonkey.org/?p=13&#038;cpage=1#comment-10</link>
		<dc:creator>Mat Hamlin</dc:creator>
		<pubDate>Fri, 30 Oct 2009 14:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://smokingmonkey.org/?p=13#comment-10</guid>
		<description>&lt;p&gt;&quot;From the perspective of entitlement enforcement, the basic jist is that any system that is going to work for a customer needs to support both ABAC and RBAC. Policy enforcement decisions need to take in to consideration role definitions and sometimes they also need to incorporate dynamic attributes from applications.&quot;&lt;/p&gt;
&lt;p&gt;Amen.&lt;/p&gt;
&lt;p&gt;We cannot assume that all entitlement enforcement decisions can be made based on Roles only.. It&#039;s just not reality.  There will always be policies that define access based on a particular entitlement and/or context. &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&quot;From the perspective of entitlement enforcement, the basic jist is that any system that is going to work for a customer needs to support both ABAC and RBAC. Policy enforcement decisions need to take in to consideration role definitions and sometimes they also need to incorporate dynamic attributes from applications.&quot;</p>
<p>Amen.</p>
<p>We cannot assume that all entitlement enforcement decisions can be made based on Roles only.. It&#8217;s just not reality.  There will always be policies that define access based on a particular entitlement and/or context. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Raskin</title>
		<link>http://smokingmonkey.org/?p=13&#038;cpage=1#comment-9</link>
		<dc:creator>Daniel Raskin</dc:creator>
		<pubDate>Fri, 30 Oct 2009 03:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://smokingmonkey.org/?p=13#comment-9</guid>
		<description>&lt;p&gt;Hi Babak. In the 3rd paragraph I&#039;m simply stating what many critics of RBAC say (i.e.--ABAC proponents). In the following paragraph I&#039;m saying that debating &quot;pure&quot; RBAC is silly as you only see it in textbooks. My take is that it&#039;s an academic argument because you will rarely, if ever, come across an environment that is purely RBAC. In fact, it&#039;s usually the exact opposite problem. An org is trying to get some semblance of roles in place just to get a basic foundation for compliance. If that makes me a proponent of ABAC then so be it, but I don&#039;t really think those that are proponents of RBAC really believe that all attributes will be part of a role. Anyway, thanks for the comment. &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Babak. In the 3rd paragraph I&#8217;m simply stating what many critics of RBAC say (i.e.&#8211;ABAC proponents). In the following paragraph I&#8217;m saying that debating &quot;pure&quot; RBAC is silly as you only see it in textbooks. My take is that it&#8217;s an academic argument because you will rarely, if ever, come across an environment that is purely RBAC. In fact, it&#8217;s usually the exact opposite problem. An org is trying to get some semblance of roles in place just to get a basic foundation for compliance. If that makes me a proponent of ABAC then so be it, but I don&#8217;t really think those that are proponents of RBAC really believe that all attributes will be part of a role. Anyway, thanks for the comment. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Babak Sadighi</title>
		<link>http://smokingmonkey.org/?p=13&#038;cpage=1#comment-8</link>
		<dc:creator>Babak Sadighi</dc:creator>
		<pubDate>Thu, 29 Oct 2009 08:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://smokingmonkey.org/?p=13#comment-8</guid>
		<description>&lt;p&gt;Hi Daniel,&lt;/p&gt;
&lt;p&gt;I am not sure if I understand this correctly. In paragraph 3 you say that the critics saying that we need roles plus other attributes, and then in the next paragraph you say that the debate is self-created and that we simply need roles plus attributes! Isn&#039;t that a repetition of the critic that you somehow object?&lt;/p&gt;
&lt;p&gt;There is actually no RBAC vs. ABAC as such, but the debate is if we solve some of the issues that a pure-RBAC model can be avoided by extending the model to talk about other attributes than only the roles of users. &lt;/p&gt;
&lt;p&gt;It is good that OpenSSO has now entitlement management capabilities.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Babak  &lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Daniel,</p>
<p>I am not sure if I understand this correctly. In paragraph 3 you say that the critics saying that we need roles plus other attributes, and then in the next paragraph you say that the debate is self-created and that we simply need roles plus attributes! Isn&#8217;t that a repetition of the critic that you somehow object?</p>
<p>There is actually no RBAC vs. ABAC as such, but the debate is if we solve some of the issues that a pure-RBAC model can be avoided by extending the model to talk about other attributes than only the roles of users. </p>
<p>It is good that OpenSSO has now entitlement management capabilities.</p>
<p>Regards,</p>
<p>Babak  </p>
]]></content:encoded>
	</item>
</channel>
</rss>
