The scenario

Recovery is a sequence of decisions, not just a restore button. In Vulnverse v2, Backup Recovery Drill organizes an exercise around the information those decisions need: incident status, business assets, restore requests, recovery plans and stakeholder updates. A team can examine whether its proposed recovery order is supported by the available records.

The public routes represent coordination. Private records represent backup inventory, recovery sequencing, exercise evidence and audit exports. Together they support a structured tabletop or an investigation into recovery information exposure. Users define the exercise question, decision criteria and review process.

Public surfaces

Incident coordination, restore requests and stakeholder updates run through these routes; the configured exercise inventory sets the actual scope.

Public routes declared in the Backup Recovery Drill catalog
RouteSurfaceContext
/incident-statusIncident status and executive update portal.
/restorerestore-requestsRestore request and prioritization workflow.
/assetsasset-catalogBusiness service and asset catalog facade.
/commscomms-portalStakeholder communication and update surface.

Private systems

backup-vault-inventory Private data

Backup vault inventory and retention metadata.

recovery-orchestrator Private application

Recovery sequencing and dependency workflow data.

tabletop-evidence Private data

Tabletop exercise evidence store.

immutable-log-store Private data

Immutable log and audit export representation.

Exercise questions

  • What information is needed to prioritize a restore request against the business asset inventory?
  • Which dependencies must be resolved before an operator could reasonably declare a service restored?
  • Do stakeholder updates distinguish a requested action, an approved plan and evidence that an action completed?

What to hand in

Create a recovery decision record with the proposed order, supporting artifacts, unresolved dependencies and evidence still needed. Treat missing confirmation as an open question rather than a successful restore.

Records and evidence

Assets and restore requests define scope. Backup vault metadata and recovery plans describe the intended context. Communications and audit exports help trace how a decision was explained. Use the records to identify which confirmation a recovery decision still needs.

  • assets
  • restore-requests
  • backup-vaults
  • recovery-plans
  • communications
  • audit-exports

Record each Backup Recovery Drill finding with the research method →