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

ovum-research

New Analyst SWOT Assessment Identifies Key Strengths of PowerBroker

Posted November 24, 2014    Scott Lang

Following on the heels of the Gartner PAM market guide and Frost & Sullivan review of Password Safe comes a new analyst review of our BeyondInsight and PowerBroker platforms, a SWOT assessment of BeyondTrust written by Ovum. Ovum’s honest and thorough review of BeyondTrust indicates that we are delivering, “…an integrated, one-stop approach to PAM….

Tags:
, , ,

Patented Windows privilege management brings you unmatched benefits

Posted November 24, 2014    Scott Lang

We are pleased to announce that BeyondTrust has been granted a new U.S. Patent (No. 8,850,549) for privilege management, validating our approach to helping our customers achieve least privilege in Windows environments. The methods and systems that we employ for controlling access to resources and privileges per process are unique to BeyondTrust PowerBroker for Windows….

Tags:
6

A Quick Look at MS14-068

Posted November 20, 2014    BeyondTrust Research Team

Microsoft recently released an out of band patch for Kerberos.  Taking a look at the Microsoft security bulletin, it seems like there is some kind of issue with Kerberos signatures related to tickets. Further information is available in the Microsoft SRD Blogpost So it looks like there is an issue with PAC signatures.  But what…

Tags:
, , , ,