Use Cases

CerberusD fits access that operates as a scoped piece of work instead of a loose connection detail. The same pattern appears in each use case: connect the resource, assign the person, open the session, close access, and review the record.

Personal or office computer access

When a person needs to reach an assigned workstation or office computer, CerberusD provides a resource-scoped path. The person sees the assigned resource, starts work from the browser or controlled private access path, and leaves a session record when the work ends.

Flow: connect the machine, assign the person, open the session, close access.

Evidence: launch decision, session duration, closure reason, and revocation event when used.

Shared server or operations terminal

A shared server, test machine, or terminal endpoint can be assigned through CerberusD instead of passing connection files and passwords around. The resource remains tied to assignment, role, duration, and session evidence.

Flow: register the resource, decide who can work, open the session only during the allowed scope, close the session when the task is complete.

Evidence: who opened the work surface, which resource was used, when work started, and how it closed.

Private network RDP and terminal access

RDP, VNC, SSH, terminal, and Kubernetes work paths can be operated through CerberusD when the goal is resource-scoped work rather than broad network membership. The person works through the approved surface while the platform keeps the decision and closure record together.

Flow: resource readiness is read, policy is evaluated, the session gateway opens the work surface, and the closure record is attached to the decision.

Evidence: assignment context, readiness state, session lifecycle, and closure outcome.

Temporary support or maintenance

For maintenance or support work, CerberusD lets the access owner create a time-bound assignment for the relevant resource. The work path can close with the task instead of leaving standing access behind.

Flow: add the support person, assign only the needed resource, set duration, open the session, revoke when complete.

Evidence: access reason, session start, closure, and revocation record.

Workspace resource operations

When multiple resource groups are handled separately, each workspace keeps its own resource visibility, assignments, and evidence records. This lets teams operate different resource sets without turning one inventory into a shared access pool.

Flow: resources are connected under the right workspace, assignments are created in that scope, and records are reviewed from the same scope.

Evidence: resource, person, assignment, decision, and closure all carry the workspace context.