BeyondTrust

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.

Some People Collect Stamps, I Collect Least Privilege Rules

Posted February 17, 2012    Peter McCalister

As I guide folks through setting up and using PowerBroker Windows Desktops I’m always thinking ahead, past the, ‘Phase 1′ deployment. A big part of this is sorting out your rule set, (Policies that dictate what elevation an application receives, or whether it is even allowed to execute), into collections.

A collection is a folder you create within your GPO where you put ‘like’ application rules into, or rules specific to a particular group. In other words, you may choose to create a collection for In-House created applications, or one containing a set of rules for Adobe software. In other cases, where you do need deeper control over who gets a set of rules, you can create a collection named after this group, for instance, Accounting, Engineering, Marketing, etc. In this latter case, you combine the convenience of collections with the control of Item-Level Targeting, just like what you use with MS Group Policy Preferences. I’ll cover this more in-depth in a future post. For now think of Item-Level Targeting like the Security Filtering available in the MS Group Policy Management Console on steroids.

Whether you are just starting out with PowerBroker Windows Desktops or have been using the software to either mitigate the risk associated with over-privileged users or reduce support costs with under-privileged ones for awhile, think about your enterprise and how you can use collections.

Do you have rules now that you put into a separate GPO because you need to make sure they only apply to certain situations?
Do you have a list of rules and are having trouble remembering what all of them deal with?

Maybe you’re like me and just need to put everything in it’s place. These are just a few of the reasons to use collections. If you want more information on applying collections to your environment, just give us a call; we’re here 24 hours a day/7 days a week.

Leave a Reply

Additional articles

How To Implement The Australian Signals Directorate’s Top 4 Strategies

Posted October 20, 2014    Morey Haber

The Australian Signals Directorate (ASD), also known as the Defence Signals Directorate, has developed a list of strategies to mitigate targeted cyber intrusions. The recommended strategies were developed through ASD’s extensive experience in operational cyber security, including responding to serious security intrusions and performing vulnerability assessments and penetration testing for Australian government agencies. These recommendations…

Tags:
, , , ,
asp-mvc

Exploiting MS14-059 because sometimes XSS is fun, sometimes…

Posted October 17, 2014    BeyondTrust Research Team

This October, Microsoft has provided a security update for System.Web.Mvc.dll which addresses a ‘Security Feature Bypass’. The vulnerability itself is in ASP.NET MVC technology and given its wide adoption we thought we would take a closer look. Referring to the bulletin we can glean a few useful pieces of information: “A cross-site scripting (XSS) vulnerability exists…

Tags:
4bestpracticesaudits-blog

Four Best Practices for Passing Privileged Account Audits

Posted October 16, 2014    Chris Burd

Like most IT organizations, your team may periodically face the “dreaded” task of being audited. Your process for delegating privileged access to desktops, servers, and infrastructure devices is a massive target for the auditor’s microscope. An audit’s findings can have significant implications on technology and business strategy, so it’s critical to make sure you’re prepared…

Tags:
, , , ,