[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] Groups - XACML v3.0 Obligation and Advice Authority (OAA) Profile Version 1.0 uploaded
Thanks Steven for posting this.
In Section 2 there is a use-case which motivates the profile. To summarize, your use-case requires:
- Bob can “create”, “read”, “update” and “destroy” documents.
- Alice can only “read” document.
- “Create”, “update” and “destroy” by anyone must be logged.
- Any operation on sensitive resources must take approval.
You have argued that adding the obligations requires splitting the authorization rules, but I don’t see why this is necessary. Correct me if I am wrong but I think these requirements can be formulated by the following PolicySet without splitting the rules:
(I have attached a PDF if you are reading in plain text):
Suppose Bob wants to update a sensitive document. This will match policyset 1, 1.1, and 1.1.1 and causes rule 126.96.36.199 to evaluate, permitting the access. But since the overarching combining algorithm is deny-overrides, policy 1.2 is also evaluated. Again since the combing algorithm is deny-override, both rules are evaluated triggering both obligations to log and take approval.
Any other authorization rule can go under policyset 1.1 and any other obligation rule can go under policy 1.2.
Mohammad Jafari, Ph.D.
Security Architect, Edmond Scientific Company