Why it’s important

Privileged credentials are the keys to the IT kingdom. Administrators must be able to customize permissions and access to meet security requirements, and ensure that users can’t accidentally or intentionally change administrative settings they shouldn’t have rights to.

How this feature solves it

Role Based Access Control for Active Directory (RBAC AD) enables IT admins to control what individual users can do within Secret Server.

Use preset roles to get going fast: Secret Server password management software ships with out-of-the-box roles to solve common configurations that get you going quickly. Every user and group is assigned to one or more roles that define what they are able to do in the system.

Customize access to suit your organization: Secret Server fits into your organization’s role management strategy by restricting system access in a strategic, controlled manner, allowing custom roles to be created within the application that correspond to your organization’s structure.

Additional information about role based access security

Roles are made up of specific permissions which grant a user access to different features within the system. If an out-of-the-box role doesn’t suit you it can be modified or you can simply create a new one.

An example of role based access control use in Secret Server:
You need a monitoring team to be able to configure event alerts or view usage reports, but they shouldn’t actually have access to the privileged passwords. Within Secret Server you can grant granular access to those users so they only have access to the information they actually need. Later, you can quickly and easily revoke that access—and therein lies one of the finer benefits of RBAC.