Day: October 23, 2026

Why Every Backup Plan Now Needs a Copy That Cannot Be Changed

Why Every Backup Plan Now Needs a Copy That Cannot Be Changed

Ransomware groups learned some time ago that encrypting a company’s files is not enough. If the company can restore from backup, it has little reason to pay. So many attacks now go after the backups first, deleting or encrypting them before the main systems are touched. Data protection vendors such as Veeam have responded by building features around one idea, which is keeping at least one backup copy that nobody can alter or delete for a set period.

For many organisations, that single copy is the difference between a hard week and a business that cannot recover.

How Attackers Reach the Backups

Most backup systems are connected to the same network as the servers they protect. That makes daily backups easy to run, but it also means an attacker who gains administrator access can often see the backup storage too.

Once inside, attackers commonly delete backup files, change retention settings so older copies expire early, or encrypt the backup storage along with everything else. Some wait for weeks before acting, so that even older backups already contain their tools.

None of this requires advanced skills. Stolen passwords and weak administrator accounts are often enough.

Veeam

What an Immutable Backup Is

An immutable backup is a copy that is locked for a fixed period after it is written. During that time it cannot be changed, encrypted or deleted, even by a user with full administrator rights. When the lock period ends, the copy can be removed in the normal way.

This lock can be applied in different places. Some cloud storage services offer object lock features. Certain backup appliances and hardened Linux repositories provide the same protection on local storage. Tape stored offline gives a similar result through physical separation, since a tape on a shelf cannot be reached over a network.

Finding Problems Before Restoring

A locked copy protects against deletion, but it does not tell anyone whether the data inside is clean. If malware was already present when the backup ran, restoring that copy can bring the infection straight back.

This is why scanning backup data has become common. Platforms like Veeam can watch backup data for unusual changes, such as a sudden jump in encrypted files, which may signal an attack in progress. Scanning a restore point before bringing it back into production helps teams pick a clean version.

Keeping several restore points over a longer period also helps. If the latest copies are affected, an older clean copy is still available.

What the First 72 Hours of Ransomware Recovery Look Like

What the First 72 Hours of Ransomware Recovery Look Like

Ransomware rarely arrives at a good time. Often it is an alert at 2 am on a Saturday, servers that will not boot and a ransom note on every shared drive. Companies such as Veeam make the backup tools most recoveries depend on. What really decides the outcome, though, is the order of work over the first three days.

The First Day, Containment and Investigation

Restoring too early is the costly mistake. If the attacker still has access, restored servers can be locked again within hours.

  • Infected machines come off the network, left powered on where safe to keep evidence.
  • Suspicious admin accounts are disabled and remote access tools switched off.
  • The cyber insurer gets an early call, since many policies only cover approved responders.
  • Australian businesses with turnover above $3 million generally must report ransom payments within 72 hours.

Investigators then trace how the attacker got in. The backup team checks whether backups were touched. Immutable copies, locked against changes for a set period, and offline tape usually survive.

The Second Day, Finding a Clean Copy

The newest backup may already contain the attacker’s tools, since many groups wait days or weeks before striking. Teams work backwards through restore points. Veeam and similar platforms can scan backups for malware and unusual changes to help find the last clean one. Many organisations restore into an isolated clean room first, testing systems away from the main network.

Veeam

The Third Day, Restoring in Order

Systems return in waves.

  • Identity systems such as Active Directory first, with all passwords reset.
  • Networking, DNS and security tools next.
  • Priority business systems after that.
  • Archives and minor systems last.

Each system is patched before staff log back in, and monitoring stays heightened for weeks.

What Makes the Difference

Fast recoveries usually rest on work done months earlier. That means a backup copy attackers could not reach, a recent restore test, an agreed list of priority systems and contact numbers stored somewhere other than the encrypted server.