What can we help you with?

Supercharged PAM

Combine the best of Session Management and Credential Management solutions at a new, incredible value!

Learn More Learn More

What is BeyondTrust?

Get a closer look inside the BeyondTrust identity & access security arsenal.

Learn More Learn More

Gartner Peer Insights

Find out how customers & analysts alike review BeyondTrust.

Learn More Learn More

Go Beyond Customer & Partner Conference

Our biggest customer conference of the year is happening in Miami and virtually on May 1-5, 2023.

Learn More Learn More

Watch Our Video

Find out more about our integrations.

Learn More Learn More

Leader in Intelligent Identity & Secure Access

Learn how BeyondTrust solutions protect companies from cyber threats.

Learn More Learn More

Unix & Linux Systems are High Value Targets

Unix & Linux systems present high-value targets for external attackers and malicious insiders. The same holds true for networked devices, such as IoT, ICS and SCADA. Gaining root or other privileged credentials makes it easy for attackers to fly under the radar and access sensitive systems and data.

BeyondTrust Privilege Management for Unix & Linux is an enterprise-class, gold-standard privilege management solution that helps security and IT organizations achieve compliance, control privileged access, and prevent and contain breaches that can affect Unix & Linux systems. Extend capabilities far beyond sudo with centralized administration, session monitoring and management, file integrity monitoring, and powerful productivity enhancement.

The BeyondTrust Privilege Management for Unix and Linux implementation was very successful. All server access is limited—even via SSH. The auditors can easily see that procedures are being followed and our IT employees are able to remain productive.

SVP Systems / Recovery, CTO, DCI

Highlighted Features

Highlighted Integrations

How Privilege Management Works

Endpoint Privilege Management for Unix & Linux: Key Components Explained

First, there’s a client installed on a server. This is used to initiate any sort of elevated commands.

These commands are sent off to the second component, which is the policy server. The policy server evaluates the policy and decides centrally based on your business rules who is authorized to run what commands, as well as where and when they can run them.

These commands are recorded in the event log, so we know which commands were attempted and whether or not they ran elevated.

The session recorder then starts a session recording on the policy server before the command is elevated.

Finally, the client runs the command as the run user.

This architecture allows for both centralized policy management and centralized auditing. Rather than capturing logs locally on the machine where the user has been given root access, logs are captured off the host the user is logged into and where they're trying to elevate.