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.

There is No Patch For Stupidity

Posted January 24, 2011    Peter McCalister

No, I’m not talking about a Boy or Girl Scout patch (or merit badge) now awarded for making dumb errors with information technology at work.  I’m referring to the ever present vendor tech support cry of “just install the patch” whenever something goes wrong.

In this case, the patch is a “fix” for the buggy software that invariably caused some loss of data and/or productivity.  But what happens when the error is human error?  Unfortunately there are no “patches” for that, unless you count getting rid of said employee and replacing him/her with someone smarter.  A common cry of helps desk personnel worldwide is PEBKAC! If you forgot what that means then remind yourself at this post on Reducing Help Desk Costs Is a Least Privilege Benefit.

Accidents happen and if you are still providing excessive privileges to your desktop/laptop users or server/network/database/cloud/virtual administrators, then you are at risk of the accidental misuse of privilege.  Sometimes these accidents can cause harm that is newsworthy.  In this instance you not only have to deal with the problems created, but the public fall out that follows from the press and blogosphere.

First you need to eliminate admin rights on windows desktops and root privileges off of servers, then you implement a privilege identity management solution to create a “least privilege” environment such that no one will have enough permission to cause harm if they misuse their privileges.  In this way you can mitigate the severity of potential user stupidity and not have to deal with the help desk crying PEBKAC or fear an unpleasant expose in the Wall St Journal, local paper, wikileaks.com or the blogosphere.

Leave a Reply

Additional articles

Integrating Least Privilege and Password Management to Solve Account Security Challenges

Integrating Least Privilege and Password Management to Solve Account Security Challenges

Posted July 24, 2014    Morey Haber

There is a reason all BeyondTrust Privileged Account Management (PAM) solutions share the PowerBroker name: They all inherently enable you to reduce user-based risk and can be integrated under a centralized IT risk management platform. Here’s one common use case that demonstrates how this integration changes the playing field. Consider the challenge of privileged access:…

Tags:
, , , , ,
PowerBroker Password Safe Password Age Report

Reshaping Privileged Password Management with Password Safe 5.2

Posted July 21, 2014    Martin Cannard

Today, we’re pleased to unveil the latest edition of our privileged password management solution, PowerBroker Password Safe. I’ll start with a brief intro of what’s new and then tell you a little about the driving factors behind Password Safe development. New features for mitigating password risk and ensuring accountability enterprise-wide Here’s the 10,000-foot overview of…

Tags:
, , ,
PowerBroker for Windows tamper protection

PowerBroker for Windows 6.6 Tamper Protection

Posted July 18, 2014    Morey Haber

I have a bone to pick: Stopping an administrator from performing an action on a system is futile endeavor. As an administrator, there is always a way to circumvent a solution’s from tampered protection. Really! By default, Windows administrators have unrestricted access to the system – and even though an application, hardened configuration, or group policy…

Tags:
, ,