The what, how and why of Role Based Access Control (RBAC)
06 February 2012
Download Type: Adobe PDF
In the world of identity and access management, Role Based Access Control (RBAC) is gradually becoming a frequently used term. Dictated in part by legislative and regulatory norms, an increasing number of organizations wish to manage and assign all access privileges across the network in a structured way. This is possible through the use of RBAC software. So how can companies achieve an adequate implementation of RBAC across their entire organization?
Organizations are faced with two pitfalls when it comes to assigning and revoking access privileges. To assign privileges, they often create a copy of a colleague’s account, also known as ‘template user’. This creates the risk that new employees are provided with unwarranted access to business applications and systems. Added to which, organizations do not pay sufficient attention to revoking privileges when they create copies of existing user accounts. After all, their most important consideration is enabling new employees to do their job rather than checking for excess access privileges. Dictated by standards, IT auditors and unnecessary licensing costs for suites including Microsoft Visio, Projects and Adobe CS, organizations have come to acknowledge the importance of a responsible handling of authorizations. RBAC may just be the solution for them.
In this white paper we will explain the nature of Role Based Access Control, how it can be optimally implemented across the organization and what approach Tools4ever uses to this end..
Already registered? Click the button below to login.