Skip to main content

Concepts

What is CerberusD?

The governed operations model for users and AI agents, and how resources, authority, decisions, work, revocation and evidence fit together.

Browse all docs

Cerberus is a Governed Operations Plane for users and AI agents doing desktop and terminal work. Task, resource, authority and duration stay defined; required approvals from authorized users and revocation decisions govern the work scope; decisions and results remain in reviewable work history.

User access to resources is one part of this model. Existing computers, servers, terminals and Kubernetes resources stay in their environments; a user sees only assigned resources. Readiness and a valid decision open the browser or controlled private work surface; closure, revocation and lifecycle records remain reviewable together.

Workspace

A workspace groups people, resources, assignments, sessions, and evidence under the same operating scope. It answers questions such as “who can see this resource?” or “where will the session record be reviewed?”

A resource becomes launchable only after workspace connection, readiness, assignment, and policy are clear. Inventory visibility is therefore separate from session authority.

Resource

A resource is the target that can be opened through RDP, SSH, VNC, terminal, or Kubernetes access. It can be a machine, terminal endpoint, cluster entry point, or governed access endpoint.

Two signals matter once the resource appears in the panel:

  • readiness: agent or gateway state that shows whether access can open;
  • scope: which protocol, person, and role can open the resource.

Assignment

A user assignment defines which user can access which resource and under what scope. It is not treated like broad standing network access; session launch still evaluates the user, role responsibility, resource, duration, readiness, active policy and required approval from an authorized user.

This distinction is important: reachability and authority are separate. A deployment can keep a resource reachable for the platform while the person still needs the right assignment and allowed time window to open work.

Session

A user session is the moment an assigned resource opens in the browser. The user works on the assigned resource surface instead of joining a broad network.

Protocol, deployment and active policy determine the scope of session controls:

  • input enabled or blocked,
  • clipboard and file transfer rules,
  • timed access,
  • supported observation and evidence policies,
  • active session closure or access revocation.

Video or screen recording, playback and export remain in development; lifecycle records do not imply video evidence.

Closure and evidence

Closure is the end of the session by user action, system action, time limit, revocation, or connection event. Evidence keeps identity, resource, assignment, launch time, closure reason, and event summary together.

That gives the operating team one place to answer: who connected, which resource opened, what decision allowed it, and when it closed.

Evidence is operational proof that can support review, investigation, and control checks within the deployment’s retention and policy model.

The access branch of this model applies privileged access management (PAM) controls through roles and resource authority, person-resource assignments, time limits, required session approval, credential custody, revocation and audit records. The scope of these controls depends on resource readiness, protocol and active session policy.

Credential custody

CerberusD opens governed work without making the target resource credential part of the everyday user workflow. Credential custody separates the user assignment from secret storage and unwrap flow.

The envelope encryption approach and deployment secret handling are covered in the security model.