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.

PowerBroker for Windows – Solution Deployment

Posted October 11, 2012    Morey Haber

PowerBroker for Windows (PBW) is designed to integrate directly into your corporate Active Directory (AD) structure without modifying your existing schema. In the asset labeled “1” below, an administrator simply loads a Group Policy Option (GPO) snap-in onto an asset that uses the Microsoft Management Console (MMC).  The administrator can then create policies and rules that are stored in the AD domain labeled “2”.  An administrator can also access the management console (Retina CS labeled “3”) via a web interface to run reports or create additional rules based on collected events from the environment.

As domain assets log on (servers, workstations, or remote clients labeled “4”) they receive policy from the domain controller that is processed by the PBWagent. This agent is installed on each device and can be distributed through a software delivery solution or even through GPO itself. This enforces privilege identity management rules on the endpoint and sends status events back to Retina CS for additional reporting, trending, and rule creation.

In a traditional deployment, your organization needs to consider deploying the following three components:

  1. PBW Agents on Servers, Desktops, and Remote Clients
  2. PBW GPO Snap-In for Rules on Administrator Workstations
  3. Retina CS Management Console for Reporting and Event Management (optional).

PBW Agents are lightweight MSI installers, under 30MB, that can be pushed down to assets using everything from logon scripts to GPO. The GPO snap-ins should only be deployed where needed for policy creation. And,Retina CS (available soon for PBW) is generally a one-time server installation (software, virtual, or appliance) for management. It can also be deployed as multiple servers in atiered architecture for enterprise clients if needed.  Below is an example of this approach.

For more information on how to take advantage of PowerBroker for Windows and Retina CS within your environment, please click here. BeyondTrust is the thought leader for integrating privilege identity management and vulnerability assessment in a single solution.

Tags:
, , , , , , , ,

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