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.

3 Ways to Remediate Misuse of Privilege

Posted January 20, 2011    Peter McCalister

In the event that someone in your organization does misuse privilege and causes harm (theft, damage or loss of data), you will have to immediately deal with the aftermath.  In today’s security conscious enterprise, there are three level of remediation to consider:

  1. Password Management:  In this situation you have eliminated users maintaining their own credentials and facilitate the access to information technology (IT) resources through a web-based Shared Account Password Management (SAPM) solution.  When the user desires access they go to a specific web screen which then logs the user into the requested resource based on some recognized stored policy.  The good news here is that in the event someone misuse that resource, you have a record of who was using it at the time of the breach.  This is the equivalent of know who did the damage but not what they did.
  2. Session Management:  In this situation, you are building on Password Management with the addition of automatic logging of every event (or keystroke) to another server of what was done once someone is granted access to the resource.  If harm does in occur in this situation then you not only know who did the harm but what they did, so you can “unwind” or fix what was done.
  3. Privilege Delegation:  In this situation, you are delegating privileges (system authorizations) to specific users based on defined, centralized corporate policy.  This builds on Session Logging and delivers all of the previous value but now limits the damage potentially done as it limits what authorizations are available based on policy.  In effect you have prevented harm from being done and have a record of who attempted to do harm and what they attempted to do.

Bottom line is that you need some form of solution to protect against the misuse of privilege and remediate any potential harm that does occur.

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:
, , , ,