Ransomware backup and restore drill
Ransomware hit at 01:40. Choose a clean, intact restore point for a domain controller, a file server, and a database, within each recovery time objective.
- Interactive lab
- Advanced
- 5 graded steps
- 0 of 5 solved
This lab is part of The first hour of a ransom note.
Your goal
Your goalPick a clean, intact restore point for each of three systems, within its recovery time, losing as little data as possible.
It is Sunday morning, 1 November 2026. Ransomware encrypted the file server and the finance database at 01:40 UTC. Containment is done, and the incident lead asks you for the restore plan.
For each system, choose the restore point to use. A good point is intact, taken before anything the attacker touched on that system, restorable within the system’s recovery time objective (RTO), and as recent as possible.
What’s on screen
- Incident timeline (UTC)
- the top panel. It lists what the attacker did and when, in Coordinated Universal Time.
- System tables
- one table per system with its RTO (recovery time objective, the longest outage allowed). Each row is one backup copy.
- Use
- the round button at the start of each row. Pick one per system.
- Walkthrough
- the numbered path beside the workbench (below it on a phone). Each step says what to do and what you should see. Hints open one at a time.
Words to know
- RTO
- recovery time objective, how long you can afford to be down
- •
2026-10-21 22:05VPN sign-in with a stolen contractor password (found later in VPN logs) - •
2026-10-24 03:10Scheduled task and a new account svc-health created on DC01 - •
2026-11-01 01:22NAS snapshots deleted with the domain backup admin account - •
2026-11-01 01:40Encryption starts on FS01 and ERP-DB; ransom note appears - •
2026-11-01 01:45Sync replica copies encrypted files from FS01
| Use | Copy | Taken | State | Restore time |
|---|---|---|---|---|
| NAS snapshot | 2026-10-31 23:00 | deleted | 2 h | |
| Immutable object storage (system state, nightly) | 2026-10-31 23:00 | intact | 3 h | |
| Immutable object storage (system state, weekly) | 2026-10-25 20:00 | intact | 3 h | |
| Immutable object storage (system state, weekly) | 2026-10-18 20:00 | intact | 3 h |
| Use | Copy | Taken | State | Restore time |
|---|---|---|---|---|
| Sync replica | 2026-11-01 01:45 | encrypted | 1 h | |
| NAS snapshot | 2026-11-01 01:00 | deleted | 2 h | |
| Immutable object storage (nightly) | 2026-10-31 23:00 | intact | 7 h | |
| Offline tape (weekly, offsite) | 2026-10-25 20:00 | intact | 30 h |
| Use | Copy | Taken | State | Restore time |
|---|---|---|---|---|
| Standby replica (domain-joined) | 2026-11-01 01:41 | encrypted | 1 h | |
| Immutable nightly full + hourly log backups | 2026-11-01 01:00 | intact | 5 h | |
| Immutable nightly full only | 2026-10-31 23:00 | intact | 4 h | |
| Offline tape (weekly, offsite) | 2026-10-25 20:00 | intact | 26 h |
0 of 3 systems planned.
Read first
More in Risk and resilience
The whole walkthrough
Every step in order: 290 words, about 2 min. It gives away every answer, so try the steps first.