Data is the lifeblood of today’s enterprises, and an extremely lucrative target for attackers. Ransomware, which essentially holds data “hostage” by encrypting it until a ransom is paid by the company, is increasingly common and becoming more advanced every day.
In fact, some estimates say that a ransomware attack occurs every 11 seconds. These attacks can cripple an organization, causing unexpected downtime and wreaking havoc on an enterprise’s operations, production, customer service, and even future reputation.
It can cost a lot of time, effort, and money to recover from a ransomware attack. Simply having a backup of your data is no longer sufficient, because attackers can now infiltrate backups as well.
In addition to practicing “defense in depth,” IT professionals are now beginning to see the critical need for immutable backups as a last line of defense from ransomware and other attacks—and a smart way to maintain a successful strategy for business continuity and disaster recovery.
होस्ट: एंडी व्हाइटसाइड
सह-मेजबान: हार्वे ग्रीन
सह-मेज़बान: जिराह कॉक्स
Why Backups Are a Ransomware Target
Backups are the last resort when an attack succeeds, which is exactly why attackers go after them. Ransomware can do to a system whatever the logged-in user can do. That includes local drives, network drives and file shares. If a user or an administrator account can modify or delete the backup repository, so can malware running under that account.
The common pattern is to encrypt data and then remove the original. If the backups sit on an ordinary network share and are reachable with the same permissions, they can be encrypted or deleted too. Simply having a backup is no longer enough.
What Immutable Means
An immutable backup cannot be changed or deleted for a defined period. It is possible to approximate this on conventional storage with file permissions and access control lists, but that depends on the administrator configuring the platform correctly. True immutability is built into the storage medium itself.
New backup data can still be written on whatever schedule the organization uses, whether hourly, nightly or weekly. A short cool-down window may allow changes at first, after which the data is locked. Under a retention policy, even an administrator should not be able to delete the data sooner than the policy allows. A compromised privileged account is then unable to wipe out the recovery copy.
Object Storage as the Backup Target
Object storage, accessed through the S3 protocol, is well suited to this job. Unlike the SMB or NFS shares that backup software has traditionally written to, an object store can enforce write-once behavior at the platform level. Nutanix Objects provides this, and it can act as the backup target for third-party backup software.
Nutanix Mine combines the backup application and the storage on one cluster, so the same system serves as both backup appliance and repository. Organizations can also run Objects on its own and bring their own backup application. Either way, the immutability is a property of the storage.
Benefits Beyond Ransomware
Immutability also addresses other concerns. It protects data integrity, since a backup that is written should be there when a restore is needed. It simplifies compliance for backups that fall under retention requirements, and it removes the risk of accidental changes or deletions made by well-meaning staff.
Practical Requirements for Implementation
A sound implementation starts with a platform that enforces write-once behavior as a feature, not as a configuration that can drift over time. It also applies zero trust principles, with authentication enforced and access limited to what each person needs. Administrators are increasingly asking how little access they need to do their jobs, since unnecessary access is a liability.
Backups should be scanned for signs of tampering or malware before a restore, to avoid reintroducing the infection. Teams should also track the impact of each incident, including the hours spent on recovery and verification. A single clicked link that leads to dozens of hours of lost productivity is a powerful way to show the business why prevention matters.
Layered Protection
Non-persistent virtual desktops that reset to a gold image are one familiar example of immutability. User profiles and redirected files still need a tested rollback process, and cloud services such as email and file sync need their own backups. Assuming a SaaS service does not need a backup is a common mistake. Immutable backup is one layer in a broader strategy that also includes least-privilege access and recovery procedures that are practiced in advance.