Data Backups are turning into lifelines to businesses as they help firms to recover from data loss in the event of catastrophic disasters. But when we look at the new levels of ransomware doing the damage in 2017, one can easily get a feeling that it’s getting hard to keep the cloud-based backups isolated from ransomware spreading hackers.
But for those storing their critical enterprise data backups on Microsoft Azure, it’s soon going to be Merry Time!
Yes, Microsoft Corporation has made it official that data stored in Microsoft Azure Architecture will/can now be protected from ransomware by default in three efficient steps.
The first step is that the data stored by users will from now be available on 3-4 virtual machines stored in different geographic locations. Means, if your data on-premises gets compromised with ransomware, the user of an Azure backup server could use the data stored on one or several clouds based virtual machines as a part of disaster recovery planning.
Hence, it gives Azure users the privilege to restore their data back to a specific period of time. Therefore, in simple terms, users can keep their data continuity alive all as a part of a predetermined business continuity planning.
The next level of protection offered to users storing backups on Azure is a way to set up a 6-digit PIN number directly from the Azure portal as an additional security layer. This PIN will be available to only authorized users before any backup and restore operation of data is performed.
In-Time notification alerts are the third layer of security protection offered to Azure data backup users. Whenever any suspicious activity is attempted with a backup, a notification is immediately sent to the account admin.
Note- All these days, the privilege to create several backups on virtual machines was left to the choice of premium account holders of Microsoft Azure. But now, in order to save enterprise databases from the fangs of Ransomware encryption, Azure is offering backups onto Azure cloud-based virtual machines by default.