Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint

Least-Privilege Technology Still Swimming Upstream, But Making Progress

Fundamental shift in endpoint security might be easier with rollout of Windows 7, experts say

The least-privilege security model is one of the oldest and best-known endpoint strategies in the industry. It has the support -- at least on paper -- of Microsoft, and products for implementing it have been available for years. Yet so far, researchers estimate that only 20 percent of corporate endpoints are using those technologies.

So what's everybody waiting for?

For those who came in late, the least-privilege concept was developed in military circles more than a decade ago. Put simply, it states that people -- and their PCs -- should be given access only to information (and software) they expressly need to do their jobs. It's basically the "need to know" concept applied to computers -- each endpoint starts with no access and no administrative rights, and access to applications and data is given only when the end user is deemed to have a need for it.

On paper, the least-privilege concept appears ideal for the business environment, where many security breaches are caused by end users who accidentally leak data or hackers who exploit Windows administrative rights. Microsoft has lent its support to the least-privilege concept with the development of User Access Control (UAC), which creates "standard user rights" on end stations, eliminating the default administrative rights that previously characterized most Windows deployments.

In practice, however, only a small percentage of PCs currently use least-privilege technology. Analysts and other experts point to three chief inhibitors to its deployment: technology, complexity, and culture.

The first problem -- technology -- has to do with Windows itself. In the past, Windows has always granted the user administrative rights as a default, and therefore many applications developers have created software that uses those rights. Intuit QuickBooks, for example, offers several features that rely on administrative privileges, and the program wouldn't work properly if those rights were not there. Many other applications, particularly industry-specific and home-grown apps, also require admin privileges to operate.

"The biggest reason why least-privilege technology hasn't caught on is because of the applications that require admin rights in order to work," says Scott McCarley, director of marketing at BeyondTrust, a security software vendor that specializes in least-privilege. "If you've got programs that won't work without those rights, you're in a tough spot."

BeyondTrust, which works closely with Microsoft, has developed a tool called Privilege Manager, which enables the PC to access administrative rights when it needs them to operate a specific application or task -- and keeps those rights restricted the rest of the time. Of the 20 percent of end stations that currently use least-privilege, many are running the BeyondTrust software, and the company doubled its sales last year.

BeyondTrust maintains that many of today's most popular hacks would be impossible on Windows computers that don't have administrative rights. In a study conducted earlier this year, the company found that of all the vulnerabilities Microsoft labeled as "critical" in 2008, some 92 percent exploited administrative privileges in some fashion.

"Implement least-privilege without admin rights, and 92 percent of those vulnerabilities would have been mitigated," McCarley said. "That's a big step in the right direction."

But analysts say the second inhibitor -- complexity -- still stands in the way of implementation. "[Least-privilege] is a very effective control, but nearly impossible to implement on Windows XP," says Rich Mogull, founder of Securosis, a security consulting firm. "You can do it, but it's pretty hard and has a high impact on the user experience. Thus we see organizations focusing on [Group Policy Objects] and third-party security tools, since dropping to regular user permissions is so disruptive."

In an 2008 interview, Bill Jensen, a product marketing manager at Check Point, said complexity is the chief reason why least-privilege technology hasn't taken off.

"Unfortunately, there are always bugs, even at the kernel level, that can potentially circumvent security privileges," Jensen said. "Least-privilege means defining an individualized security policy for every single person or application. This is, well, nigh impossible."

For this reason, Check Point advocates the use of "default deny" technology that is implemented, not surprisingly, in the firewall. But McCarley says default deny is too restrictive, and doesn't solve the admin rights problem. This argument -- which basicially boils down to whether access rights should be defined in the network or at the endpoint -- adds another level of complexity to the discussion, and makes IT people even more reluctant to implement least-privilege technology.

Many enterprises are solving the problem by leaving administrative rights in their Windows machines, but severely restricting users' ability to access them, Mogull says. But with the rollout of Windows 7, Microsoft will make UAC and standard configurations part of the OS, and that will make the least-privilege concept much easier to deploy, he notes. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
10 Ways to Keep a Rogue RasPi From Wrecking Your Network
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/10/2019
The Security of Cloud Applications
Hillel Solow, CTO and Co-founder, Protego,  7/11/2019
Where Businesses Waste Endpoint Security Budgets
Kelly Sheridan, Staff Editor, Dark Reading,  7/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: "Jim, stop pretending you're drowning in tickets."
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3571
PUBLISHED: 2019-07-16
An input validation issue affected WhatsApp Desktop versions prior to 0.3.3793 which allows malicious clients to send files to users that would be displayed with a wrong extension.
CVE-2019-6160
PUBLISHED: 2019-07-16
A vulnerability in various versions of Iomega and LenovoEMC NAS products could allow an unauthenticated user to access files on NAS shares via the API.
CVE-2019-9700
PUBLISHED: 2019-07-16
Norton Password Manager, prior to 6.3.0.2082, may be susceptible to an address spoofing issue. This type of issue may allow an attacker to disguise their origin IP address in order to obfuscate the source of network traffic.
CVE-2019-12990
PUBLISHED: 2019-07-16
Citrix SD-WAN 10.2.x before 10.2.3 and NetScaler SD-WAN 10.0.x before 10.0.8 allow Directory Traversal.
CVE-2019-12991
PUBLISHED: 2019-07-16
Citrix SD-WAN 10.2.x before 10.2.3 and NetScaler SD-WAN 10.0.x before 10.0.8 have Improper Input Validation (issue 5 of 6).