Skip to main content

How can we help you?

Druva Documentation

Ransomware Recovery for Servers

 The availability of this feature may be limited based on the license type, region, and other criteria. To access this feature, contact your Druva Account Manager or Druva Support.

Introduction

The risk of a cybersecurity failure is no longer limited to the reputation of a company, or something to be borne by its customers, but is an existential risk to the company itself. Ransomware extorts the business with the one universal thing all businesses value – their own data. Needless to say, you need to be well prepared for this danger.

In this article, we will help you understand how Ransomware Recovery by Druva can help save the day in case you are unfortunately attacked by ransomware.

In case of an infection, to quarantine is to isolate the infected parts in order to contain the infection and not allow it to spread. To this effect, Ransomware Recovery enables you to quarantine infected snapshots on the impacted resources, which helps safeguard your system from further infection by barring users or administrators from downloading or restoring data to other resources.

To reduce downtime and loss of productivity, you can restore the data from the latest secure snapshot that you deem safe and get the resource operational again.

Here's how you can use Ransomware Recovery to quarantine infected snapshots in the following ways:

  • Manually search for the impacted resource and quarantine the infected or all the snapshots.
  • Integrate Ransomware Recovery with third-party security and incident response solutions and automate the response to quarantine the resources using Ransomware Recovery APIs.

 Ransomware Recovery for Servers supports only NAS Shares and Windows/Linux file servers.

Know the impact of quarantining 

  • After you quarantine snapshots, access to the quarantined snapshots is blocked for the administrators and the users of that resource.
  • Administrators and users cannot download data or restore data from the quarantined snapshots.
    You can identify quarantined snapshots by the blocked icon (cannot select icon.png) displayed beside the snapshot creation timestamp in the Restore Data window.

    restore data window without warning.jpg

 The data in the unquarantined (clean) snapshots of the resource are still accessible and can be viewed, downloaded, or restored by administrators.

Decide your approach

Druva enables you to set up your response to the Ransomware Recovery. You can either manually quarantine snapshots on an impacted server or automate the quarantine process by integrating with third-party security and incident response solutions using Ransomware Recovery APIs.

Manually quarantine infected snapshots

The manual way of quarantining the snapshots on a resource is helpful when you get to know about an impacted server from a trusted source such as the server administrator himself or alerts raised by your security infrastructure and antivirus software about a potential risk.

Prerequisites
Identify the potential date when the resource was infected by ransomware. It helps you decide from which date onwards you want to quarantine the snapshots on the resource.

Note: If you are unaware or not sure about the date, you can start quarantining the snapshots of the impacted resource from the current date or from January 6, 2020, a system-defined limit, before which you cannot quarantine snapshots in Druva Phoenix.

You can always talk to the people in your organization whose servers are impacted and track their potential activities such as the files they downloaded or interacted with on a particular day that infected the server.

Choose the best way to quarantine the resource

You can manually quarantine servers using any of the following available methods -

  • Search and then quarantine a resource - Use this option when you want to search for an impacted resource, identify the snapshots, and then take quarantine action on the snapshots. To use this option, see Search and quarantine a resource.
  • Quarantine resources in bulk using CSV - Use this option when you have to quarantine multiple servers and have the following information available with you to save on your efforts -
    • Organization Name - The name of the organization that contains the server that you want to quarantine.
    • Server Name - Name of the server that you want to quarantine. 
    • From Date - The date from which you want to quarantine the snapshots, in the DD-MM-YYYY format. This should be the date on which the server was impacted. If you do not enter a date, Phoenix will start quarantining all snapshots of the server from January 6, 2020.
    • To Date -  The date till which you want to quarantine the server, in the DD-MM-YYYY format. If you want to quarantine snapshots in a specific time period, enter the date till which Phoenix should quarantine snapshots. If you do not enter a date, Phoenix will keep quarantining snapshots indefinitely. 
      To use this option, see Quarantine snapshots in bulk using CSV.
    • Resource Type - The server type such as File Server or NAS.

Search and quarantine a resource

Use this option when you want to search for a server, identify the snapshots, and then quarantine it.

Procedure

  1. Log in to Druva Cloud Platform (DCP) Console
  2. On the DCP Console dashboard, under Cyber Resilience, click the Ransomware Recovery service.
  3. On the left pane, click Quarantine Bay > Servers
  4. Click Add Resources > Find Resources.
  5. Search for the impacted servers. You can search for servers using either one or a combination of the OrganizationsWorkload Type, and Workload Name.

    add resources to quartine bay.png

  6. Select the servers on which you want to quarantine the snapshots and click Next.
  7. On the Quarantine Response page, select one the following based on the information available with you -
    • Quarantine all snapshots from the impacted date - Choose this option only if you are sure about the date when the resource was impacted. If you are not sure about the date choose the next method, Quarantine all snapshots.
      When you choose - Quarantine all snapshots from the impacted date - you can specify a particular date from which you want to quarantine all the snapshots. Phoenix will keep quarantining all the snapshots formed on the server due to Phoenix backups. Select a date from which you want to mark all the snapshots as quarantined.
      •  You can select snapshots for quarantine not earlier than January 6, 2020.
      •  Phoenix uses UTC timezone to quarantine a resource. You must factor in the difference between the server time zone and UTC zone while selecting the dates. 
    • Quarantine all snapshots - Choose this method to quarantine snapshots if you are not sure about the exact date when the resource may have been impacted. When you choose - Quarantine all snapshots - Phoenix will quarantine all the snapshots after January 6, 2020 (a system-defined limit) and keep quarantining all the snapshots formed on the server due to Phoenix backups.

      quartine all snapshots from selected date.png

7. Click Finish.

Druva Phoenix starts quarantining the snapshots from the mentioned date and also quarantines the snapshots created as part of the regular Phoenix backups. See What's next to take the suggested course of action.

Quarantine snapshots in bulk using CSV

Use this option when you want to quarantine snapshots for multiple servers.

Procedure

  1. Log in to Druva Cloud Platform (DCP) Console
  2. On the DCP Console dashboard, under Cyber Resilience, click the Ransomware Recovery service.
  3. On the left pane, click Quarantine Bay > Servers
  4. Click Add Resources > Import CSV.  The Import from CSV dialog box appears.
  5. Download the sample CSV file.
  6. Open the CSV file and provide the following information in the required format:
    • Organization Name - The name of the organization that contains the server that you want to quarantine.
    • Server Name - Name of the server that you want to quarantine. 
    • From Date - The date from which you want to quarantine the snapshots, in the DD/MM/YYYY format. This should be the date on which the server was impacted.

      If you do not mention any date, Phoenix will start quarantining all snapshots of the servers from January 6, 2020.

      • Resource Type - The server type such as File Server or NAS.
      • To Date -  The date till which you want to quarantine the server, in the DD/MM/YYYY format.  If you want to quarantine snapshots in a specific time period, enter the date till which Phoenix should quarantine snapshots.

        If you do not mention any end date, Phoenix will keep quarantining snapshots indefinitely.

         

    csv import for servers.png

  7. Save the CSV. 
  8. On the Import from CSV dialog box, select the CSV file and click Import.

After the validation of CSV, Druva Phoenix starts quarantining the snapshots on the servers of the organizations mentioned in the CSV.

You have successfully quarantined the infected resources, which will now help contain the ransomware attack. Refresh the Quartine Bay > Servers page to view the quarantined list of servers.

What’s next?

Now that you have now quarantined the infected snapshots, you might be wondering what to do next? You can take the following actions to contain the ransomware and bring up the resource to resume productivity. 

 We highly recommend that you work with your Data Security and IT teams to take appropriate steps to resolve such a situation.

  • Exclude the suspected file types from being backed up. Once you identify the name, file type, file extension, of the ransomware, you can exclude those file types and restrict them from being backed up from other servers.
  • Share the impacted server data with the Data and Information security team of your organization for further analysis of the infected data and the server.
  • Allocate a new server to the user. When you are replacing the infected server with a new server, you can restore the last clean snapshot to the new server during using Restore To Alternate Location option. Once you replace the server, ensure that you unquarantine future snapshots of the impacted server. Otherwise, Phoenix will keep quarantining the snapshots even in the new server. To unquarantine a resource, see Unquarantine a resource.

Unquarantine a resource 

After you have completed the required inquiry into the impacted resources with the help of your Data Security and IT teams, you may find that some resources were falsely marked as ransomware impacted. In this case, you might want to remove the resource and the snapshots from the quarantined state and mark it as clean!

After you unquarantine the snapshots, Phoenix administrators and users can again securely restore and download data from those clean snapshots resulting in no loss of data.

Procedure

  1. Log in to Druva Cloud Platform (DCP) Console
  2. On the DCP Console dashboard, under Cyber Resilience, click the Ransomware Recovery service.
  3. On the left pane, click Quarantine Bay > Servers
  4. Select the resource that you want to remove. 

    UNQUARANTINE SERVERS.png
  5. Click Remove

Once removed, users and administrators can access the data in the unquarantined snapshots and can download and restore it.

Delete infected snapshots of a resource

You might have to clean the existing server or provide a new server to the user after your Data or Information Security teams have completed their analysis on the impacted server.

After receiving access to the new server, the user can restore the last clean snapshot of the old server. Once the restore activity is complete, you can delete the infected snapshots of the server.

Snapshot deletion is an irrecoverable activity. You cannot access and recover any data from the deleted snapshots.  The deleted snapshots are not displayed in the Restore Data window in the Phoenix Management Console.

Procedure

  1. Log in to Druva Cloud Platform (DCP) Console
  2. On the DCP Console dashboard, under Cyber Resilience, click the Ransomware Recovery service.
  3. On the Overview page, click Quarantine Bay > Servers
  4. Click the resource name to view the snapshots of that resource. 
  5. Click the Snapshots tab. The list of all the infected snapshots is displayed.

    snapshots listed servers.png
  6. Select the snapshots that you want to delete and click Delete Snapshot.

Automatically quarantine infected snapshots using APIs

You can use APIs to integrate Ransomware Recovery with your existing security tools or build custom scripts to automatically take action if there is a ransomware attack. 

Here are a few links to help you get started:

The following is a probable workflow if you know the IDs of the infected servers and the date of infection and want to quarantine snapshots using APIs. 

workflow.png

 

 

  • Was this article helpful?