Covert Copy: Safeguarding Your Data

Prev Next

Wasabi’s Covert Copy is an effortless way to safeguard your data by creating a locked copy of your S3 bucket. Covert Copy is easy to implement without configuration requirements or technical knowledge. The Covert Copy feature:

  • Replicates all or filtered content of your source bucket as an immutable and indestructible copy.

  • Ensures that the copied bucket cannot be modified in any way. This provides a secure long-term backup to prevent data loss.

  • Completely isolates the copied bucket from all programmatic and user interface access without MFA (Multi-Factor Authentication) and MUA (Multi-User Authentication) approval. This stops internal data leaks and unauthorized access.

Only a Root user can manage the covert copied bucket, and implementation requires the use of:

Before you create a covert copy of a bucket, note that:

  • You cannot delete the covert copy bucket for a minimum of 30 days.

  • The covert copy bucket will renew automatically until you disable the auto-renewal feature in settings.

  • Storage in the covert copy bucket will be charged in accordance with your current rate/plan.

When you create a covert copy bucket, you acknowledge these conditions.

Recommendations

The Covert Copy feature is Wasabi’s number one recommendation to protect your data from ransomware attacks, malicious data deletion or modification, and accidental data loss. A covert copy of your bucket protects your data, and the following are recommendations to maximize the value of this protection.

  • Wasabi recommends you have at least one covert copy of each of your most sensitive buckets or folders at any given time. It is also important that you refresh these every 30, 60, 90, or 120 days to ensure the data that you covert-copied remains current.

    When refreshing covert copies, create a new covert copy and then wait for the new covert copy to finish populating before deleting older covert copies.

  • Wasbi recommends you create your covert copies in a region different from the source bucket from which you are creating the covert copy. This will reduce geographic risk associated with events such as natural disasters.

  • If you are using a backup application, Wasabi recommends pausing your backup jobs before creating a covert copy. Unpause your backup jobs when the covert copy has been fully populated.