Results 1 - 10
of
18
TRBAC: A Temporal Role -based Access Control Model
- ACM Transactions on Information and System Security (TISSEC
, 2001
"... A temporal RBAC (TRBAC) model has recently been proposed that addresses the temporal aspects of roles and trigger-based role enabling. However, it is limited to constraints on enabling of roles only. We propose a Generalized Temporal Role Based Access Control model (GTRBAC) that is capable of expres ..."
Abstract
-
Cited by 25 (14 self)
- Add to MetaCart
A temporal RBAC (TRBAC) model has recently been proposed that addresses the temporal aspects of roles and trigger-based role enabling. However, it is limited to constraints on enabling of roles only. We propose a Generalized Temporal Role Based Access Control model (GTRBAC) that is capable of expressing a wider range of temporal constraints. GTRBAC is capable of expressing periodic as well as duration constraints on roles, user-role assignments and role-permission assignments. In GTRBAC, temporal constraints on role enablings and role activations can be separately specified. A user-activated role can further be restricted to various activation constraints such as cardinality constraint or maximum active duration constraint within a specified interval. The GTRBAC model extends the synta ctic structure of TRBAC model and its event and trigger expressions subsume those of TRBAC. Portions of this work were supported by the sponsors of the Center for Education and Role based access control (RBAC) models have generated great interest in the security community as a powerful and generalized approach to security [2, 13, 16, 18, 19]. In RBAC,
Access Control to Information in Pervasive Computing Environments
, 2003
"... Many types of information available in a pervasive computing environment, such as people location information, should be accessible only by a limited set of people. Some properties of the information raise unique challenges for the design of an access control mechanism: Information can emanate from ..."
Abstract
-
Cited by 21 (3 self)
- Add to MetaCart
Many types of information available in a pervasive computing environment, such as people location information, should be accessible only by a limited set of people. Some properties of the information raise unique challenges for the design of an access control mechanism: Information can emanate from more than one source, it might change its nature or granularity before reaching its final receiver, and it can flow through nodes administrated by different entities. We propose three design principles for the architecture of an access control mechanism: (1) extract pieces of information in raw data streams early, (2) define policies controlling access at the information level, and (3) exploit information relationships for access control. We describe an example architecture in which we apply these principles. We also report how our earlier work about adding access control to a people location service contributed to the more general access control architecture proposed here.
Conflict Checking of Separation of Duty Constraints in RBAC - Implementation Experiences
- In Proc. of the Conference on Software Engineering (SE
, 2004
"... Separation of duty constraints define mutual exclusion relations between two entities (e.g. two permissions). Thus, a software component that supports the definition of separation of duty constraints implicitly requires a means to control their definition and to ensure the consistency of the resulti ..."
Abstract
-
Cited by 11 (6 self)
- Add to MetaCart
Separation of duty constraints define mutual exclusion relations between two entities (e.g. two permissions). Thus, a software component that supports the definition of separation of duty constraints implicitly requires a means to control their definition and to ensure the consistency of the resulting runtime structures. In this paper, we present our experiences with the implementation of conflict-checking methods for separation of duty constraints in the XORBAC access control service.
Context-Aware Role-based Access Control in Pervasive Computing Systems
- SACMAT’08 Proceedings of the 13th ACM Symposium on Access control Models and Technologies
, 2008
"... In this paper we present a context-aware RBAC (CA-RBAC) model for pervasive computing applications. The design of this model has been guided by the context-based access control requirements of such applications. These requirements are related to users ’ memberships in roles, permission executions by ..."
Abstract
-
Cited by 11 (5 self)
- Add to MetaCart
In this paper we present a context-aware RBAC (CA-RBAC) model for pervasive computing applications. The design of this model has been guided by the context-based access control requirements of such applications. These requirements are related to users ’ memberships in roles, permission executions by role members, and context-based dynamic integration of services in the environment with an application. Context information is used in role admission policies, in policies related to permission executions by role members, and in policies related to accessing of dynamically interfaced services by role members. The dynamic nature of context information requires model-level support for revocations of role memberships and permission activations when certain context conditions fail to hold. Based on this model we present a programming framework for building contextaware applications, providing mechanisms for specifying and enforcing context-based access control requirements.
On the Role of Roles: from Role-Based to Role-Sensitive Access Control
, 2004
"... This paper maintains that for an access-control mechanism to support a wide range of policies, it is best to dispense with any built-in semantics for roles in the mechanism itself, leaving such semantics to be defined by particular policies. ..."
Abstract
-
Cited by 9 (3 self)
- Add to MetaCart
This paper maintains that for an access-control mechanism to support a wide range of policies, it is best to dispense with any built-in semantics for roles in the mechanism itself, leaving such semantics to be defined by particular policies.
Experiences with the Enforcement of Access Rights Extracted from ODRL-based Digital Contracts
- In Proc. of the 3rd ACM Workshop on Digital Rights Management (DRM
, 2003
"... In this paper, we present our experiences concerning the enforcement of access rights extracted from ODRL-based digital contracts. We introduce the generalized Contract Schema (CoSa) which is an approach to provide a generic representation of contract information on top of rights expression language ..."
Abstract
-
Cited by 9 (2 self)
- Add to MetaCart
In this paper, we present our experiences concerning the enforcement of access rights extracted from ODRL-based digital contracts. We introduce the generalized Contract Schema (CoSa) which is an approach to provide a generic representation of contract information on top of rights expression languages. We give an overview of the design and implementation of the xoRELInterpreter software component. In particular, the xoRELInterpreter interprets digital contracts that are based on rights expression languages (e.g. ODRL or XrML) and builds a runtime CoSa object model. We describe how the xoRBAC access control component and the xoRELInterpreter component are used to enforce access rights that we extract from ODRL-based digital contracts. Thus, our approach describes how ODRL-based contracts can be used as a means to disseminate certain types of access control information in distributed systems.
An Approach to Extract RBAC Models from BPEL4WS Processes
- Processes, (2004), in Proceedings of the 13 th IEEE International Workshops on Enabling Technologies: Infrastructures for Collaborative Enterprises (WET ICE 2004
, 2004
"... The Business Process Execution Language for Web Services (BPEL) has become the defacto standard for Web Service composition. Yet, it does not address security aspects. This paper is concerned with access control for BPEL based processes. We present an approach to integrate Role-Based Access Control ..."
Abstract
-
Cited by 9 (1 self)
- Add to MetaCart
The Business Process Execution Language for Web Services (BPEL) has become the defacto standard for Web Service composition. Yet, it does not address security aspects. This paper is concerned with access control for BPEL based processes. We present an approach to integrate Role-Based Access Control (RBAC) and BPEL on the meta-model level. Moreover, we show that such an integration can be used to automate steps of the role engineering process. In particular, we extract RBAC models from BPEL processes and present an XSLT converter that transforms BPEL code to the XML import format of the xoRBAC software component. 1.
Role-Based Access Control in Ambient and Remote Space
, 2004
"... In the era of Ubiquitous Computing and world--wide data transfer mobility, as an innovative aspect of professional activities, imposes new and complex problems of mobile and distributed access to information, services, and on--line negotiations for this purpose. This paper restricts itself to presen ..."
Abstract
-
Cited by 6 (0 self)
- Add to MetaCart
In the era of Ubiquitous Computing and world--wide data transfer mobility, as an innovative aspect of professional activities, imposes new and complex problems of mobile and distributed access to information, services, and on--line negotiations for this purpose. This paper restricts itself to presenting a distributed and location--dependent RBAC approach which is multi--layered. Also an adapted form of Administration Nets [24] is presented which allows the scheduling of distributed on--line processes for automated location-- dependent negotiating procedures, and for proving their correctness. Examples are discussed in some detail.
Avoiding Privacy Violations Caused by Context-Sensitive Services
- IN: PROCEEDINGS OF 4TH IEEE INTERNATIONAL CONFERENCE ON PERVASIVE COMPUTING AND COMMUNICATIONS, PERCOM 2006
, 2006
"... The increasing availability of information about people's context makes it possible to deploy context-sensitive services, where access to resources provided or managed by a service is limited depending on a person's context. For example, a location-based service can require an individual to be at a ..."
Abstract
-
Cited by 6 (1 self)
- Add to MetaCart
The increasing availability of information about people's context makes it possible to deploy context-sensitive services, where access to resources provided or managed by a service is limited depending on a person's context. For example, a location-based service can require an individual to be at a particular location in order to let the individual use a printer or learn her friends' location. However, constraining access to a resource based on confidential information about a person's context could result in privacy violations. For instance, if access is constrained based on a person's location, granting or rejecting access will provide information about this person's location and could violate the person's privacy. We introduce an accesscontrol algorithm that avoids privacy violations caused by context-sensitive services. Our algorithm exploits the concepts of access-rights graphs, which represent all the information that needs to be collected in order to make a contextsensitive access decision. Moreover, we introduce hidden constraints, which keep some of this information secret and thus allow for more flexible access control. We present a distributed, certificate-based access-control architecture for context-sensitive services that avoids privacy violations, a sample implementation, and a performance evaluation.
Object-based and class-based Composition of Transitive Mixins
- Information and Software Technology
, 2007
"... doi:10.1016/j.infsof.2006.10.001 ..."

