Easier Deployment and Improved Manageability

Bomgar Privileged Identity, formerly Lieberman RED Identity Management, installs quickly and is easy to deploy and configure. It has been designed from the ground up to be operationally efficient, and integrations with new systems management, SIEM, help desk and other applications are simple configurations that you can make without professional services. 

Privileged Identity is provided as a software application for on-premises or cloud deployments in Microsoft Azure, Amazon Web Services, or as an application in the Microsoft Azure marketplace. It can also be deployed “headless” and programmatically managed, controlled, and accessed via PowerShell cmdlets or using REST or SOAP based web services. 

With its industry leading integrated system and device discovery and ability to take part in any orchestration process, our time from install to full management is often measured in days, not months or years.

Configuration Made Simple

Bomgar Privileged Identity is designed to be easy to configure and maintain over time. 

  • All customers get the same supported code base that includes built-in options to configure the solution for your specific purposes, however complex. 
  • There is no extensive customization and one-off vendor implementations, so you’ll minimize your future costs and simplify your software updates and security fixes. 
  • Nearly all customers are able to configure Privileged Identity without requiring professional services.


Requirements for Privileged Identity Deployment

A SQL Server database, either on premises or in your preferred cloud is required to store password credentials (encrypted) and audit logs. Configuration of the data store is handled automatically by the application. 

You can leverage your organization’s trusted processes for database management, monitoring, and high availability and disaster resiliency – giving you unmatched transparency and control. Privileged Identity components will be installed on a Windows Server host running Windows Server 2008 R2 or later, including Windows Server 2016.