Blog

  • Customizing Roles For Your Company – Part Two

    In Part One of this two-part series we discussed setting custom Roles inside of Secret Server. In this section we will discuss the three ways to set Permissions on Secrets within Secret Server.

    Roles give a user the ability to perform actions inside Secret Server, whereas Permissions dictate the level of control a user has within Secret Server. There are three Permissions within Secret Server:

    1. View, which allows a user to see a Secret/Folder.
    2. Edit, which allows a user to change Secret/Folder information.
    3. Owner, the highest level of control which grants a user the ability to change advanced security settings for a Secret/Folder.

    Permissions can be bulk-assigned by Folder. By default Secrets inherit the Permissions of the Folder where it is created. This set up requires two steps. First, create a folder structure that is separated by Permission level. Typically, this would follow your company’s team structure. For example, you could configure folders in the hierarchy:

    • IT Management Team
      • Server Admins
        • Server Admins
    • Finance Management Team
      • Staff Accountants
        • Book Keepers

    Second, assign Permissions to each folder based on the users that need access to that information. Now, when a Secret is created inside a folder it will automatically be assigned the Permissions of that Folder.

    Permissions can be individually assigned to specific Secrets. When setting up Permissions in this way, Folders are used primarily as an organization tool and typically are named in a much more general manner, such as:

    • Servers
      • Windows Servers
      • LINUX / UNIX
      • Apache
    • Databases
      • MS SQL
      • MySQL
      • Oracle

    When assigning Permissions to individual Secrets, the Secret will not inherit Folder Permissions and can be placed in a Folder alongside Secrets that have different levels of Permissions. To ensure Secrets do not inherit Permissions from the Folder, update your product settings by going to Administration > Configuration and setting the Default Secret Permissions to “Only Creator Has Permissions to New Secrets”.

    Permissions can be bulk AND individually assigned. It is also possible to set up Secret Permissions through a combination of the options above. In this case, you would use the Folder to push Permissions to the Secrets through inheritance when a Secret is created. Once this is complete, Secrets do not have to stay within that Folder. Inheritance can be turned off for individual Secrets afterward to allow assignment of custom Permissions.

    Leave a reply →

Leave a reply

Cancel reply