Skip to main content

Governed desktop and terminal access

Manage server, desktop, and terminal access from one panel.

Cerberus brings RDP, SSH, VNC, terminal, and Kubernetes resources into a centralized access plane. Agent or gateway models keep resource ports away from direct user access. Approved sessions open in the browser while assignment, credential custody, revocation, and auditable records stay in one flow.

MA
RDP, SSH, VNC, and Kubernetes accessExample resource access flow
ResourceProtocolAuthority / credentialStatusAction
ERRDPTimed accessActive
PLSSHDynamic passwordAudit on
K8KubernetesRole-basedActive
HPVNCWaiting approvalClosed
Record summary

RDP access to erp-windows-02 is open with a timed permission; start and closure events are tracked.

One task, different teams

One resource. Each team sees its part.

IT, external support, security, and the work owner make different decisions around the same resource. Cerberus keeps those decisions visible in one work context.

  1. IT operations

    See resource readiness, the assigned person, and the work duration together.

    Manage the connection path and assignment in one workspace.
  2. External support

    Work only on the desktop or terminal task assigned to them.

    Use the browser work surface without receiving the target password.
  3. Security team

    Follow the request, any required approval, and the active session in the resource context.

    Verify the revocation decision and closure of the path to new sessions.
  4. Work owner

    Find start, work, and closure events in the same task trail.

    Review the outcome without searching across separate tools.
  1. 01

    IT operations

    See resource readiness, the assigned person, and the work duration together.

    Manage the connection path and assignment in one workspace.
  2. 02

    External support

    Work only on the desktop or terminal task assigned to them.

    Use the browser work surface without receiving the target password.
  3. 03

    Security team

    Follow the request, any required approval, and the active session in the resource context.

    Verify the revocation decision and closure of the path to new sessions.
  4. 04

    Work owner

    Find start, work, and closure events in the same task trail.

    Review the outcome without searching across separate tools.

The task owner, work status, and closure stay clear across teams.

Why does this model matter?

The Cerberus operation path

One panel brings the work's decisions together.

Reaching a resource is only part of the work. Cerberus keeps the actor, selected resource, and closure visible in the same view.

01User
PAMCerberus PAM control
  • Identity
  • Assignment
  • Duration
  • Live session
  • Record
  • Terminate access
02Assigned resources
  • RDP
  • SSH
  • VNC
  • Kubernetes

Users connect to assigned resources. Access can be closed when required, while session start and closure events leave an auditable record.

Who is working?
The person and assigned resource appear together.
What is the work status?
Duration and session state are visible in one place.
How did it close?
The revocation decision and session outcome are shown separately.

Bring resources into the workspace

Resources stay put. Work meets in one place.

Choose the connection path that fits your environment. Even when resources live in different places, the team manages assignments and session state from one panel.

Swipe to compare both connection models

Agentless connection

Bring existing server, desktop, and terminal resources into the panel through a suitable gateway or defined access path for RDP, SSH, VNC, terminal, and Kubernetes access. RDP, SSH, and VNC sessions open in the browser when the resource is ready and the access decision allows them.

  • RDP
  • SSH
  • VNC
  • K8S

Agent-assisted connection

Use the Agent on Windows machines for a closer view of readiness, service health, and connection state.

  • Readiness
  • Health
  • Private path
COMMON

Assignment, duration, session, and record

The connection path and the decision about who may work are separate. Both meet in the same Cerberus resource view.

  1. 01Resource
  2. 02Assignment
  3. 03Session
  4. 04Record

The resource connection path and a user's session permission are separate decisions. See how it works. Agent details

First month TRY 1 campaign

Manage governed desktop and terminal operations from one panel.

Choose an Agent or gateway model in Cerberus Platform and govern remote machines, terminal sessions, and Kubernetes resources through PAM-controlled access and records. Start with the first-month TRY 1 campaign.

  • Optional Agent
  • Setup in minutes
  • Session events

Explore the AI side.

See how the same governance model extends to AI workers, tasks, and outcome records.

CERBERUS / DAEMON

Give AI the work. Keep the control.

Create an AI worker in Cerberus, assign a task and resources, and keep approvals, automation, and work history in one place.

Zero Trust · desktop and terminal

To see the resource and session flow in Cerberus Platform, open the live demo ↗

Cerberus governs human and AI desktop and terminal operations with a Zero Trust approach.

Earth illuminated against a dark background
HUMANS · AI · SYSTEMS

Cerberus AIFollow the worker from task to result below.

Cerberus PlatformSee resources, permissions, duration, and session records in the live demo.

Work branches out.
Control stays central.

Start with one worker. As work expands, manage AI workers in the same system and set the resources and permissions for each task.

Your decisions
CERBERUSAI operations center
01 / ASSIGNED APPLICATION

ASSIGNED APPLICATION

Turn requests into work.

An AI worker reviews incoming requests, separates missing details, and prepares work records for your approval.

Ready for approval
02 / PERMITTED FILES

PERMITTED FILES

Bring scattered work together.

It works with the files you choose, gathering missing details and the material needed for delivery.

Prepared delivery
03 / ASSIGNED COMPUTER

ASSIGNED COMPUTER

Keep routines on track.

Connect selected checks to scheduled tasks and follow results that need your attention.

Check and notification
Example work paths. You set each role, task, and access scope; the system grows with the resources you assign.

ONE CERBERUS

Teams and AI workers. One governance plane.

Manage resources and your team's access in Cerberus Platform. Assign tasks, resources, and duration to workers in Cerberus AI. You set permissions and decide when to revoke; authorized users make the required decisions, and results remain in the work record.

01 / TEAMS

Cerberus Platform

Connect a resource and check readiness. Grant access by person and duration; follow the session, revocation, and closure record.

RESOURCE → ASSIGNMENT → SESSION
02 / AI

Cerberus AI

Create a worker and assign a task to a chosen resource. Track required decisions by authorized users and the result with the task.

WORKER → TASK → RESULT

Bound the AI workspace by task, resource, and duration. Other resources are not added to the task automatically; you decide when access expands.

ONE TASK · TANGIBLE RESULT

The task ends. The record stays.

A resource and work duration defined in the platform are linked to an AI task. AI flags a missing delivery date; you decide, and the result stays in the work record.

BEFORE

Open document · Find gaps · Write review note

IN THIS FLOW

AI prepares a first review · An authorized user evaluates the result

EXAMPLE TASK RESULT · HISTORY / WORK RECORD

ONE TASK · TANGIBLE RESULT

Ready for review

ASSIGNED TASK

“Find missing details in the document and prepare a summary for my approval.”

Missing detail
The example document has no delivery date.
Completion
Missing fields and a review summary are ready.
Authorized user decision
An authorized user decides whether work can proceed without the delivery date.
Record
Task, decision, and result remain visible in history.

Illustrative view · Results depend on the task and work conditions.

CERBERUS / NEXT STEP

Set up the resource model.
Grow with AI.

Set up resources, permissions, and sessions in Cerberus Platform. Plan how to govern AI workers and automation by task, resource, and duration within this operations plane.

Discuss AI useSee plansAfter exploring the resource and session model, choose a suitable plan.

See the platform side.

See how resource readiness, permissions, duration, sessions, and closure records come together for user access.