Towards Standardization of Distributed Access Control Mario - - PowerPoint PPT Presentation
Towards Standardization of Distributed Access Control Mario - - PowerPoint PPT Presentation
Towards Standardization of Distributed Access Control Mario Lischka, Yukiko Endo Elena Torroglosa, Alejandro Prez, Antonio G. Skarmeta NEC Laboratories Europe University of Murcia Presentation at W3C Workshop on Access Control Application
Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
Different type of policies
identified different kind of policies
control the privacy of the user's
identity
his/her data, as well as interoperation between different
participants.
Decisions could not only be done locally, but have to be aligned with policies in other domains.
2
Overview
3 Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
- Example
- Important Aspects
- Proposed Architecture
- Extension to Policy Language
- Complexity of Evaluation
- Conclusion
Operator
Attribute Provider
Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
Example of Deductive Policies
Service Provider
Additional Service User’s Attribute Provider
Access Control Access Control Access Control Access Control
- Access to service provider requires
- approval of included service
- access to additional values
Slide 4
Decisions could not only be done locally, but have to be aligned with policies in other domains.
Request Attribute
Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
Important Aspects
Abstraction: details about other policy of
- ther domains are not required
Independent :definition of policies Adaptive: Policies support dynamic references to other authoritative domains Bridging: translation of local attribute names and value space into those of referred ones Transparency: location of the referred domain with respect to end-points is not explicitly required inside a policy Confidentiality: internal details on the rules and the attributes leading to the decision can be kept confidential
Slide 5
Authoritative Domain as new structuring entity Hierarchical requests: circular dependencies among Authoritative Domains have to be avoided
- Autho. Domain B
Policy Set B3 Policy Set B2 Policy Set B1
- Autho. Domain A
- Autho. Domain C
- Autho. Domain D
- Autho. Domain E
Depending on resource B2 refers to D or E
Proposed Architecture
Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
Extension to the existing XACML architecture
- Two new entities
responsible for deducting
- Attributes (DPIP)
- Authorization
request (DPDP)
- Messages are an
extension of XACML
Slide 6
Extension to XACML
Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
- Redefinition of PolicySet
- Integration of distributed PolicyReference and local
Policy through (new) combining algorithm
Slide 7
Complexity of the Evaluation
8 Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
- depending on combining algorithm
- local policies could be evaluated first, avoiding referred
requests
- Initiate parallel evaluation (saving time)
- referred request takes extra communication time
- referred Domains are always unique at evaluation time
(e.g, in contrast to Datalog)
- Circular dependencies are avoided
Complexity of the evaluation not changed compared to XACML
Conclusion
9 Presentation at W3C Workshop , 17./18. Nov. 2009,Luxembourg
- Deductive policies could be used to bridge different domains
- distribute decisions
- access to remote attributes
- Authoritative Domain provides a new abstraction level
- avoiding undeciadability problem of Datalog
- integration into existing XACML standard
- extra communication costs,
but no general increase of evaluation complexity
- Application of Deductive Polices in various prototypes
- f the EU FP7 project SWIFT