Deception Check

SMALL BUSINESS / RECOVERY REHEARSAL

The backup finished.
Can the business reopen?

Rehearse one critical service, measure the time and usable data, and let the business owner verify the result.

A green backup job is the beginning of the recovery conversation.

Pick the work you need back: receiving orders, dispatching stock, paying staff, or running equipment safely. Ask what it depends on, which copy would restore it, and who can prove it works. The exercise should end with measured results, not another successful-job notification.

Set two targets before you test.

OUTAGE TARGET

How long can this work stop?

Count to usable business service, including application setup, dependencies, and the owner's checks. The file-copy finish time is an intermediate milestone.

DATA-LOSS TARGET

How much recent work can you recreate?

Use a time unit the owner understands. Compare the usable recovery point with the test's incident cutoff, not just the age of the backup job notification.

RECOVERY-REHEARSAL WORKFLOW

Agree targets

Outage limit and recent work at risk.

Protect the route

Copy, retained versions, access, keys, dependencies.

Restore in isolation

Block real transactions and equipment actions.

Verify the work

Owner checks usability; team fixes gaps.

Read left to right on a wide screen, or top to bottom on a phone.

The files came back. The service missed its target.

This is a hypothetical practice exercise, not a customer result or a benchmark. Ordering must be usable within four hours, with no more than thirty minutes of recent orders lost. The exercise uses 09:00 as its incident cutoff and test start.

WORKED EXAMPLE / SAME-DAY TIMES / UTC

08:40

Latest consistent recovery point available.

09:00

Recovery work starts; this is the exercise incident cutoff.

11:00

Data restoration finishes.

14:00

Ordering application, shipping dependency, and representative order checks are complete. Business owner confirms usability.

Five hours to usable service. Twenty minutes of work at risk.

OUTAGE COMPARISON / HOURS / BOTH BARS SHARE A ZERO

Maximum outage4 hours
Usable service5 hours
Outage target missed by one hour. Data-loss target met: the usable copy is twenty minutes before the cutoff, within the thirty-minute limit. The data-age comparison is separate from the outage bars.

The next action is specific: find what consumed the three hours between restored data and usable ordering. It may be an integration, an unavailable administrator, a license, or a missing procedure. Assign the gap and retest the service after the fix.

Protect the test and the way back.

Ask who can change backup jobs, shorten retention, or delete saved versions. Keep a protected recovery path beyond the access used for normal operations. Offline copies, retention-protected immutable storage, and encryption do different jobs; check the controls and recovery procedure your provider actually supports.

Before the rehearsal, identify the application, data, identities, keys, licenses, compatible hardware, and vendor tools the service needs. Record references to protected credentials, never their values. Keep the existing viable copy while testing a replacement.

Use an isolated restore target agreed with the owner and provider. Block production writes, customer messages, real payments, and live equipment actions. For a controller, involve the person responsible for safe operation and follow the vendor's restoration procedure. NIST's OT backup guide includes configurations, dependencies, and non-production testing for this reason.

During the exercise, record the restore start, data-ready time, business-usable time, and actual usable recovery point with one stated timezone. Have the owner check representative work without sending it into production. Record incomplete results as incomplete, then name the next action and retest date.

After a real intrusion, restoration also needs investigation and a trusted return to service. A restored file does not revoke stolen credentials or recover data already taken.

FREE WORKING TOOL / NO ACCOUNT REQUIRED

Run the rehearsal with a record.

The worksheet keeps targets, protected-copy details, dependencies, safe-test controls, timestamps, and the owner's result together. Keep the completed record restricted to the people who need it.

Open the recovery worksheetFillable PDF

Also check who can still reach the service.