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.

Extending Password Policy To UNIX and Linux

Posted September 21, 2011    Peter McCalister

Our friends and colleagues at the Linux Foundation have been hit by a “brute force attack” and many of their sites have been taken down until the security breach is fully controlled.

The good news here? The Linux kernel and the projects’ source codes haven’t been affected. The bad news? As noted by desktoplinux.com, “Username, password, email address, and “other information” provided by users registered with the sites may have been stolen.” As a Linux user and big fan of the Linux Foundation, my personal information is likely included in the compromised set. And on a personal basis, the fix is easy–a new, strong password that’s unique to that site.

What about on a corporate level? When a breach like this occurs, say at a BeyondTrust customer with a large deployment of Linux & UNIX systems, what’s the best practice for IT admins?
I wrote a couple months back about password management and how it is the weakest link in enterprise security. There have been many studies done that show password complexity and a regular cycle of password changes improves the daunting prospect of maintaining security. This is a best practice employed in most enterprise IT organizations and a key component of compliance with regulations and standards like Sarbanes-Oxley.

Password policy is easily managed in Active Directory for Windows systems. But what about Linux and UNIX systems–as highlighted by the breach at Linux.com?

We’ve noted before that centralizing on a single directory is a security best practice, and we have a free and open source solution that enables extending password policy to Linux and UNIX systems–fulfilling best practice requirements. PowerBroker Identity Service – Open Edition is a free download for over 200 Linux and UNIX platforms and enables administrators to join machines to Active Directory and require users to login with their directory credentials. The entire process takes less than five minutes–download, install, join. The password policies that you set in your Windows environment are then extended to users on these machines.

And when a security breach occurs like the one noted above? Administrators can push out a password change requirement or trust their strong password policy to keep systems secure across the enterprise, no matter what operating system they are using.

Leave a Reply

Additional articles

Dark Reading

2014: The Year of Privilege Vulnerabilities

Posted December 18, 2014    Chris Burd

Of the 30 critical-rated Microsoft Security Bulletins this year, 24 involved vulnerabilities where the age-old best practice of “least privilege” could limit the impact of malware and raise the bar of difficulty for attackers.

Tags:
, , , , ,
dave-shackleford-headshot

Looking back on information security in 2014

Posted December 16, 2014    Dave Shackleford

Dave Shackleford is a SANS Instructor and founder of Voodoo Security. Join Dave for a closer look at the year in security, and learn what you can do to prepare for 2015, with this upcoming webinar. 2014 has been one heck of an insane year for information security professionals. To start with, we’ve been forced…

Tags:
, ,
patch-tuesday

December 2014 Patch Tuesday

Posted December 9, 2014    BeyondTrust Research Team

This month marks the final Patch Tuesday of 2014. Most of what is being patched this month includes Internet Explorer, Exchange, Office, etc… and continues a trend of the greatest hits collection of commonly attacked Microsoft software. Probably the one thing that broke the mold this month is that for once there is not some…

Tags:
,