Security

Resource Readiness and Agent Trust

How connected-machine registration, health, readiness, and controlled local action signals become part of the session decision.

Page type: SecurityResource readinessStatus: CurrentCurrent product behaviorLast reviewed: 2026-07-01

Resource readiness means a machine is read as a governed CerberusD resource, not just a name or address. The connection agent exposes registration context, last-seen state, service health, protocol readiness, and controlled action outcomes.

A ready resource still does not grant automatic access. Readiness is an input to the session decision, evaluated with identity, assignment, duration, and policy.

Scope

Seeing a row in inventory is not the same as opening a secure session. CerberusD evaluates these questions together:

  • is the machine registered to this workspace,
  • is the resource sending current service and last-seen signals,
  • is the target protocol or work path ready,
  • what happened if local account or credential preparation ran,
  • which action remains visible on the machine when access closes.

How it works

Resource readiness has three layers.

Registration binding ties the machine to the correct governed resource. Resource identity is not inferred only from hostname or IP similarity.

Health and capability signal carries last-seen, service state, and protocol readiness into the decision layer.

Controlled local action covers deployment-dependent work such as managed local account creation, password rotation, RDP membership preparation, account disablement, or account deletion.

Process

  1. The agent is installed on the target machine, or the resource appears through a defined connection method.
  2. The resource appears as a pending record.
  3. An authorized role claims the record.
  4. The agent sends last-seen, service, and readiness signals.
  5. The resource is assigned to a person.
  6. Credential or local account preparation runs when needed.
  7. A session request evaluates identity, assignment, duration, policy, and readiness together.
  8. Closure records the revocation outcome against the resource.

Records

Resource readiness records show:

  • registration and claim time,
  • last-seen and service state,
  • protocol or work-path readiness,
  • local action outcome,
  • the link between session decision and preparation,
  • revocation or closure outcome.