Scribd
Upload
8 views3 pages

Unit 5-Role Based Access Control (RBAC)

VMware's Role-Based Access Control (RBAC) is a security mechanism that assigns permissions to roles rather than individual users, streamlining user management. It involves predefined or custom roles that dictate user actions, with permissions defining specific capabilities. Users can be assigned to multiple roles, and permissions can be set individually or in sets, requiring administrative approval for assignment.

Uploaded by

clothestheticzz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views3 pages

Unit 5-Role Based Access Control (RBAC)

VMware's Role-Based Access Control (RBAC) is a security mechanism that assigns permissions to roles rather than individual users, streamlining user management. It involves predefined or custom roles that dictate user actions, with permissions defining specific capabilities. Users can be assigned to multiple roles, and permissions can be set individually or in sets, requiring administrative approval for assignment.

Uploaded by

clothestheticzz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

-:RBAC:-

In VMware, Role-Based Access Control (RBAC) is a security mechanism


that restricts system access to authorized users by assigning permissions to
specific roles rather than individual users, simplifying user management and
reducing administrative overhead.
Key Concepts:
 Roles:
Predefined or custom roles with specific permissions that determine what
actions a user can perform within the VMware environment.
 Permissions:
Specific capabilities or actions that a role grants, such as creating virtual
machines, managing networks, or accessing storage.
 Users:
Individuals or groups assigned to specific roles, inheriting the permissions
associated with those roles

The concept of role-based access control began with multi-user and multi-
application on-line systems pioneered in 1970’s. Introduces the concept of a role
and a permission. A permission is an association between a transformation
procedure and an object. A permission can be thought as an object-method pair
or a class-method pair in an object-oriented environment. A permission can be
thought as a table-query pair or a view, query pair in a database application.
Permissions are assigned to roles. Users are assigned to roles.
***************************************************************************

Roles
Few generalized roles in an organization:
OPERATIONS:
Operations based on user’s visibility access in an organizations data. Below
are the few examples:
Database – Update Insert Append
Objects- View, Read/Write
Delete Locks – Open Close
Reports – Create View Print
Applications - Read Write Execute
User Assignments:
 One user can be assigned to one or more roles.
 Also role can be assigned to one or more users.

Permission Set:
 A set of permissions can be assigned to users. Or System Admin can
be assigned individual permissions like Create, Read, Edit, Delete,
append, update.
 Admin can be assigned permissions based on user’s role, only after
having approval from organization.
 A permission can be assigned to one or more users (based on roles).
 Multiple permissions like CRED (Create, Read, edit, delete) can be
assigned to single role.

*************************************************************

You might also like