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

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:
, , , ,
Password Game Show

Managing Shared Accounts for Privileged Users: 5 Best Practices for Achieving Control and Accountability

Posted November 20, 2014    Scott Lang

How do organizations ensure accountability of shared privileged accounts to meet compliance and security requirements without impacting administrator productivity? Consider these five best practices…

Tags:
, , , , , ,
Triggering MS14-066

Triggering MS14-066

Posted November 17, 2014    BeyondTrust Research Team

Microsoft addressed CVE-2014-6321 this Patch Tuesday, which has been hyped as the next Heartbleed.  This vulnerability (actually at least 2 vulnerabilities) promises remote code execution in applications that use the SChannel Security Service Provider, such as Microsoft Internet Information Services (IIS). The details have been scarce.  Lets fix that. Looking at the bindiff of schannel.dll, we see a…

Tags:
, , , , ,