CerberusD docs
Governed operations guides
Explore user resource access within CerberusD’s governed operations model for users and AI agents. The guides explain readiness, authority, required approval, duration, revocation and evidence alongside security, architecture and operating responsibilities.
Reading path
Docs sections
Sections follow a practical reading path. Task-specific steps, operating boundaries and evidence are explained on their focused pages.
- Start with the operating model and controlled work on the first resource.
- Then review Windows Agent, architecture, security and deployment responsibilities.
- Use reference and troubleshooting pages to verify operating behavior.
Getting started
First resource readiness, person assignment, controlled work and closure record.
Concepts
The operating model: workspace, resource authority, decision, duration, revocation and evidence.
- ComparisonCompare the access branch of CerberusD’s governed operations model with VPN, remote support, PAM, ZTNA, browser gateway, identity and VDI approaches.
- Core modelThe governed operations model for users and AI agents, and how resources, authority, decisions, work, revocation and evidence fit together.
- Use CasesGovern private-network, shared-server and maintenance work with resource assignments, authorized user decisions, time limits, revocation and reviewable records.
- Time-limited (JIT) accessJIT access opens privileged access only for the task's length. The request, approve (if required), expire and revoke cycle, and how Cerberus applies it.
- Virtual machine accessHypervisor console rights and in-VM access are separate layers. Cerberus governs the second with assignment, time limits, approval if required and records.
- Credential custodyServer access without sharing the password: how the target credential stays out of sight yet ties into session decision, closure and evidence.
- Windows AgentWhat the Windows Agent does for enrollment, readiness, secure connectivity, agentless access boundaries, and evidence.
- Access problemsA source-backed catalog of common access-operations problems, and how CerberusD handles them through governed workspaces, sessions, revocation, and evidence.
- Supplier accessGive a contractor or external support team server access that is time-limited and has audit records, not a standing VPN account or shared password.
- RDP securityRemote desktop access without exposing the RDP port or deploying a VPN: the options, Cerberus's browser session model and its scope.
- SSH access managementSSH access management for teams: assigned, time-limited and, where required, approved browser SSH sessions to Linux servers instead of shared keys.
- AI agent accessGranting AI agents access to servers and desktops: the assignment, duration, approval, revocation and record questions, and what Cerberus covers.
- Privileged access platformsHow to choose a PAM solution. Compare PAM, remote support and VPN/ZTNA by vaulting, time-limited access, approvals, revocation and audit evidence.
Guides
Resource preparation, invitation, authority and assignment, controlled work, revocation and record review.
- WorkspacesCreate or switch workspaces, accept or decline invitations, and work in the correct scope.
- Invite usersInvite a user to a Cerberus workspace by email, resend an invitation that was not accepted, or cancel a pending invitation.
- User rolesChange a Cerberus workspace member’s role from Users, recheck their assignments and pending sessions, and keep administrator roles limited.
- User statusSuspend, reactivate, remove a member, or reset the member's resource access.
- Timed accessLimit member access by end time or usage budget. Follow the steps to extend access, end a grant and check open sessions.
- Connect a machineHow to enroll a Windows machine and make it available as a governed resource.
- Resource managementAdd a manual resource to Cerberus, update its connection details, or archive it so it is no longer offered for new sessions.
- Assign resourcesAssign a Cerberus workspace member a ready resource: pick the member, set timed access and session policy, then confirm it appears in their resource list.
- Manage accessA compact index that routes workspace, people, resource, session, and record tasks to the right guide.
- Session approvalsReview a pending Cerberus session request: check the member, resource and requested duration, then approve, extend or deny it before the session starts.
- Share a sessionRequest to join an active session, use read-only viewing, and end sharing.
- Start a sessionHow to open a browser-based desktop or terminal session from an assigned resource.
- Close resource accessHow to stop a resource from launching new sessions, remove assignments, and verify closure evidence.
- Support ticketsOpen a Cerberus support ticket, add the context support needs, and follow replies and status changes until the request is resolved.
- Ticket escalationRaise a ticket for deeper review when the first support pass is not enough.
- Audit logsReview Cerberus audit logs to see who connected to a server, when and under which decision, with the full event context.
- NotificationsInspect the title, message, time, and read state of access and operational notifications.
Architecture
Decision, readiness, work surface, evidence and operating responsibilities in the resource-access branch.
- Architecture evolutionExplains why Cerberus evolved from infrastructure management into governed desktop operations.
- OverviewDecision, resource readiness, work surfaces, evidence and operating responsibilities in the access branch of CerberusD’s Governed Operations Plane.
- Control planeHow the decision area interacts with identity, resource, assignment, and policy inputs before a session opens.
- Machine connectionWhat the Cerberus Windows connection agent reports, how readiness gates sessions, its Zero Port relationship, revocation and agent lifecycle.
- Browser sessionHow the CerberusLite runtime turns an approved decision into a browser session: checks, controller and viewer roles, input and clipboard rules, closure.
- Evidence planeHow decision, actor, resource, time, closure, and outcome become a readable record.
- Failure and revocationWhat happens when a Cerberus session does not open, closes early or needs a new decision: failure classes, state propagation, retry and review trail.
- Mesh and private networkHow the Windows Agent, gateway paths, and Tailscale-compatible private connectivity keep reachability separate from session authority.
Security
Identity, scope, resource readiness, credential custody, session policy, revocation, and evidence.
- Identity and SSOHow SSO, MFA, person context, assignment, and session decisions stay separate in CerberusD.
- Security modelIdentity, assignment, resource readiness, credential custody, session policy, revocation, and records.
- Zero Trust / Zero PortZero Trust and Zero Port: identity, assignment and session decisions without making the resource port the user's sign-in address.
- Identity and assignmentHow the session decision combines person, role responsibility, resource scope, duration, and readiness signals.
- Envelope encryptionHow secret material stays out of plaintext work surfaces while remaining tied to credential custody and the session decision.
- Revocation and evidenceHow the work path, local preparation, closure reason, and records are read together after access closes.
- Resource readinessHow connected-machine registration, health, readiness, and controlled local action signals become part of the session decision.
- Local accountsHow CerberusD can prepare, rotate, disable, and remove managed local Windows accounts for governed sessions.
Deployment
Product, resource, identity, evidence, and support responsibilities in the managed service.
Reference
Supported protocols, states, roles, events, and responsibilities.
- RolesWorkspace roles, access scope, resource assignments, and session records in Cerberus.
- Session flowDecision, gateway, closure, and evidence path for browser-opened desktop, terminal, or Kubernetes sessions.
- Session policiesHow session duration, work mode, clipboard, transfer, closure, and recording behavior connect to the security decision.
- Without the AgentConnect Linux servers, network devices, terminal and Kubernetes targets and existing RDP/SSH/VNC resources to Cerberus sessions without the Windows Agent.
- Compatibility and versionsA reference for checking connection paths, protocols, and release alignment.
Troubleshooting
Symptoms, likely causes, safe checks, resolutions, and escalation notes.