Privilege Authority Blog

A great tool I use frequently when creating and troubleshooting Privilege Authority Rules is Process Explorer, one of the suite of tools from SysInternal. It can be downloaded here.

I will take you through the example of allowing users to make changes in Device Manager.

Here I am going to run through the steps to create a rule which will allow users with restricted privileges to download and install Adobe Flash Player from the Adobe site.

When Flash Player is installed from 3rd party sites the installation process can be different and this rule will not necessarily work.

In this blog entry I wanted to talk about this community’s “Rules of Engagement” for Rules Exchange. We as a community need to collectively identify and agree on guidelines that would support our efforts to create rules with good applicability,  quality and security and to ensure they can be easily exchanged and consumed within the user community.

The guiding principle is “The simpler the better”. The intent is to keep it simple while instilling an authoritative trust in the Rules Exchange content and a sense of ownership within the community.

As you all know, we just released Privilege Authority 2.0 this week. It can be downloaded from http://www.scriptlogic.com/products/privilegeauthority/.

Users can draw lot of value from Privilege Authority through its rules that enable a domain administrator to selectively elevate privileges for users while ensuring the security of the infrastructure. So our priority is to help the Privilege Authority Community build a comprehensive set of highly needed rules that can in turn be used by the community.

Essentially support the idea of Content(Rules) By the Community for the Community.