A common complaint about the way Microsoft Windows handles privileges and security is that it remains ungranular and clumsy. For instance, if you put a user into a reduced-privilege context, it's hard to selectively allow them elevated privileges without changing their group memberships. If they need to run one application (or a set of apps) that requires admin rights, the administrator needs to contrive a way to allow them to run those programs with elevated privileges.
Although mechanisms exist for doing this in Windows, they are close-ended: You can either do something or you can't. It's difficult to carve out exceptions or grant one-time allowances for something.
A third-party solution to this problem is
Each program can be given one of four levels of control: deny, run as limited user, run as administrator or allow normally. The "deny" function doesn't rely on the type of blacklisting/application-image hashing technique used by Group Policy; if told to do so, it will block anything not specifically authorized by the administrator. (You can use hashes, filenames, owners or other methods to define allowed files.) This approach offers an auxiliary benefit: Since any application that isn't specifically allowed can be restricted, viruses and spyware have that much more difficulty getting a toehold.
Another key feature that isn't supported in Windows by default is the ability to get "run-time requests for permission." A user can attempt to launch an application, and if it's denied, they can petition an administrator to grant them the right to do so, immediately, without having their security policy rewritten. Admins can also "harvest" running applications from systems to see what people are using, and then build their restriction policies from that information. That way they can use real-time data and not guesswork or manually tabulated lists to get a handle on things.
A free evaluation version of the product, which runs totally unrestricted for 30 days, is available. Pricing varies based on the number of seats and servers needed, but a sample quoted price for one server and 25 workstations is $1100.
About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators.
More information from SearchWinSystems.com
- Tip: Tool takes away
privileges -- when you don't want them
- Topic: Administrative
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in May 2006