VK Cloud logo

Ensuring data safety in case of a cyberattack or insider threat

Using the Cloud Backup service, you can protect backups from deletion or integrity changes by enabling deletion lock in Compliance mode for a backup plan. In this mode, backups or part of them cannot be deleted until the specified period expires — including via technical support. This guarantees data safety in the event of a cyberattack, account compromise, or insider threat from privileged users. At the same time, the deletion lock does not prevent restoration from a backup — it only prevents deletion and integrity changes of the backup itself.

The following data is used as an example:

  • Virtual machine name: secure-vm
  • Backup plan name: compliance-locked-plan
  • Retention period: 3 days
  • Protection mode: Compliance

Preparation steps

  1. Go to the VK Cloud personal dashboard and make sure the Cloud Backup service is available in the project.

  2. Make sure the project contains a virtual machine for which you need to configure protected backups. The secure-vm VM is used as an example.

  3. Determine the backup retention period in days in accordance with compliance requirements or regulations (for example, Federal Law No. 152-FZ).

1. Create a plan with a deletion lock in Compliance mode

Create a backup plan for the virtual machine. Specify the following parameters:

  • Plan name: compliance-locked-plan.
  • Resource type: Virtual machine.
  • In the list of VMs, select secure-vm.
  • In the Days of full backup creation field, select the days of the week (for example, all days) and specify the time (for example, 02:00).
  • (Optional) Enable the Enable incremental backups option so that incremental copies are created on days without a full backup.
  • In the storage approach selection block, enable the Enable non-removable backups option.
  • Select the lock type: Temporary protection.
  • In the retention period field, specify 3 days.
  • In the protection mode selection field, select Compliance to enable (a strict lock).

2. Verify that the lock is applied to backups

  1. Wait for the first scheduled backup run.

  2. Make sure the compliance-locked-plan plan is marked with a lock icon (protected).

  3. View the list of backups of the secure-vm VM for the compliance-locked-plan plan.

  4. For each created copy, hover over the lock icon next to the name. Make sure the following is displayed:

    • Lock type: Compliance.
    • Lock period: 3 days (or the remaining days until expiration).

3. Verify that everything works

  1. Restore the secure-vm VM from a protected backup to a new instance.

  2. Wait for the restoration to complete.

  3. Check the restored VM:

    • Make sure the VM is created and running.
    • Verify the integrity of the data on the restored VM.
  4. Make sure the protected copy cannot be deleted ahead of schedule. In the list of backups, try to select Delete copy for a copy with an active Compliance lock — the operation should be unavailable until the period expires.

Delete unused resources

The created resources are billed. If you no longer need them:

  1. Delete the secure-vm virtual machine if it is no longer needed.

  2. Delete the VM restored from the backup if it is no longer needed.

  3. Delete the backup plan after the lock period ends if the copies are no longer needed.

Was this article helpful?