Using an underlying role-based model for the administration of roles has proved itself to be a successful approach. This paper sets out to describe the enterprise role-based access control model (ERBAC) in the context of SAM Jupiter, a commercial enterprise security management software 1 . We provide an overview of the role-based conceptual model underlying SAM Jupiter. Having established this basis, we describe how the model is used to facilitate a role-based administration approach. In particular, we discuss our notion of 'scopes', which describe the objects over which an administrator has authority. The second part provides a case study based on our real-world experiences in the implementation of role-based administrative infrastructures. Finally, a critical evaluation and comparison with current approaches to administrative role-based access control is provided.  Categories and Subject Descriptors General Terms Management, Security Automated identity management, security provisioning, security administration, role-based access control (RBAC), enterprise role-based access control (ERBAC), enterprise roles, administrative role-based access control (ARBAC), scopes, SAM Jupiter 1 SAM Jupiter was developed by Systor Security Solutions and was recently taken over by Beta Systems Software AG.
Similarly, in the ERBAC model, proposed by Kern et al. scopes are used to define over which RBAC objects and administrator has authority REF .
An administration concept for the enterprise role-based access control model
SACMAT '03
Computer Science