An RBAC-Based Access Control Model for Object-Oriented Systems Offering Dynamic Aspect Features
Summary :
This paper proposes a model for access control within object-oriented systems. The model is based on RBAC (role-based access control) and is called DRBAC (dynamic RBAC). Although RBAC is powerful in access control, the original design of RBAC required that user-role assignments and role-permission assignments should be handled statically (i.e., the assignments should be handled by human beings). Nevertheless, the following dynamic features are necessary in access control within a software system: (a) managing dynamic role switching, (b) avoiding Trojan horses, (c) managing role associations, and (d) handling dynamic role creation and deletion. DRBAC offers the dynamic features. This paper proposes DRBAC.
- Publication
- IEICE TRANSACTIONS on Information Vol.E88-D No.9 pp.2143-2147
- Publication Date
- 2005/09/01
- Publicized
- Online ISSN
- DOI
- 10.1093/ietisy/e88-d.9.2143
- Type of Manuscript
- PAPER
- Category
- Application Information Security
Authors
Keyword
Latest Issue
Copyrights notice of machine-translated contents
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Cite this
Copy
Shih-Chien CHOU, "An RBAC-Based Access Control Model for Object-Oriented Systems Offering Dynamic Aspect Features" in IEICE TRANSACTIONS on Information,
vol. E88-D, no. 9, pp. 2143-2147, September 2005, doi: 10.1093/ietisy/e88-d.9.2143.
Abstract: This paper proposes a model for access control within object-oriented systems. The model is based on RBAC (role-based access control) and is called DRBAC (dynamic RBAC). Although RBAC is powerful in access control, the original design of RBAC required that user-role assignments and role-permission assignments should be handled statically (i.e., the assignments should be handled by human beings). Nevertheless, the following dynamic features are necessary in access control within a software system: (a) managing dynamic role switching, (b) avoiding Trojan horses, (c) managing role associations, and (d) handling dynamic role creation and deletion. DRBAC offers the dynamic features. This paper proposes DRBAC.
URL: https://global.ieice.org/en_transactions/information/10.1093/ietisy/e88-d.9.2143/_p
Copy
@ARTICLE{e88-d_9_2143,
author={Shih-Chien CHOU, },
journal={IEICE TRANSACTIONS on Information},
title={An RBAC-Based Access Control Model for Object-Oriented Systems Offering Dynamic Aspect Features},
year={2005},
volume={E88-D},
number={9},
pages={2143-2147},
abstract={This paper proposes a model for access control within object-oriented systems. The model is based on RBAC (role-based access control) and is called DRBAC (dynamic RBAC). Although RBAC is powerful in access control, the original design of RBAC required that user-role assignments and role-permission assignments should be handled statically (i.e., the assignments should be handled by human beings). Nevertheless, the following dynamic features are necessary in access control within a software system: (a) managing dynamic role switching, (b) avoiding Trojan horses, (c) managing role associations, and (d) handling dynamic role creation and deletion. DRBAC offers the dynamic features. This paper proposes DRBAC.},
keywords={},
doi={10.1093/ietisy/e88-d.9.2143},
ISSN={},
month={September},}
Copy
TY - JOUR
TI - An RBAC-Based Access Control Model for Object-Oriented Systems Offering Dynamic Aspect Features
T2 - IEICE TRANSACTIONS on Information
SP - 2143
EP - 2147
AU - Shih-Chien CHOU
PY - 2005
DO - 10.1093/ietisy/e88-d.9.2143
JO - IEICE TRANSACTIONS on Information
SN -
VL - E88-D
IS - 9
JA - IEICE TRANSACTIONS on Information
Y1 - September 2005
AB - This paper proposes a model for access control within object-oriented systems. The model is based on RBAC (role-based access control) and is called DRBAC (dynamic RBAC). Although RBAC is powerful in access control, the original design of RBAC required that user-role assignments and role-permission assignments should be handled statically (i.e., the assignments should be handled by human beings). Nevertheless, the following dynamic features are necessary in access control within a software system: (a) managing dynamic role switching, (b) avoiding Trojan horses, (c) managing role associations, and (d) handling dynamic role creation and deletion. DRBAC offers the dynamic features. This paper proposes DRBAC.
ER -
English
