If our systems were locked by ransomware tomorrow, could we restart the business from our own backups without paying, and how long would it take?
Whether the company can restore without the attacker's help is the single fact that most shapes a ransom decision. Without a recent test, the board only finds out the true answer during an attack, when it is too late to fix it.
What a strong answer includes
- Gives a restore time for the core business taken from a real test in the last year, not an estimate, and names what was restored in that test.
- Explains why the attacker could not delete or encrypt the backups, for example because a copy is kept offline or cannot be changed for a set period, and says when that was last checked.
- Includes the systems everything else depends on, such as user accounts and network services, which often have to come back before anything else can.
- Sets out the agreed order in which systems return, with the business saying how long each can be down, and how much data could be lost between the last backup and the attack.
- Is honest about the gaps, such as systems that have never been restored in a test, and says what it will cost and how long it will take to close them.
What a weak answer sounds like
- “Yes, we back everything up every night.” Taking backups is not the same as being able to restore from them.
- “Our recovery time objective is four hours.” A target written in a policy, not a result anyone has measured.
- “Our cloud provider handles that.” A provider protects its own service. Whether our data survives an attacker using our own accounts is usually our job.
If the answer is weak, ask
When did we last restore a core system from backup in a test, how long did it actually take, and what went wrong?
Red flags
- No full restore of a core system has been tested in the last year, or the test was a single file.
- The backups can be reached with the same administrator accounts the attacker would be trying to steal.
- The restore time quoted is a target from a policy and nobody can say when it was last achieved.
- The business has never been asked which processes must come back first.
Ask for in writing
- The report from the most recent restore test, with the time taken and the problems found.
- A one-page description of how backups are protected from deletion or encryption by an attacker, confirmed by someone independent of the team that runs them.
- The agreed restore order for critical systems, signed off by the business owners.
- A list of the systems that have never been restored in a test, with a plan and date for each.