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

Restricted Area Sign

Implementing Least Privilege for Windows the Easy Way

Posted July 31, 2014    Morey Haber

The concept of least privilege states that asset users should have the lowest level of access privileges required to effectively conduct their jobs. Implementing least privilege can bring several benefits to your organization, including: Increased security by reducing the attack surface available to users and to potential attackers who compromise user systems via phishing, malware,…

Tags:
, , ,
gartner market guide image - aug 2014

Introducing the Gartner Market Guide for Privileged Account Management

Posted July 29, 2014    Chris Burd

Gartner recently released a new Market Guide for Privileged Account Management (PAM), and we’d like to share a complimentary copy with you. The report includes PAM market analysis and direction, vendor overviews, and recommendations for selecting PAM solutions for your environment. BeyondTrust is one of two representative vendors (out of 20) to address all solution…

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