Skip to main content

Concepts

Privileged Access Management (PAM) Comparison and Selection Guide

How to choose a PAM solution. Compare PAM, remote support and VPN/ZTNA by vaulting, time-limited access, approvals, revocation and audit evidence.

Browse all docs

Privileged access management (PAM) controls who reaches sensitive resources such as servers, virtual machines and desktops, for how long and under which controls. When choosing a PAM solution, ask one question first: does the product manage passwords, or access decisions? The criteria below separate approaches along that line, and the page ends with the cases where Cerberus is not the right fit.

Operating-model difference

  • Identity and access: A privileged-access product may center on accounts and policy; CerberusD evaluates a decision with person, workspace, resource, assignment, readiness, role scope and session policy.
  • Credential custody: A target credential can be used through a controlled work surface without exposing it to the operator; detailed custody remains deployment-dependent.
  • Session and closure: When an assignment ends, new sessions are blocked; an active session is checked separately. Decision and lifecycle records are read together in audit review.

What problem does PAM solve?

Privileged accounts are administrator passwords, root access and service accounts. When they are shared, it becomes unclear who did what and when; when a person leaves or a job ends, closing access means knowing where the password was copied.

PAM reduces this risk in three ways: it keeps the credential away from the user, ties access to a decision and a time limit, and makes what happened reviewable afterwards. Products weight these three differently. The comparison is about seeing that weighting.

Credential vault or session without sharing the password?

Classic vault-centric PAM stores the credential in a vault and hands it to the user or rotates it automatically. Its strength is managing credentials in one place.

In a no-password-sharing model the user never sees the target password; the session opens on a managed work surface. Cerberus applies this through credential custody: in supported session types the target credential is not handed to the person who opens the session. Detailed custody responsibility depends on the deployment, so settle that boundary during selection.

If users are shown the password, invalidating it after access is closed is a separate task. If they never see it, the only thing left to close is the decision.

Is there time-limited (just-in-time) access?

Standing administrator access is the most common weakness of privileged accounts. With time-limited access, a membership or resource permission is bound to an end time or a usage budget.

In Cerberus, timed access is chosen when an invitation or member access is created; once the time ends, the decision to start a new session follows that condition. The time can be extended, but extending does not add resources. When evaluating, ask: after expiry, can a new session still open, and what happens to one that is already open?

How does the approval flow work?

Not every access needs a person’s decision, but sensitive resources do. The criteria are who holds the approval and what it covers: person, resource and duration.

In Cerberus an authorized role reviews pending session requests and approves or rejects them; an approved request starts for the allowed duration, a rejected one opens no session. Whether approval is required depends on the active session policy.

Session gateway or endpoint agent?

A gateway model opens the session from a central point; it needs no installation on the resource, but signals from inside the machine stay limited. An agent model runs on the machine and produces health and readiness information, at the cost of an installation.

Cerberus supports both. The Windows Agent produces service health, local readiness and managed local account signals on Windows machines. For Linux servers, network devices or resources where no agent can be installed, agentless access brings RDP, SSH and VNC targets into the same decision and record flow. In the agentless model, in-machine health and cleanup signals are more limited.

How is access revoked?

Revocation is not one operation. Removing an assignment closes new sessions but does not end an open one; the open session is closed separately. Depending on the connection model, resource readiness is also withdrawn.

Cerberus shows these three operations separately. If a termination request fails, it is not marked as a successful close and the result stays visible. When evaluating a product, ask exactly what its “revoke access” button closes.

What does the audit evidence show?

Audit evidence is worth what the product actually keeps. In Cerberus the scope is event records: decision, assignment change, session lifecycle, revocation and close. Records contain no secret values.

Session recording and playback are not part of the product today; that area is in development. If it is a decision criterion for you, evaluate another solution. You can read the records with the audit review guide.

How much work is the deployment model?

The setup effort of PAM programs varies by product and deployment; ask during selection whether separate security, network and infrastructure ownership is needed. Cerberus starts close to the endpoint and the managed session: connect the resource, assign the person, open the session. Network reachability, firewall and identity provider responsibilities stay with your team; the Zero Port model removes the resource port as the user’s entry address, but the network team still operates the resource-side network boundary.

What changes for AI workers?

Automation and AI agents also do privileged work. The criteria are the same as for people: task, resource, authority and duration are defined, required approval comes from an authorized user, and the outcome is reviewable. Cerberus’s operating model bounds the work of AI agents in this framework alongside users; see AI agent access for details. Ask separately which identity and which approval an AI job runs under in the solution you choose.

Approaches side by side

Criterion Vault-centric PAM Remote support tools VPN / ZTNA Cerberus
Main focus Storing and managing privileged credentials Fast screen sharing and support Reachability of a network or private resource Managed session decision on an assigned resource
Does the user see the password? Depends on the model Depends on the product Out of scope Not in supported sessions
Time-limited access Depends on the product Depends on the product Depends on policy and product End time or usage budget
Session approval Depends on the product Depends on the product Usually out of scope Authorized role approves or rejects
Revocation Depends on the product Closing the connection Removing network authority New session, open session and readiness handled separately
Records Depends on the product Depends on the product Depends on policy and product Decision and lifecycle events

Verify every “depends” cell individually; the table shows general tendencies of categories, not the features of a specific product. For the support side see the remote support comparison, for the network side the private network and ZTNA comparison. These are not rivals; in most environments they complement each other.

When is Cerberus not the right fit?

  • Your main need is a password vault, password rotation or central management of service account secrets. Cerberus focuses on the session decision and is not a general-purpose secrets manager.
  • Session video and playback are mandatory. That area is in development.
  • You need virtual machine hosting, VDI or hypervisor management. Cerberus governs access to your own machines; it does not provide machines and has no hypervisor console integration.
  • You want instant, user-attended screen help. Remote support tools fit that better.

FAQ

What is the difference between PAM and a VPN?

A VPN brings a person close to a network; PAM decides who works on a sensitive resource in that network and for how long. Being able to reach a network is not authority to work. The two can be used together.

What is the first question when choosing PAM?

Which resources are protected and who accesses them: people, service accounts, AI agents? The answer shows whether you need a vault-centric or a session-centric solution. Then test time limits, approval and revocation behavior.

Does a small team need PAM?

Yes, if you use a shared administrator password and cannot safely close access when a job ends. A three-person operations team carries this risk too; starting with a few critical resources and widening from there is enough.

Does Cerberus make an organization compliant?

No. Cerberus records decisions, assignments and session events; these records can serve as evidence in an audit, but compliance with a standard is not the outcome of a product alone.

To try Cerberus on your own resources, go to the demo page.