JOTO GLOBAL
← Insights

You Have Backups. Can You Actually Recover from Ransomware?

A recovery drill that checks isolation, data integrity and business restart, not just backup completion.

Server hardware

A successful backup job is only the beginning

A green dashboard confirms that a job ran; it does not prove that a business service can return safely. CISA recommends offline, encrypted backups of critical data and regular tests of their availability and integrity. Start by naming the systems whose loss would stop operations. For each one, document the recovery point, acceptable downtime, application dependencies, responsible people and the location of a protected copy.

Run a clean-room restoration drill

Choose a representative dataset and restore it into an isolated environment. Confirm that the backup is readable, that credentials and keys are available to authorized responders, and that the recovered data matches expected records. Rebuild the supporting application, identity and network components in the required order. Measure the elapsed time from declaring the incident to a usable service, not merely the time needed to copy files.

Define the business service to restore

In a hypothetical example, an order database restores successfully, but staff cannot sign in and the warehouse interface remains unavailable. Shipping still cannot resume. Work backward from business actions to dependencies such as identity, name resolution, databases, application configuration, certificates, interfaces and operator devices. Do not assume they restore with the data, or treat this example as a universal recovery order.

The business owner should identify orders that can wait, processes that can temporarily run manually, and the point at which interruption becomes unacceptable. Technical staff propose recovery order and resources, then both sides confirm priorities. This shows whether investment should improve recovery points, recovery infrastructure, or staff and supplier response.

Make recovery objectives measurable

A recovery point objective defines tolerable data loss in time; a recovery time objective defines tolerable service interruption. Specify systems and measurement boundaries for both. Record incident declaration, environment readiness, backup retrieval, application startup and business acceptance separately instead of reporting only the fastest copying stage. There is no universal hourly target here: objectives should follow business impact analysis.

Check whether backup frequency actually supports the objective: incremental chains, retained versions, accessible media and available key custodians all matter. An off-site copy that requires a failed identity service is still dependent on that service. Include these prerequisites in the plan and in procurement and service acceptance.

Assess trust before restoring

Authorized incident responders should follow the response plan to contain impact, preserve necessary evidence and establish scope. Business urgency should not lead recovery staff to reconnect backups directly to an environment that may remain affected. Review the backup point, known anomalies, administrator access and restoration platform with security staff before selecting a recovery point.

Offline and immutable backups offer different protections, whose effectiveness depends on deployment and administrative permissions. Neither proves that a copy is free of malicious content or that keys and catalogs are complete. Combine post-restore scanning, configuration checks and business sampling. A single passed check is not proof of absolute safety; retain unresolved scope as explicit risk and follow-up work.

Use a bounded drill to expose real gaps

Choose a representative system and approved test data, define isolation, permitted actions, stop conditions and contacts, and then schedule the exercise. Backup administrators retrieve versions; platform staff prepare resources; application staff restore services; security staff examine the environment; and business users perform normal work. A drill lead maintains the overall timeline so teams do not report only their own completed stage.

Test unavailable administrators, an inaccessible primary site or delayed suppliers in separate rounds rather than combine every failure initially. Do not introduce real ransomware or interrupt production without approval. If a stop condition occurs, preserve findings, stabilize the environment and revise the plan. A stopped exercise can still yield valuable evidence.

Accept correctness and continuity, not just startup

After the database opens, business users should check representative records around the recovery point, relevant amount or quantity totals, and consistency between systems. Orders, stock and finance may restore to different times; define reconciliation and controls against duplicate actions. Use approved samples and controlled records instead of copying sensitive data into public screenshots.

Test sign-in, queries, submissions, interface exchange and required reports, then observe for an agreed period. Document the actual recovery point, total duration, missing functions, temporary constraints and sign-off owner. Report partial recovery when that is what was achieved. Server counts and file sizes do not establish that all business services work.

Turn findings into issues that can be closed

Give each failed step an owner, corrective action, deadline and retest evidence. Missing keys require corrected controlled access and alternate custody; insufficient bandwidth requires a measured transfer window; dependence on one employee requires documentation and a test with another operator. Preserve both targets and actual outcomes rather than relax targets afterward to hide failure.

Review dependencies after new systems, backup-platform replacements or identity changes. This is JOTOglobal guidance for organizing exercises, not a replacement for an incident response plan or a guarantee that a product prevents ransomware. The useful deliverable is a verified path to business recovery.

Record evidence and close the gaps

NIST SP 1800-11 stresses that recovery from destructive events requires confidence in the accuracy of restored data. Keep a drill log with the backup version, integrity checks, failures, decisions and business sign-off. Test scenarios in which the normal administrator account or the primary site is unavailable. Treat missed targets as engineering work: remove single points of failure, update runbooks and repeat the drill. An offline copy and an immutable copy can be complementary controls, but neither replaces a demonstrated restoration.

Sources

#StopRansomware Guide

https://www.cisa.gov/resources-tools/resources/stopransomware-guide

Data Integrity: Recovering from Ransomware and Other Destructive Events

https://csrc.nist.gov/pubs/sp/1800/11/final