Advanced security

While this example fits for large enterprises, please keep in mind that any privilege should be granted only as necessary. Be careful when granting permissions to a user or a user group. Our fictional company, Windjammer, has three user groups: HelpDesk, ServiceDesk, and Consultants. There are two client companies: Downhill Pro and Telemark.

The following tree view structure represents entries which users have access to once all permissions are set:

Here is an example of user configuration. To create users, navigate to Administration – Users – Add User.

Here we select the user type to give them the most basic rights (Add, Edit, and Delete).

ServiceDesk users are Restricted users. They have the Add and Edit rights. However, they cannot add entries into the vault folder.

HelpDesk users are Restricted Users as well. They only have the Add right. However, they cannot add entries into the vault folder.

Consultants are Read Only Users and can only view a subset of entries. They cannot add or edit anything.

Now that the users are created, we will add the user groups which we will later grant the permissions to. We need to create the user groups and assign the respective user to each user group. There is no need to grant any privilege to these user groups since they are mainly empty shells used to group multiple users. This allows for controlling multiple users at once instead of granting permissions to each users, one at a time.

• ServiceDesk

• HelpDesk

• Consultants

To add a user group, click the Add User Group button, enter a name for the user group, and click Ok.

To assign users to a user group, select a user group and click the Assign User Groups button. Use the Is Member check boxes to add users to the user group.

Now, everything is ready to grant or deny access to the user groups.

• All vault folder permissions are set to Never. By inheritance, this denies the child items default access to everyone.

• The ServiceDesk has the permission to view and open all entries but is able to edit only the entries in the client's groups/folders.

• The HelpDesk has the permission to view and open entries in the client's groups/folders only and is not able to edit them.

• The Consultants have the permission to view and open entries in the Montreal folder only but is not able to edit it or its child items.

Vault Settings As mentioned above, ALL vault settings folder permissions are set to Never. This denies the default access to other users.

Windjammer Downhill Pro, and Telemark, the vault level groups/folders The permission to view the Windjammer folder is set for the ServiceDesk only since we want them to be able to use the child entries. We do not want the ServiceDesk to add, edit or delete anything. We leave the Add, Edit, and Delete permissions to Inherited so only the administrators can perform these action on the Windjammer folder and its child items.

• View: Custom; ServiceDesk.

• Add: Inherited; Never inherited from vault. Only the administrator can add entries.

• Edit: Inherited; Never inherited from vault. Only the administrator can edit entries.

• Delete: Inherited; Never inherited from vault. Only the administrator can delete entries.

• Move: Inherited; Never inherited from vault. Only administrators can move entries.

• View password: Inherited; Never inherited from vault. Only administrators can view password.

• View sensitive information: Inherited; Never inherited from vault. Only administrators can view sensitive information.

• Connect (Execute): Inherited; Never inherited from vault. Only administrators can connect (execute).

For Downhill Pro, we grant permissions to the ServiceDesk and the HelpDesk.

• View: Custom; HelpDesk, ServiceDesk.

• Add: Custom; ServiceDesk.

• Edit: Custom; ServiceDesk.

• Delete: Inherited; Never inherited from vault. Only the administrator can delete entries.

• Move: Inherited; Never inherited from vault. Only administrators can move entries.

• View password: Inherited; Never inherited from vault. Only administrators can view password.

We already have a good example of the flexibility of Remote Desktop Manager Security. ServiceDesk and HelpDesk users can view and use all the entries in the Downhill Pro folder, even the credential entries, but they will never see any passwords since the ServiceDesk and HelpDesk users do not have the privilege to reveal passwords.

Next, for the Telemark folder, we grant permissions to the ServiceDesk, the HelpDesk and the Consultants. This is where things get complex. If we want the Consultants to be able to view only the Montreal folder, which is a child item of Telemark, we must grant Consultants the permission to view the parent folder, thereby the entire Telemark content. Then we will grant permissions on child items only to the user group that should have access to these items. This last step will deny the view permission for the Consultants on the child items.

• View: Custom; Consultants, HelpDesk, ServiceDesk.

• Add: Custom; ServiceDesk.

• Edit: Custom; ServiceDesk.

• Delete: Inherited; Never inherited from vault. Only the administrator can delete entries.

• Move: Inherited; Never inherited from vault. Only the administrator can move entries.

• View password: Inherited; Never inherited from vault. Only administrators can view password.

• View sensitive information: Inherited; Never inherited from vault. Only administrators can view sensitive information.

Telemark Child Items Since we want the users to be able to use the credential entries, we grant the ServiceDesk and the HelpDesk the permission to view the Credentials folder. Therefore, the ServiceDesk and HelpDesk are able to use the entries in the folder without revealing the passwords. By specifying that only the HelpDesk and ServiceDesk have the View permission, we deny the view access to any user group or user that is not on the list of the permission.

The Add and Edit permissions are set to Never and the Delete permission can be left to Inherited since it inherits the Never settings from the vault. Only the administrators can perform these actions in groups/folders containing credentials.

• View: Custom; HelpDesk, ServiceDesk.

• Add: Never; Only administrators can add credential entries.

• Edit: Never; Only administrators can edit entries.

• Delete: Inherited; Never inherited from vault. Only administrators can delete entries.

• Move: Inherited; Never inherited from vault. Only administrators can move entries.

• View password: Inherited; Never inherited from vault. Only administrators can view password.

• View sensitive information: Inherited; Never inherited from vault. Only administrators can view sensitive information.

• Connect (Execute): Inherited; Never inherited from vault. Only administrators can connect (execute).

We want the ServiceDesk to be able to use the Domain admin credential entry, but not the HelpDesk. For this, we must grant the View permission to the ServiceDesk. The ServiceDesk is still be able to use the credential entry but will never see the password.

• View: Custom; ServiceDesk.

• Add: Inherited; Never inherited from vault. Only administrators can add credential entries.

• Edit: Inherited; Never inherited from vault. Only administrators can edit credential entries.

• Delete: Inherited; Never inherited from Telemark\Credentials. Only administrators can delete credential entries.

• Move: Inherited; Never inherited from vault. Only administrators can move entries.

• View password: Inherited; Never inherited from vault. Only administrators can view password.

• View sensitive information: Inherited; Never inherited from vault. Only administrators can view sensitive information.

• Connect (Execute): Inherited; Never inherited from vault. Only administrators can connect (execute).

The last step for the Telemark child items is to set the View permission to the ServiceDesk and the HelpDesk on the Boston folder and leave every other permissions of this folder to Inherited. This denies the Consultants to view the Boston folder. Now, the Consultants are able to view and open entries only in the Montreal folder.

• View: Custom; HelpDesk, ServiceDesk.

• Add: Inherited; ServiceDesk inherited from Telemark.

• Edit: Inherited; ServiceDesk inherited from Telemark.

• Delete: Inherited; Never inherited from vault.

• View password: Inherited; Never inherited from vault. Only administrators can view password.

• View sensitive information: Inherited; Never inherited from vault. Only administrators can view sensitive information.

There is no need to set any permissions on the Montreal folder, since they all inherit values from parent folders.

The permissions are now correctly set. Note that every entry added at vault level are inheriting from the vault as well. This means they would be available to admins only, unless their permissions were modified. This can be confirmed by looking at the screenshot below, in which the entry Daily routine is available for everyone (its permissions have been changed to Everyone). Here is what each user should see in the tree view:

You can further customize permissions by using the Security Settings section when editing entries. As always, great care must be taken when granting permissions.