Core model

CerberusD brings existing computers, servers, terminals, and Kubernetes work surfaces into a governed access operation. The resource stays in its operating environment; a workspace defines who can see it; an assignment narrows who can use it; a session decision opens the work surface; closure or revocation ends the path; and evidence keeps the decision and result reviewable.

The model is easiest to read as an operating loop: connect the resource, assign the person, open the session, close access, and review the record.

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

An assignment defines which person can access which resource and under what scope. It is not treated like broad standing network access; session launch still evaluates the person, role responsibility, resource, duration, readiness, and active policy.

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 session is the moment an assigned resource opens in the browser. The person works on the assigned resource surface instead of joining a broad network.

Session behavior can include deployment-specific controls:

• input enabled or blocked,
• clipboard and file transfer rules,
• timed access,
• monitoring or recording requirements,
• active session closure or access revocation.

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.

Credential custody

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

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