Build a ransomware-resistant backup baseline
Separate backup identity and infrastructure, keep immutable or offline copies, and prove recovery with measured exercises.
Scope
For organisations designing or reviewing backup protection against destructive incidents.
Start with the situation, not the slogan
Hardening is the practice of making the safe path ordinary and the dangerous path conspicuous. Build a ransomware-resistant backup baseline is not a demand to enable every severe-looking setting. It is a measured baseline: understand the service, reduce unnecessary exposure, protect privileged changes and prove that the business function still works.
Begin with inventory and ownership. A control applied to an unknown dependency is not defence in depth; it is surprise as a service. Record the current state, define the rollback condition and change one coherent control group at a time. The result should be supportable by the people who will receive the telephone call six months later.
Attackers often target backup consoles, credentials, retention, and connected repositories before encryption. Recovery requires protected copies and a clean path to use them.
Composite scenario
How this usually reaches the desk
Assume a routine review records the following condition: “Backup administrators share production identities or use the same management devices as daily operations.” The appropriate response is not a mass edit copied from a checklist. Establish which systems share the condition, which legitimate workflow depends on it, and how a safe pilot will demonstrate improvement. A baseline earns trust by surviving both an attack-shaped test and an ordinary Monday.
This scenario combines common operational patterns; it is not presented as a report of one named incident.
What to look for
Begin with preserved, comparable evidence. One signal is rarely proof; use independent observations and a reliable timeline before declaring scope or intent.
Backup administrators share production identities or use the same management devices as daily operations.
Measure the current state and identify the owner before proposing a target. Configuration without ownership quietly returns to folklore after the next upgrade.
Every copy is online, mutable, reachable from the same control plane, or dependent on one provider.
Separate necessary exceptions from historical accidents. An exception needs a reason, compensating control, approver and review date; otherwise it is merely a setting wearing formal clothes.
Restore tests check files but not applications, identities, keys, DNS, capacity, or business transactions.
Look for enforcement and telemetry together. A blocked action should leave a useful record, while an allowed action should remain understandable to support staff and service owners.
Working examples
Run it, read it, decide what changes
These examples use documentation addresses, test identities and bounded targets. Replace placeholders only inside systems you own or are explicitly authorised to operate. Read the expected result and next action before running the command; a successful command is evidence, not yet a conclusion.
List snapshots and verify repository structure
- Prerequisites
- Repository access configured through a protected credential source.
restic snapshots
restic checkSnapshots are listed and repository metadata/data references are checked.
A check can succeed even when the selected restore is application-inconsistent or credentials depend on the failed production system.
Record the latest usable snapshot time and perform a restore to a separate destination.
Restore one snapshot without overwriting production
- Prerequisites
- Empty target storage and the snapshot ID selected from the inventory.
mkdir -p /srv/restore-test
restic restore SNAPSHOT_ID --target /srv/restore-test
find /srv/restore-test -type f | wc -lRestic reports restored files and the count provides a simple completeness lead.
File count is not business validation. Databases and directory services need supported consistency and recovery procedures.
Start the restored application isolated, run owner-approved integrity checks, and measure actual recovery time.
Sample repository data on a schedule
- Prerequisites
- A maintenance window and enough bandwidth for a bounded read.
restic check --read-data-subset=5%
restic forget --dry-run --keep-daily 7 --keep-weekly 5 --keep-monthly 12A data sample is read; the retention command previews what would be kept and removed without deleting anything.
Sampling changes the probability of finding corruption, not certainty. Dry-run output must be reviewed before any prune.
Rotate through subsets over time, alert on failed jobs, and keep at least one restore path isolated from production credentials.
What to do
Read the whole sequence before starting. Several workstreams may run in parallel, but their evidence, authority and expected outcomes still need to be explicit. Every step below points back to a concrete example; use the example as implementation evidence, not as permission to operate outside the stated scope.
Operational judgement
Controls age. Products change defaults, licences move features, teams replace applications and carefully written exceptions outlive the systems that inspired them. Review the baseline for Backup, Ransomware and Recovery after material upgrades and incidents, and on a scheduled cadence. The review should remove obsolete rules as readily as it adds new ones.
Measure outcomes rather than configuration volume. Useful evidence includes reduced exposed services, stronger authentication coverage, tested recovery, fewer standing privileges and alerts that an operator can act upon. A longer policy is not automatically a safer policy; sometimes it is merely more difficult to print.
Handover
Make the result useful to the next person
Publish the baseline with its purpose, scope, authoritative management path, minimum supported versions, dependencies, allowed exceptions, monitoring, rollback and review date. Show the delta from the previous state rather than distributing a mysterious final configuration. Service owners should know which user-visible behaviour may change and where to report a legitimate failure. Security owners should know what event proves that the control blocked or detected the intended case.
The implementation record should connect “Map critical services to recovery point, recovery time, dependencies, owners, and required recovery evidence.” to the verification required after “Run scheduled restore exercises into an isolated environment and measure actual outcomes.” Include pilot population, success measures, support findings and every approved exception. If the control cannot be continuously measured, schedule a repeatable audit. A baseline is healthy when operators can explain it, new systems inherit it, exceptions remain scarce and visible, and removal of an obsolete rule is treated as maintenance rather than heresy.
Validate before you close
The baseline is proven when a clean team can recover the priority service from a protected copy within agreed objectives and document every dependency.
Capture the test, the expected result and the observed result. Where a person or business owner must accept restored service, name them in the record. A green dashboard can confirm that a component is answering; it cannot confirm that invoices, identities or restored data are trustworthy.
Finish with a compact closure note: the original trigger, confirmed scope, evidence retained, controls changed, tests passed, known gaps, residual risk, and the people responsible for the remaining work. Schedule a review while the timeline is still fresh enough to challenge. The purpose is not to find a person to blame; computers already perform blame with admirable efficiency. The purpose is to make the next response faster, safer and less dependent on one person remembering where the useful log was hidden.
Common mistakes
- Changing many controls at once without a rollback path.
- Applying a generic baseline without documenting business exceptions.
- Assuming a setting is effective without testing both normal use and a blocked case.
These errors usually come from haste, unclear ownership or misplaced confidence. Build the safeguard into the runbook: a required evidence field, a second-person review, a rollback test or a specific exit criterion.
Questions people ask when the clock is running
Should we apply every recommendation at once?
No. Group related controls, pilot them, define rollback and expand only after verification. Large undifferentiated changes make both outages and security improvements difficult to attribute.
What makes an exception acceptable?
A business reason, narrow scope, accountable approver, compensating control, expiry or review date, and evidence that the residual risk is understood. “It broke once in 2019” is useful history, not permanent governance.
How is the baseline verified?
The baseline is proven when a clean team can recover the priority service from a protected copy within agreed objectives and document every dependency. Re-test after significant platform changes and keep the result with the control record.
Safety boundary
Use these steps only on systems you own or are explicitly authorised to assess. Preserve evidence, follow your organisation’s legal and regulatory obligations, and prefer reversible actions when the situation is not yet understood.
Primary references
Editorial status: first edition. Review the linked vendor documentation for product- and version-specific changes before acting.