Separation of duties and role-based access control in organizations
This assignment talks about the separation of duties and implementation of the Role based Access control policy. The discussion revolves around the organization needs to make their ventures more secure. Both of these mechanisms are discussed in more detail. Furthermore, this assignment talks about managing trust across different business networks.This assignment talks about the separation of duties and implementation of the Role based Access control policy. The discussion revolves around the organization needs to make their ventures more secure. Both of these mechanisms are discussed in more detail. Furthermore, this assignment talks about managing trust across different business networks.
✍️ How to write this paper — guide & tools ▾
User Access
It is crucial to study the structural behavior within organization so that the effectiveness of the organization can be improved. (Robbins & Judge, 2013) The employer needs to be aware of the duties and tasks within the organization so they can be managed in a proper way. Along with managing tasks and maintaining the work output, special care needs to be given to the security measures within the company. In the competitive world today, organizations are making using of the smallest information they can attain from their rival companies. Just recently, separation of duty and role based access control (RBAC) were discovered as the new mechanisms to improve the security measures within an organization.
Separation of Duties
Separation of duties is very important when it comes to keeping control. It appears that separation of duties is difficult and sometimes very difficult to manage. The main task is attained by dividing all the tasks and privileges among different people. (Coleman, 2008) Separation of duty is a security model utilized to formulate multi-person control policies. The major aim here is that two or more persons are selected for the completion of a certain task. The purpose behind this act is to reduce the incidence of fraud and cheating within the organization. In this way, there are more than one persons involved and the responsibility and authority of the act is spread over more than one person. (Simon & Zurko,1997) It should be noted that the idea of separation of duty must include the principle of user-centered security. (Simon & Zurko, 1996) Separation of duties also makes sure that critical decision making power does not reside with only one person within the organization.
Role-based access control (RBAC)
A role based access control (RBAC) policy establishes access control decisions on the duties and functions an individual has within the organization. This means that the users cannot give access permission to other users at their discretion. It should be noted that the RBAC method would simplify the management of permissions. To simplify this, the major aim here is to link permissions with roles. After doing that, certain users or user groups are made members or certain roles within the organization (S and Hu et al., 1996) A role basically represents a person's ability to carry out a certain task. This can also mean a responsibility or an authority within the organization.
A study carried out by NIST (Ferraiolo and Gilbert et al., 1995) states that RBAC goes on to satisfy many needs of the government and commercial sectors. This study showed that many organizations base their control decisions depending on the roles that the users have in the organization. If one looks at it in simpler terms, it is basically a system of checks and balances so that one person does not become very powerful in the company. It is quite simple that if the person attains unlimited power, he is more likely to carry out unfair practices in the organization. An example can be taken of an operator role where the person has the access to all the resources. Despite all of that, that person is allowed to access to change permissions. Similarly, a security officer can change permissions but not have access to the resources.
In this method, the users would be granted permissions only based on their job requirement. The RBAC method is also efficient because it might not cause as many conflicts in the organization. For instance, it is easy to predefine role-permission relationship. This makes it simpler to assign new employees to the roles that have been established before. The NIST study also indicated that the permissions assigned to roles change slowly. Administrators and employers can annul or award membership to users in existing roles without changing the role-permission assignments. This makes the entire organization more systematic and reduces chances of error. If employees are aware of their own roles and permissions, they will be less likely to try and attain permissions that are not linked to their duty. Because these employees know that they will not get other permissions, they will be more focused on their own work rather than looking around what his colleagues are doing.
In short, we see that RBAC policy supports the security principles of data abstraction, least privilege and separation of duties. All of these security principles will therefore make the entire organization more secure and efficient in the long run.
Trust management issues
Organizational behavior experts have pointed out that an organization member's actions can be altered by a lot of factors within the organization. Values and the attitude the person keeps has been considered very crucial in explaining their activities and attitude in the organization. A person's values would also affect their choices, alternatives, and performance measures in their decision process. (Lin & Chang, 2008; Robbins & Judge, 2013) Trust management can be viewed as maintaining security policies, assigning credential to entities and checking if the credentials complete the policy.
In the paper less business transactions being carried out today, trust management is very important. Organizations need to look over the complexity of access-restricting and access-granting processes. (Blaze et.al, 1999) One method utilizes for this purpose is the access control list. Strict confidentiality should be maintained through the precise access control. For instance, if the company is managing accounts and funds for a different set of clients, different attempts from users of all needs and levels will be going on. In these sorts of instances, we see that a programming language-based control structure will verify who is exactly asking for what.
A national accounting firm that is spread onto different network requires trust management that matches up to the level of complexity and scrutiny that is present. It is crucial to ensure that appropriate authorization is maintained and also that the authorizing body is also maintained. It is also necessary to set up an independent application that will compare requests with policies, verify identities, handle request and grant the access that is necessary. This sort of distribution trust management will therefore enable proper control over sensitive data within an organization (Damico, 2009).
Create your account
- Blaze, M., Ioannidis, J., Keromytis, A. and Feigenbaum, J. (1999). The role of trust management in distributed systems security. Computer Science Volume, 1603 pp. 185-210. [Accessed: 14 Sep 2013].
- Chang, H. and Lin, G. (2008). Effect of personal values transformation on leadership behaviour. Total Quality Management, 19 (1-2), pp. 67--77.
- Clark, D. and Wilson, D. (1987). A comparison of commercial and military computer security policies. 184 p. 194.
- Coleman, K. (2008). Separation of Duties and IT Security. [online] Retrieved from: http://www.csoonline.com/article/446017/separation-of-duties-and-it-security [Accessed: 14 Sep 2013]. ↗
- Damico, T. (2009). Distributed Trust Based Management: Who's Getting In?. Student Pulse, 1 (11).
- Ferraiolo, D. and Kuhn, D. (2009). Role-based access controls. arXiv preprint arXiv:0903.2171.
- Ferraiolo, D., Gilbert, D. and Lynch, N. (1995). An examination of federal and commercial access control policy needs. p. 107.
- Robbins, S. and Judge, T. (2013). Organizational Behavior. 15th ed. Pearson.
- S, Hu, R., Coyne, E., Feinstein, H. and Youman, C. (1996). Role-based access control models. Computer, 29 (2), pp. 38--47.
- Zurko, M. and Simon, R. (1996). User-Centered Security. [e-book] http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.136.7754&rep=rep1&type=pdf [Accessed: 14 Sep 2013]. ↗
Always verify citation format against your institution’s current style guide requirements.