Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Organizing your PowerBroker Desktops Rules

Posted October 20, 2012    Peter McCalister

When tackling a project to remove administrator privileges from users, it is critical to understand what applications and tasks will be impacted. Some things just break or won’t function properly when users are no longer administrators. Of course, PowerBroker Desktops is designed to elevate those apps and tasks that require administrator privileges so that there is no impact on end user productivity. PowerBroker Desktops has the ability to automatically discover apps in your environment that require administrator privileges so that most of the work is done for you. During the audit, you may discover dozens of apps in your environment that require administrator privileges, but some apps may only be needed by certain departments or certain individuals. PowerBroker Desktops provides you with the most comprehensive organization capabilities to simplify the management of your rule set, and make it as easy and intuitive as managing the Windows file system.

There are several different ways to organize your policies, and due to the capabilities that PowerBroker Desktops provides, the sky is the limit on how you decide to organize your rules. In this blog post, I’ll discuss several common ways of organizing your rules.
One way to organize your rules in a flat format. All the rules are simply placed in in one Group Policy Object (GPO), linked at a high level in Active Directory (AD) and applied to everyone in the organization.

You can still use Item-Level Targeting to filter the rules to groups of users based on a number of different criteria like IP Address Range, Site, OU, hardware profile, etc. Item-Level Targeting can be applied to Collections and to individual rules as well.

The downside to this design is that it is difficult to find rules in what could be a lengthy list, and it is also makes it hard to figure out just who is getting what rules.

A better way is to use Collections to organize your rules, much like you use folders to organize your files in Windows. You can use Collections to organize your rules based on what you want them to do. To do this, you simply select the action when you configure your collection.

You can do this for each action you wish to implement, and all of the rules that you place into the collections will inherit the action from its collection.

You can take Collections even further by organizing by Role and then by Action.

collections, no action is enforced, it is simply a folder, but in the second level of collections, actions do get enforced. So, in this example, the “Sales” collection is a container that sets no action and the second level folders, like “Elevate” would enforce an action. All rules placed in the second level folder would inherit the action specified at its collection level.

Additionally, you will want to apply Item-Level Targeting at the first level collection, like “Sales” to target all child Collections and Rules to the Sales Group.

You can go even further with Collections, because there is no limit to how many Collections you can nest. Take a look at this screenshot where I am organizing based on Location, then by Role, then by Action, then by type of application:

Keep in mind that all of the Collections and rules can have Item-Level Targeting applied so that no matter complex your environment is currently organized, PowerBroker can fit.

As I mentioned earlier, the sky is the limit. With the unique organizational capabilities that Collections, Actions, and Item-Level Targeting provide, PowerBroker Desktops makes managing even the largest sets of rules easy.


Leave a Reply

Additional articles

VMware Hardening Guidelines-img3

How to Audit VMware ESX and ESXi Servers Against the VMware Hardening Guidelines with Retina CS

Posted February 27, 2015    BeyondTrust Research Team

Retina CS Enterprise Vulnerability Management has included advanced VMware auditing capabilities for some time, including virtual machine discovery and scanning through a cloud connection, plus the ability to scan ESX and ESXi hosts using SSH. However, in response to recent security concerns associated with SSH, VMware has disabled SSH by default in its more recent…

, , , ,

Privileged Passwords: The Bane of Security Professionals Everywhere

Posted February 19, 2015    Dave Shackleford

Passwords have been with us since ancient times. Known as “watchwords”, ancient Roman military guards would pass a wooden tablet with a daily secret word engraved from one shift to the next, with each guard position marking the tablet to indicate it had been received. The military has been using passwords, counter-passwords, and even sound…

, , ,
Privileged Account Management Process

In Vulnerability Management, Process is King

Posted February 18, 2015    Morey Haber

You have a vulnerability scanner, but where’s your process? Most organizations are rightly concerned about possible vulnerabilities in their systems, applications, networked devices, and other digital assets and infrastructure components. Identifying vulnerabilities is indeed important, and most security professionals have some kind of scanning solution in place. But what is most essential to understand is…

, , , , ,