Risk
2/3/2009
04:18 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Windows Security Improved By Denial Of Administrative Rights

Configuring users to operate without administrative rights mitigates 92% of "critical" Microsoft vulnerabilities and 69% of last year's published vulnerabilities, according to a report.

To make Microsoft Windows more secure, organizations should trust Windows users less.

In a report released Tuesday, BeyondTrust, a company that sells computer privilege management software, concludes that, indeed, computer privileges should be managed.

This unsurprising finding is borne out by the company's analysis of the 80 security bulletins, addressing 150 vulnerabilities, that Microsoft published in 2008. The company found that configuring users to operate without administrative rights mitigates the impact of 92% of "critical" Microsoft vulnerabilities and 69% of last year's published vulnerabilities.

The removal of administrative rights has significant impact on the vulnerability of Microsoft Office and Internet Explorer, the company claims, making it harder to exploit 94% of Office vulnerabilities and 89% of Internet Explorer vulnerabilities.

Microsoft's own data indicates that 75% of Windows machines run with a single account and full administrative privileges.

Microsoft has been aware for years that user accounts with administrative rights can be abused. That's why it introduced User Account Control in Windows Vista. But the implementation of UAC has been widely criticized as annoying and ineffective. A Microsoft employee reportedly said last year that UAC was supposed to annoy users.

Microsoft last month published a blog post explaining changes to UAC in Windows 7. It said the company's forthcoming operating system would reduce the number of UAC warning prompts and offer users greater control over UAC.

Last week, blogger Long Zheng published a critique of the company's new approach, claiming that Microsoft's effort to make UAC less annoying makes UAC vulnerable to being disabled.

Among the Windows users posting comments about Microsoft's changes to UAC, the response is mixed. Some praise UAC, others condemn it, and others express mixed feelings.

Computer security is like that. Not everyone is going to be happy, no matter what you do. Reducing administrative rights among users may help. It may also drive users to work in less-restrictive environments when possible, such as at home, and that may create other security risks.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.