Authorize and bound
Name the authority, scope, prohibited actions, safety exclusions, stop conditions, and evidence owner before the clock starts.
Run a bounded, evidence-led exercise for loss of the RMM console, API, agent communications, alerting, automation, or remote access—without improvising unsafe production changes.
Name the authority, scope, prohibited actions, safety exclusions, stop conditions, and evidence owner before the clock starts.
Test contacts, inventories, emergency identities, runbooks, ticket intake, approved endpoint access, and telemetry that do not depend on the affected RMM.
Verify console, API, agent, alerting, automation, and remote-access recovery separately. A vendor status page alone is not acceptance evidence.
Own queued jobs, stale alerts, duplicate records, missed changes, temporary access, corrective actions, due dates, and a documented retest.