{"title":"Control principles and role hierarchies","authors":"J. Moffett","doi":"10.1145/286884.286900","DOIUrl":"https://doi.org/10.1145/286884.286900","url":null,"abstract":"Role -based access control (RBAC) has been introduced in the last few years, and offers a powerful means of specifying access control decisions. The model of RBAC usually assumes that, if there is a role hierarchy, then access rights are inherited upwards through the hierarchy. This paper examines the relationship between the inheritance properties of role hierarchies and control principles which are used in many large organisations: separation of duties; delegation; and supervision and review. It discusses possible relationships between roles and identifies three different kinds of role hierarchy. The control principles and role hierarchies are illustrated in a realistic application, and their interactions are discussed. It emerges that there may be conflict between control principles and the inheritance of access rights through a role hierarchy. Some ways in which role hierarchies can be used for safe inheritance of access rights are discussed.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115276969","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Role and task-based access control in the PerDiS groupware platform","authors":"G. Coulouris, J. Dollimore, Marcus Roberts","doi":"10.1145/286884.286908","DOIUrl":"https://doi.org/10.1145/286884.286908","url":null,"abstract":"A roleand task-based access control scheme has been developed for use in a class of activities that entail cooperation between principals in a virtual enterprise (VE). Data ownership is associated with the component organisations of a VE, each of which constitutes a trust domain. The role/task model was chosen to meet the requirement for a generic access control scheme independent of application code. The model has been implemented for a software platform that provides shared access to clusters of replicated distributed objects. Implications arising from the integration of the access control model with a data replication scheme are discussed.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126689919","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Role activation hierarchies","authors":"R. Sandhu","doi":"10.1145/286884.286891","DOIUrl":"https://doi.org/10.1145/286884.286891","url":null,"abstract":"The concept of a role hierarchy (that is, partial order) is often included in role-based access control (RBAC) models and systems. In current practice the same hierarchy is typically used for two distinct purposes. Members of a senior role in the hierarchy inherit permissions from juniors. We call this the usage (or permissionusage) aspect of role hierarchies. Membership in a senior role also authorizes users to activate junior roles. For purpose of least privilege a user may choose to activate only a junior role on a particular occasion, leaving the senior roles dormant. We call this the activation (or role-activation) aspect of role hierarchies. In this paper we introduce and motivate the idea that there are useful situations where these two hierarchies should not be identical, and the activation hierarchy should extend the inheritance hierarchy. In particular we explore RBAC with respect to read-write access, and its relationship to traditional lattice-based access control or LBAC (also known as mandatory access control). More generally, we consider roles that are required to have dynamic separation of duty.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121951224","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Formal specification for role based access control user/role and role/role relationship management","authors":"S. Gavrila, John F. Barkley","doi":"10.1145/286884.286902","DOIUrl":"https://doi.org/10.1145/286884.286902","url":null,"abstract":"Role Based Access Control (RBAC), an access control mechanism, reduces the cost of administering access control policies as well as making the process less error-prone. The Admin Tool developed for the NIST RBAC Model manages user/role and role/role relationships stored in the RBAC Database. This paper presents a formal specification of the RBAC Database and Admin Tool operations. Consistency requirements for the RBAC Database are defined as a set of properties. Alternative properties, substantially simpler to verify in an implementation, are shown to be equivalent. In addition, the paper defines the semantics of Admin Tool operations, and shows that, given a consistent RBAC Database and an operation which meets specified conditions, the RBAC Database remains consistent after the operation is performed.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"37 11","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114024857","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Managing role/permission relationships using object access types","authors":"John F. Barkley, Anthony Cincotta","doi":"10.1145/286884.286901","DOIUrl":"https://doi.org/10.1145/286884.286901","url":null,"abstract":"The role metaphor in Role Based Access Control (RBAC) is particularly powerful in its ability to express access policy in terms of the way in which administrators view organizations. Much of the effort in providing administrative tools for RBAC has been devoted to tools for associating users with roles and roles with roles. This paper introduces the concept of an “Object Access Type” and describes the tool “RGP-Admin” for administering associations between roles and permissions using Object Access Types. RGP-Admin is applicable to most RBAC mechanisms and Access Control List mechanisms which support groups. A prototype demonstration of RGPAdmin was developed to illustrate how Object Access Types are used to manage associations between Windows NT groups, representing roles, and file permissions within the Windows NT File System.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"142 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116327102","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"An Oracle implementation of the PRA97 model for permission-role assignment","authors":"R. Sandhu, Venkata Bhamidipati","doi":"10.1145/286884.286889","DOIUrl":"https://doi.org/10.1145/286884.286889","url":null,"abstract":"In role-based access control (RBAC) permissions are associated with roles, and users are made members of appropriate roles thereby acquiring the roles’ permissions. Using RBAC to manage RBAC provides additional administrative convenience. ARBAC97 is an administrative model recently proposed by Sandhu et al [SBC+97]. In this paper we demonstrate the implementation of one of the components of ARBAC97 which deals with permission-role assignment and is called PRA97. Although PRA97 is quite different from that built into the Oracle database management system, we demonstrate how to use Oracle stored procedures to implement it.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127267472","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Role-based access control in Java","authors":"Luigi Giuri","doi":"10.1145/286884.286904","DOIUrl":"https://doi.org/10.1145/286884.286904","url":null,"abstract":"As the Java platform is becoming attractive and convenient for the construction of cross-platform clientserver applications, the problem of developing and managing effective security policies in that environment becomes critical. This paper analyzes the security features provided by the new Java platform in order to identify how it is possible to improve them by providing state-of-the-art role-based access control mechanisms.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133408890","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Role-based access control in telecommunication service management—dynamic role creation and management in TINA service environment","authors":"T. Hamada","doi":"10.1145/286884.286905","DOIUrl":"https://doi.org/10.1145/286884.286905","url":null,"abstract":"Security issues in telecommunication service management in Telecommunication Information Network Architecture (TINA) service environment is studied by using billing and Video on Demand (VoD) service session examples. Role-based access control is extended to address the needs of telecommunication service management. Security space represents session particpant’s security interests, and is a useful concept to describe separation of security interests in service session. To address the security issues of service composition and federation, algebraic role specification, strongly-roled system, and role mapping are studied.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128902876","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Towards a more complete model of role","authors":"C. Goh, A. Baldwin","doi":"10.1145/286884.286898","DOIUrl":"https://doi.org/10.1145/286884.286898","url":null,"abstract":"In order to manage the use of roles for the purpose of access control, it is important to look at attributes beyond the consideration of capability assignment. Fundamentally, a generic attribute description using a constraint-based approach will allow many of the important aspects of role, such as scope, activation and deactivation, to be included. Furthermore, the commonly accepted concept of role hierarchy is challenged from the point of view of subsidiarity in real organisations, with the suggestion that role hierarchy has limited usefulness that does not seem to apply widely.","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127805728","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Role based access control on MLS systems without kernel changes","authors":"D. Richard Kuhn","doi":"10.1145/286884.286890","DOIUrl":"https://doi.org/10.1145/286884.286890","url":null,"abstract":"Role based access control (RBAC) is attracting increasing attention as a security mechanism for both commercial and many military systems. This paper shows how RBAC can be implemented using the mechanisms available on traditional multi-level security systems that implement information flow policies. The construction from MLS to RBAC systems is significant because it shows that the enormous investment in MLS systems can be leveraged to produce RBAC systems. The method requires no changes to the existing MLS system kernel and allows implementation of hierarchical RBAC entirely through site configuration options. A single trusted process is used to map privileges of RBAC roles to MLS labels. Access is then mediated by the MLS kernel. Where C is the number of categories and d the depth of the role hierarchy, the number of roles that can be controlled is approximately","PeriodicalId":355233,"journal":{"name":"ACM Workshop on Role-Based Access Control","volume":"226 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1998-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124496699","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}