BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Do You Sudo? SHOULD You Sudo?

Posted March 14, 2011    Peter McCalister

Chances are, if your organization utilizes Unix and Linux servers, your IT staff uses sudo. After all, sudo ships free with virtually all versions and flavors of Linux and Unix and has long been a favorite tool for administrators to define what commands OS users can execute as root, without actually disclosing the root password.

But where the typical sudo implementation excels in convenience, cost, and quick deployment, it falls remarkably short in security and compliance. The very benefits sudo offers actually discourage the development and rollout of a disciplined, well-thought-out privileges management program. For example, sudoer files, which contain user privilege information, can be readily created or modified by any admin with root access and are rarely centrally managed or controlled.

Let’s face it: the insider threat is real. Verizon’s latest security study (2010 Data Breach Investigations Report), conducted in collaboration with the U.S. Secret Service, asserts that 48% of corporate breaches are invoked from the inside. Most companies are highly cognizant of the potential threat insiders pose – through accidental, indirect, or intentional activity – to their mission-critical business applications such as ERP systems. Given inappropriate access privileges, users can commit fraud in any number of ways; segregation of duties is a priority and is routinely tested and verified.

So why aren’t the same safety precautions taken with IT organizations, which more often than not have access to the same mission-critical corporate assets, but at the server OS level? In many cases, it’s because sudo is embraced by IT personnel and their assurance that data security is being maintained at this level is readily accepted. In fact, the companies that put security policies in place at the server level are often the first ones to recognize the need to replace sudo with commercial privileged identity management solutions, as sudo deployment can get out of control quickly and proving compliance is difficult and heavily labor-intensive.

So if you decide to peek under the covers of your company’s sudo deployment, what you may find may be unsettling. But in the interest of protecting your corporate assets, it may be time to do just that.

Leave a Reply

Additional articles

red-thumbprint

Why big data breaches won’t always be so easy

Posted September 19, 2014    Byron Acohido

This blog post is republished with the permission of ThirdCertainty. See the original post here. – By: Byron Acohido, Editor-In-Chief, ThirdCertainty Some day, perhaps fairly soon, it will be much more difficult for data thieves to pull off capers like the headline-grabbing hacks of Home Depot and Target. That’s not a pipe dream. It’s the projected outcome…

Tags:
, , , , ,
pbps-blog2

8 Reasons Your Privileged Password Management Solution Will Fail

Posted September 18, 2014    Chris Burd

Leveraging complex, frequently updated passwords is a basic security best practice for protecting privileged accounts in your organization. But if passwords are such a no-brainer, why do two out of three data breaches tie back to poor password management? The fact is that not all privileged password management strategies are created equal, so it’s critical…

Tags:
, , , , , ,
pbps-customer-campaign-image

You Change Your Oil Regularly; Why Not Your Passwords?

Posted September 11, 2014    Chris Burd

There are many things in life that get changed regularly:  your car oil, toothbrush and hopefully, your bed sheets.  It’s rare that you give these things much thought – even when you forget to change them. But what if you’re forgetting something that can cost you millions of dollars if left unchanged for long periods…

Tags:
, , ,