2012
DOI: 10.1016/j.cose.2012.01.010
|View full text |Cite
|
Sign up to set email alerts
|

domRBAC: An access control model for modern collaborative systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
25
0
1

Year Published

2013
2013
2019
2019

Publication Types

Select...
6
2

Relationship

2
6

Authors

Journals

citations
Cited by 37 publications
(26 citation statements)
references
References 13 publications
0
25
0
1
Order By: Relevance
“…Through an example, we demonstrated the proposed methodology, which resulted in a critique of existing AC approaches in [3] and the development of a new AC model for collaborative systems (e.g. Cloud environments) in [18]. Furthermore, we referred to the application of a model checking approach proposed by NIST, which resulted in the verification of the principles of security and autonomy in our defined AC model.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…Through an example, we demonstrated the proposed methodology, which resulted in a critique of existing AC approaches in [3] and the development of a new AC model for collaborative systems (e.g. Cloud environments) in [18]. Furthermore, we referred to the application of a model checking approach proposed by NIST, which resulted in the verification of the principles of security and autonomy in our defined AC model.…”
Section: Discussionmentioning
confidence: 99%
“…Table 1 summarizes the evaluation of RBAC in the context of CC based on [3]. Therefore, after evaluating RBAC, we proceeded with the design of a new access control model entitled domRBAC [18] that is suitable for modern collaborative environments. Table 1 illustrates the evaluation of domRBAC compared to RBAC, where it is shown that domRBAC strengthens the RBAC approach in all layers.…”
Section: Fig 4 Operational Environmentmentioning
confidence: 99%
See 1 more Smart Citation
“…But this model paid little attention to the security risk of privilege penetration, covert privilege promotion and role-associated conflict resulted from separation of duty constraint, role translation and domain shuttle. Then, lots of solutions were present based on IRBAC and its security [3,4] . These solutions didn't consider the security problem of covert privilege promotion and role-associated conflict, et al The domain concept is introduced to bind with role, privilege and other elements for inter-domain access control by Zan Yang [5].…”
Section: Introductionmentioning
confidence: 99%
“…context or attributes, and creating a new access control model. [10] Following the role based access control [12] has developed an access control model, which extends role based access control for virtual organizations. Unfortunately this model does not cover business processes, workflows, and cloud computing.…”
Section: Processesmentioning
confidence: 99%