The Experts below are selected from a list of 74829 Experts worldwide ranked by ideXlab platform
Seog Park - One of the best experts on this subject based on the ideXlab platform.
-
WAIM - OS-DRAM: a delegation administration model in a decentralized Enterprise Environment
Advances in Web-Age Information Management, 2006Co-Authors: Changwoo Byun, Seog ParkAbstract:In this paper, we propose an effective delegation administration model using the organizational structure. From a user-level delegation point of view, previous delegation models built on the (Administrative) Role-Based Access Control model cannot present the best solution to security problems such as the leakage of information and the abuse of delegation in a decentralized Enterprise Environment. Thus, we propose a new integrated management model of administration role-based access control model and delegation policy, which is called the OS-DRAM. This defines the authority range in an organizational structure that is separated from role hierarchy and supports a clear criterion for user-level delegation administration. Consequently, the OS-DRAM supports a decentralized user-level delegation policy in which a regular user can freely delegate his/her authority to other users within a security officer's authority range with-out the security officer's intervention.
-
task role based access control model
Information Systems, 2003Co-Authors: Sejong Oh, Seog ParkAbstract:There are many information objects and users in a large company. It is an important issue how to control user's access in order that only authorized user can access information objects. Traditional access control models-- discretionary access control, mandatory access control, and role-based access control--do not properly reflect the characteristics of Enterprise Environment. This paper proposes an improved access control model for Enterprise Environment. The characteristics of access control in an Enterprise Environment are examined and a task-role-based access control (T-RBAC) model founded on concept of classification of tasks is introduced. Task is a fundamental unit of business work or business activity. T-RBAC deals with each task differently according to its class, and supports task level access control and supervision role hierarchy. T-RBAC is a suitable access control model for industrial companies.
-
DBSec - An Integration Model of Role-Based Access Control and Activity Based Access Control Using Task
Data and Application Security, 2002Co-Authors: Seog ParkAbstract:Role-based access control (RBAC) and activity-based access control (ABAC) models are well known and recognized as a good security model for Enterprise Environment. (ABAC model is represented as ‘workflow’). But these models have some limitations to apply to Enterprise Environment. Furthermore, Enterprise Environment needs application both RBAC and ABAC models.
-
An Improved Administration Method on Role-Based Access Control in the Enterprise Environment
Journal of Information Science and Engineering, 2001Co-Authors: Seog ParkAbstract:Access control is a difficult security issue for Enterprise organizations. Role-based access control (RBAC) model is well known and recognized as a good security model for Enterprise Environment. Though RBAC is a good model, administration of RBAC including building and maintaining access control information remains a difficult problem in large companies. RBAC model itself does not tell the solution. Little research was done on practical ways to find the information that fills RBAC components such as role, role hierarchy, permission-role assignment, user-role assignment, and so on from the real world. In this paper we suggest the possibility of model-based administration of RBAC in an Enterprise Environment. Model-based administration methods allows security administrator to manage access control by GUI that supports graphical Enterprise model. If security administrator creates or changes some of components of graphical Enterprise model, then it is translated to RBAC schema information by administration tool. We focus on a practical way of deriving access control information from real world. It is a core of model-based administration. Here we show the derivation method and implementation experiences
-
Task-role based access control (T-RBAC) : An improved access control model for Enterprise Environment
Lecture Notes in Computer Science, 2000Co-Authors: Seog ParkAbstract:Companies today manage business information with computer systems and many users access it for their job functions. Companies need security mechanisms to effectively protect important information. Moreover they need to minimize the interruptions from security mechanisms that cause delays in the execution of business activities. It is a difficult problem. In this paper we analyze the requirements of access control in Enterprise Environment and propose classifications for job functions. We propose a improved access control model for Enterprise Environment through integration of role based access control and activity based access control model.
Hong Fan - One of the best experts on this subject based on the ideXlab platform.
-
Access Control Model Based on Enterprise Environment
Computer Engineering, 2005Co-Authors: Hong FanAbstract:Access control is an important measure to secure the information system in the Enterprise, but the existing access control models, suchas DAC, MAC, RBAC and TBAC, can’t fully meet the requirements of the Enterprise Environment, therefore this paper introduces a new accesscontrol model for Enterprise Environment, called task-role-based access control model (T-RBAC). In the end, an implementation framework is givenaccording to T-RBAC.
Sejong Oh - One of the best experts on this subject based on the ideXlab platform.
-
task role based access control model
Information Systems, 2003Co-Authors: Sejong Oh, Seog ParkAbstract:There are many information objects and users in a large company. It is an important issue how to control user's access in order that only authorized user can access information objects. Traditional access control models-- discretionary access control, mandatory access control, and role-based access control--do not properly reflect the characteristics of Enterprise Environment. This paper proposes an improved access control model for Enterprise Environment. The characteristics of access control in an Enterprise Environment are examined and a task-role-based access control (T-RBAC) model founded on concept of classification of tasks is introduced. Task is a fundamental unit of business work or business activity. T-RBAC deals with each task differently according to its class, and supports task level access control and supervision role hierarchy. T-RBAC is a suitable access control model for industrial companies.
Robert Hoeppe - One of the best experts on this subject based on the ideXlab platform.
-
NetObjectDays - Do We Need Components for Persistent Data Storage in the Java 2 Enterprise Environment
Objects Components Architectures Services and Applications for a Networked World, 2003Co-Authors: Stefan Böttcher, Robert HoeppeAbstract:Object-oriented applications that use the Java 2 Enterprise Environment (J2EE) and operate on any kind of data storage have to integrate access to persistent data, which is usually achieved by entity beans. However, the use of entity beans as components for persistent data storage has a number of drawbacks. Component level inheritance and dynamic querying are not supported appropriately, and the whole approach seems to be overweight. In order to overcome these weaknesses, we implemented a JCA-compliant resource adapter, which allows the use of Java Data Objects (JDO) instead of entity beans and introduces a lightweight, easy to use and powerful transparent persistence layer for the Java 2 Enterprise Environment.
-
Do we need components for persistent Data storage in the Java 2 Enterprise Environment
Lecture Notes in Computer Science, 2003Co-Authors: Stefan Böttcher, Robert HoeppeAbstract:Object-oriented applications that use the Java 2 Enterprise Environment (J2EE) and operate on any kind of data storage have to integrate access to persistent data, which is usually achieved by entity beans. However, the use of entity beans as components for persistent data storage has a number of drawbacks. Component level inheritance and dynamic querying are not supported appropriately, and the whole approach seems to be overweight. In order to overcome these weaknesses, we implemented a JCA 1 -compliant resource adapter, which allows the use of Java Data Objects (JDO) instead of entity beans and introduces a lightweight, easy to use and powerful transparent persistence layer for the Java 2 Enterprise Environment.
Stefan Böttcher - One of the best experts on this subject based on the ideXlab platform.
-
NetObjectDays - Do We Need Components for Persistent Data Storage in the Java 2 Enterprise Environment
Objects Components Architectures Services and Applications for a Networked World, 2003Co-Authors: Stefan Böttcher, Robert HoeppeAbstract:Object-oriented applications that use the Java 2 Enterprise Environment (J2EE) and operate on any kind of data storage have to integrate access to persistent data, which is usually achieved by entity beans. However, the use of entity beans as components for persistent data storage has a number of drawbacks. Component level inheritance and dynamic querying are not supported appropriately, and the whole approach seems to be overweight. In order to overcome these weaknesses, we implemented a JCA-compliant resource adapter, which allows the use of Java Data Objects (JDO) instead of entity beans and introduces a lightweight, easy to use and powerful transparent persistence layer for the Java 2 Enterprise Environment.
-
Do we need components for persistent Data storage in the Java 2 Enterprise Environment
Lecture Notes in Computer Science, 2003Co-Authors: Stefan Böttcher, Robert HoeppeAbstract:Object-oriented applications that use the Java 2 Enterprise Environment (J2EE) and operate on any kind of data storage have to integrate access to persistent data, which is usually achieved by entity beans. However, the use of entity beans as components for persistent data storage has a number of drawbacks. Component level inheritance and dynamic querying are not supported appropriately, and the whole approach seems to be overweight. In order to overcome these weaknesses, we implemented a JCA 1 -compliant resource adapter, which allows the use of Java Data Objects (JDO) instead of entity beans and introduces a lightweight, easy to use and powerful transparent persistence layer for the Java 2 Enterprise Environment.