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

How To Implement The Australian Signals Directorate’s Top 4 Strategies

Posted October 20, 2014    Morey Haber

The Australian Signals Directorate (ASD), also known as the Defence Signals Directorate, has developed a list of strategies to mitigate targeted cyber intrusions. The recommended strategies were developed through ASD’s extensive experience in operational cyber security, including responding to serious security intrusions and performing vulnerability assessments and penetration testing for Australian government agencies. These recommendations…

Tags:
, , , ,
asp-mvc

Exploiting MS14-059 because sometimes XSS is fun, sometimes…

Posted October 17, 2014    BeyondTrust Research Team

This October, Microsoft has provided a security update for System.Web.Mvc.dll which addresses a ‘Security Feature Bypass’. The vulnerability itself is in ASP.NET MVC technology and given its wide adoption we thought we would take a closer look. Referring to the bulletin we can glean a few useful pieces of information: “A cross-site scripting (XSS) vulnerability exists…

Tags:
4bestpracticesaudits-blog

Four Best Practices for Passing Privileged Account Audits

Posted October 16, 2014    Chris Burd

Like most IT organizations, your team may periodically face the “dreaded” task of being audited. Your process for delegating privileged access to desktops, servers, and infrastructure devices is a massive target for the auditor’s microscope. An audit’s findings can have significant implications on technology and business strategy, so it’s critical to make sure you’re prepared…

Tags:
, , , ,