The Backup Ran. Could the Same Admin Delete It?

  • Home
  • The Backup Ran. Could the Same Admin Delete It?
The Backup Ran. Could the Same Admin Delete It?
Immutable backups illustration: a vault custodian stores blue backup tape cartridges separately from production systems.
AI-generated illustration of isolated backup media in an offsite vault. Offline storage and immutability are distinct safeguards.

Imagine a medical wholesaler starting Monday with its order system offline. Friday’s backup report was green, but the recovery team cannot find a usable copy of the orders and stock allocations. The same account that managed the live system could also delete its snapshots. Immutable backups address that particular weakness: a protected recovery point cannot be changed or deleted during its retention period, even if some administrative credentials are compromised. The scope of that protection depends on how it was configured.

What immutable backups protect, and what they don’t

A successful backup job tells you that the scheduled copy ran. It does not tell you who can remove that copy, shorten its retention or make it unreadable. A snapshot under the same administrative controls as the live service may be useful for rolling back a mistake, but it may not provide a separate recovery option after a compromise. An immutable copy has a retention rule enforced by the storage or backup platform. An offline copy uses a different safeguard: it is disconnected from the live environment. Both can be useful, but the protections are not interchangeable.

Take the wholesaler’s customer order. Restoring the invoice PDF is not enough if dispatch cannot tell whether the order shipped, which stock was allocated or whether a credit was issued. And a protected copy can still contain corrupted data or changes made before the incident was detected. The business needs enough history to select a suitable recovery point, plus the ability to restore the records and settings that make those records useful.

Ask who can delete the copy, and who can read it

Have IT or your provider show you the permissions on an actual protected recovery point. Start with the identities you use every day: can an ordinary production administrator remove the copy, alter its retention or grant themselves the right to do so? Then ask the same question about any backup administrator and any documented emergency override. ASD’s Essential Eight maturity model goes as far as preventing backup administrators from modifying or deleting backups during their retention period at Maturity Level Three. That is a useful reference point, not a claim that every SME must adopt that level.

Check the other side of the boundary as well. If the primary login service is unavailable, can the recovery team still authenticate through an approved route? Who controls the encryption keys and can they be made unavailable through the same administrative account? A lock on the files does not by itself protect the keys or guarantee that the people on call can reach the backup. Keep emergency access tightly controlled and audited, and document who can authorise its use.

Make one recovery decision with evidence

  • Operations chooses the result. Pick one critical workflow, such as continuing existing orders without shipping them twice. Agree how much recent work the business can reconstruct and how long staff can operate manually.
  • IT demonstrates the boundary. Capture the scope, expiry and permissions of a protected test copy. Use a disposable test dataset to confirm that routine administrators cannot delete it, without touching the last good production recovery point.
  • The recovery team proves it can work. Restore to an isolated environment while treating production credentials as unavailable. Check that the application opens, reconcile sample orders and stock against a known point in time, and record how long the exercise took.

Longer protection buys more time to discover a problem, but it can also increase storage cost and complicate information retention. Set the window with the business owner rather than accepting a default. Immutable backups improve recovery options; they do not prevent data theft or replace incident response. If your business is reviewing those trade-offs, Xpansion’s managed IT and security services include scoped backup and recovery planning.

References