The Roles category lets you view all available roles. A role is a basic precept of role-based security, a security architecture best practice. A role groups users according to their level of access authorization. Grouping users into roles simplifies administration and security policy.
In a role-based security implementation, access authorization to a resource is not given to the individual users who require access. Instead, roles are identified that have a common set of responsibilities and requirements. For each role, a group of users are identified who share the role. For example, all people in a specific job position can share the same set of responsibilities and have the same authorization requirements. The job position is identified as a role and the people in that job position are identified as sharing the role.
In a role-based security implementation, a security role is defined for a common set of authorization requirements. Access authorization is given once to the role, rather than individually to each user. The users who perform in the role are attached to the role in the security model. By being attached to the role, a user acquires all of the access authorizations that are given to the role. Users typically have a set of roles that they perform in their job function. The roles are attached to the corresponding set of roles in the security model.
When new users are provisioned, they are attached to the roles that correspond to their job requirements.
After you select a row of data, more granular information appears in the Details pane at the bottom of the Investigator.
Example: Identify roles for a new team member
A new security administrator has transferred to your team. Your manager has requested your assigned roles. Your manager wants the new person to have the same roles. You use the Investigator to identify the roles to which you are assigned. You can then export the list of roles to a comma-separated value (CSV) file.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|