Proceedings of the 8th Workshop on Middleware for Next Generation Internet Computing 2013
DOI: 10.1145/2541608.2541611
|View full text |Cite
|
Sign up to set email alerts
|

Introducing concurrency in policy-based access control

Abstract: Policy-based access control aims to decouple access control rules from the application they constrain by expressing these rules in declarative access control policies. Performance of policy-based access control is of growing importance, but concurrent and distributed policy evaluation has received little research attention and current policy evaluation engines are still single-machine and fully sequential to the best of our knowledge. We believe that concurrent policy evaluation is necessary to meet the perfor… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2014
2014
2014
2014

Publication Types

Select...
1

Relationship

1
0

Authors

Journals

citations
Cited by 1 publication
(2 citation statements)
references
References 13 publications
0
2
0
Order By: Relevance
“…For attribute-based policies, this evaluation duration is mainly determined by the latency of fetching the required attributes [17]. The latency of a remote attribute fetch between tenant and provider will be an order of magnitude larger than a local database call, taking into account the complex data flows in federated applications and the geographical distance between tenant and provider.…”
Section: Overviewmentioning
confidence: 99%
See 1 more Smart Citation
“…For attribute-based policies, this evaluation duration is mainly determined by the latency of fetching the required attributes [17]. The latency of a remote attribute fetch between tenant and provider will be an order of magnitude larger than a local database call, taking into account the complex data flows in federated applications and the geographical distance between tenant and provider.…”
Section: Overviewmentioning
confidence: 99%
“…Attribute updates can be used to model historybased policies [19], e.g., a separation-of-duty policy that states that a member of the help desk cannot view both insurance and financial documents of a single organization or a policy that limits the number of views of a document. Both attribute updates and history-based policies introduce extra complexity in policy federation because (1) attribute updates require concurrency control in case of distributed policy evaluation [17] and (2) history-based policies are known to have a large impact on performance [19]. Both are therefore interesting tracks for future research.…”
Section: Obligations and Attribute Updatesmentioning
confidence: 99%