madison

Top 5 challenges of least privilege for Windows

Mark Austin, Avecto, Special to ZDNet | June 29, 2010 11:41 AM PDT

Summary

Removing admin rights helps organizations eliminate accidental or deliberate misuse, decrease the risks posed by malware and reduce the cost of supporting the corporate desktop, says Avecto's Mark Austin.

Commentary - For enterprise Windows users, having administrative rights gives them complete and total control over the security of their desktops - a scenario that is far from ideal and far too common in most corporate environments. Removing administrative rights helps organizations to eliminate the accidental or deliberate misuse of these privileges, decreases the risks posed by malware and reduces the cost of supporting the corporate desktop.

Despite these benefits, removing administrative rights brings its own set of operational challenges, which is why many organizations have struggled to embrace it. The goal for these organizations is to achieve least privilege security to enable users to install and run only those applications that they need to perform their job role. However, because there is no mechanism in Windows to assign privileges directly to applications, most organizations face the decision of either running users insecurely with full administrative privileges, or removing administrative rights entirely and facing a new set of operational challenges.

Here are five common challenges that lead to organizations to grant users administrative privileges on Windows desktops.

1. Legacy Applications: Since most organizations have hundreds or thousands of applications, it is common for them to have several applications that won't run correctly under a standard user account. Many of these applications may have been internally developed and are no longer maintained, with redevelopment of the application being too costly. A similar problem may exist for off-the-shelf applications, if an organization is continuing to use a product that is no longer supported and an upgrade is not a viable option. If it is not possible to redevelop or upgrade legacy applications, then the only alternative is to either weaken security permissions on files and registry keys to allow the application to function under a standard user account, or to virtualize the application with a suitable application virtualization solution. The latter is a more secure solution, as weakening system security can leave the computer more open to attack.

2. Basic Administration Tasks: Many users perform basic system administration tasks for themselves, such as connecting printers, adding plug-and-play hardware and defragmenting disks. Although this is particularly common for laptop users, it can affect desktop users too, especially those in a more technical role. If a user is not granted administrative privileges over their computer, then the only option is over-the-shoulder administration. This means that the user must log a help desk call to perform even the most mundane administration tasks. This can be extremely frustrating for users, and the loss of productivity is costly to the organization, especially for remote laptop users.

3. Software Installation and Upgrade: In cases where some or all software packages are not centrally deployed and updated, least privilege becomes problematic, as most software requires administrative rights to install. If a user needs to install software as part of their job role, then it is extremely difficult to remove administrative rights from them, as the only other option becomes over-the-shoulder administration, leading to loss of productivity and increased support costs.

4. ActiveX Installation and Upgrade: Most ActiveX controls will require administrative privileges to be installed or upgraded. The inability of a user to install or upgrade authorized ActiveX controls for themselves is a major headache, as alternative deployment strategies are costly and time consuming. In addition, some ActiveX controls have licensing restrictions, which prohibit repacking of the control, in order to deploy it via a software deployment solution.

5. Advanced Tools: The more technical users in an organization will often run privileged applications as part of their role. These are applications that don't fall under the legacy applications category, as they are applications that genuinely require administrative rights to function correctly. Unlike legacy applications, virtualizing these applications is not a solution, as this will either cause the application to break due to the virtualization of its operations, or the virtualized application will still require administrative privileges. Users who run advanced tools are the most difficult users to move to a standard user account without severely limiting their ability to perform their job function.

The security and operational benefits of moving to least privilege are well documented, but most organizations find themselves in the position where it would be a difficult and costly undertaking, or it would lead to severe productivity issues for some or all of their users. The key is to understand what least privilege really means, as it is not about locking down the desktop completely. It is about running applications with the minimal privileges they require to function correctly. Unfortunately, privileges are assigned to users and not applications on Windows desktops, which is the root cause of the problem.

There are a number of third-party solutions available that resolve this limitation in Windows by allowing privileges to be assigned directly to the individual applications that require them. These solutions take much of the pain out of implementing a least privilege environment, as it is possible to remove administrative rights from users and still allow users to run legacy applications, perform basic administration tasks, install authorized software, install ActiveX controls, and perform any other privileged activity. Least privilege is about flexible desktop lockdown, where applications receive the privileges they require, with the user running under a standard user account. This provides a balance between security and operational costs, while maximizing user productivity.

biography
Mark Austin is co-founder and chief technology officer of Avecto (www.avecto.com), a leading provider of least privilege management solutions for Microsoft Windows systems.

Talkback Most Recent of 11 Talkback(s)

  • Good article
    It's a shame that this kind of thing was not addressed earlier on with Microsoft. It is very difficult to properly lock down a Windows system.
    ZDNet Gravatar
    happyharry_z
    29th Jun 2010
  • RE: Top 5 challenges of least privilege for Windows
    The "Power User" role is supposed to serve this function, but it doesn't because Windows security is juvenile. Part of the problem is that files created by a user need to be secured by that user, not secured through the file system by location. If they did their security like Unix a Power User would be able to install programs nearly anywhere in the system as long as they didn't edit or alter files they didn't own. They could setup printers safely. Plus when a profile was removed, there would be the option to delete all files that user owns from all locations.
    ZDNet Gravatar
    Socratesfoot
    29th Jun 2010
  • Except for number four these aren't unique to Windows.
    Though I am able to add a local printer without being an administrator.
    ZDNet Gravatar
    ye
    29th Jun 2010
  • Not so true on Active-X controls
    Vista and Windows 7 Pro both have an Active-X installer service. On Vista pro it's not there by default and has to be installed. On 7 pro it is there by default. Once this service is running on the PC, the administrators can configure the service via group policy.

    The group policy settings allow the admins to create a list of trusted URLs from which the user is allowed to install Active-X controls. This can even be set to happen silently.

    Now, if only I could do that for Acrobat and flash updates....
    ZDNet Gravatar
    cornpie
    29th Jun 2010
  • windows does it
    I apologize to the author if I am wrong but this text reeks of market speech and pushing one's agenda. The text goes round and round in circles trying to push the idea that you need extra tools to accomplish complex user security settings in a modern windows environment. Well, maybe this was true some years ago (think of win NT) but not so much these days, with win2008R2 and windows 7. The text sounds dated and very biased.

    EDIT:
    The fact that some organizations have poor role and identity management coupled with poor windows policy (user and workstation) management does not mean that the windows based systems are broken. Sorry guys but you simply either do not know how to do it or do not have the time and resources to do it properly.
    ZDNet Gravatar
    nkanada
    30th Jun 2010
  • RE: Top 5 challenges of least privilege for Windows
    Have you thought about problem applications that need admin rights to run..? there are over 70 settings in Win 7 that need admin rights happy ....
    ZDNet Gravatar
    Jenson B
    30th Jun 2010
  • very true
    I work for a large corp and we have dozens of apps that need admin rights to run .. Windows 2008 R2 or Win 7 does NOT solve this despite some comments in this thread to the contrary!
    ZDNet Gravatar
    Jenson B
    30th Jun 2010
  • Agreed
    I support about 70 laptop users, mostly Windows 7 Enterprise and a couple of Vista Enterprise/Business. I prefer to give them admin rights on a properly set up system, with remote access, and proper instruction and regulations regarding technical and regulatory issues.

    A positive factor in my case is that most of the users I support are responsible people (lawyers, physicians, HR managers) who don't tend to do foolish things, and do tend to take their responsibilities seriously. Users are also informed that they are given administrative privileges as exactly that - a privilege; abusing it (by installing illegal software, for example) will result in having their admin rights revoked.

    In fact, if I have to be honest, the most messed up system in the company is probably mine. happy
    ZDNet Gravatar
    Daniel Breslauer
    30th Jun 2010
  • MS is slowly improving this issue
    With Windows 7 (and Vista) the ability to install printers can be delegated to the user, but not all the additional glitz that so many printer setups attempt to add.

    Using Application Compatibility shims can fix most applications that insist on admin rights.

    Running standard maintenance tools should be automated, scheduled and audited. Yes it requires someone to administer, but taking the time to setup can save issues down the road.

    The biggest issue is how to convince people that they do not need to be installing all their cute personally purchased applications on company systems.
    ZDNet Gravatar
    pjboyles
    1st Jul 2010
  • Actually, Microsoft does not address the issue of least privilege...
    @peter.j.boyles@... Microsoft did attempt to solve least privilege in Windows Vista Beta, but Vista and 7 provide no solutions for least privilege. UAC, AppLocker, etc provide no solution for users that need to run applications, features, and installating key applications/activeX controls. There are many solutions that solve this, the longest player in the industry is BeyondTrust PowerBroker, which used to be owned by DesktopStandard (creator of the now Microsoft Group Policy Preferences released in 2007). PowerBroker is a Group Policy extension that EASILY creates policies for all applications, features, ActiveX controls for all standard users.

    Derek Melber, MVP Group Policy
    ZDNet Gravatar
    derekmelber
    21st Feb
  • Microsoft COM SHIM Wizard and Avecto rights
    can you tell me the processes that the Microsoft COM SHIM Wizard uses that ought to be added to Avecto rights
    ZDNet Gravatar
    npingito
    9th Jan

Talkback - Tell Us What You Think

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity