Ransomware targeting backup copies
Locking can prevent protected versions from being modified or deleted.
Object Lock helps protect your backup copy against modification and deletion for a period you define.

A backup copy is part of your recovery plan. If it can be deleted too, recovery becomes harder. Locking that copy reduces this risk.
Locking can prevent protected versions from being modified or deleted.
Accidental deletion or cleanup should not remove a copy under a valid lock.
Protection also depends on lock mode and separate permissions. Configure both together.

Immutability preserves information without change. WORM allows a copy to be written once and read repeatedly without altering the protected version during the lock period.
Configure protection in practice. Choose lock mode and duration, then verify that the policy applies to the required backup versions.
Change the day, choose a lock mode and check the result. Try recovery too: the protected copy stays in place.
The copy was created on day 0 and locked for 30 days.
Changing a setting resets the demonstration copy.
The demonstration tests deletion of a specific version under S3 principles, assuming read and delete permissions. Lock expiry does not delete the copy automatically. Explore lock principles
Ask two questions: who can read the data, and who can delete it? Each requires an appropriate protection layer.
Combine encryption, locking and precise permissions to protect both confidentiality and your recovery copy.
Two roles. One shared goal.Content is unreadable without the correct key or password. Protect those credentials so recovery remains possible.
The protected version is retained against changes and deletion under its lock conditions. Locking alone does not encrypt content.
Default and GFS determine which copies receive a lock. Protect data written to a destination, selected full backups or a combination.
Set a lock period at the storage destination and align backup settings. In the supported workflow, new data written to the destination receives default protection, even without selecting GFS copies.
Default is configured at storage and destination level. GFS applies to full backup sets selected in the plan retention policy, using a supported format. When combining them, align baseline locking with longer-term copy periods. Verify the effective settings on versions actually written. Microsoft 365 and Google Workspace backup also requires a retention policy assigned to the user or domain.
Governance allows exceptions with special authorization. Compliance enforces a stricter lock. Choose according to operational requirements and organizational policy.
| What should you check? | GovernanceProtection with an authorized exception | ComplianceStrict locking for a defined period |
|---|---|---|
| Deleting a version during the lock | Blocked without bypass permission. | Blocked, including for the account administrator and root. |
| Bypassing before expiry | Possible with special permission and an explicit bypass request. | No ordinary bypass using user permissions. |
| Shortening the lock period | Only possible under the appropriate bypass conditions. | A valid lock cannot be shortened or removed. It can be extended. |
| Reading and recovery | Available to authorized users. | Available to authorized users. |
| Who is it for? | Organizations needing protection with controlled administrative flexibility. | Organizations needing strict enforcement of retention periods. |
This comparison concerns object-version protection within an active storage account. Locking does not preserve encryption keys or replace recovery planning. Selecting Compliance mode does not certify regulatory compliance; align the service with the relevant requirements.
Bypass permissions and administration: AWS documentationThe documentation lists support for the following destinations. Check backup type, software version, account permissions and destination capabilities before deployment.
S3-compatible storage: Compatibility depends on Object Lock implementation and permissions. Verify it in practice before configuring a backup plan.
Microsoft Azure and Google Cloud: Retention locking is configured at storage level. Settings not retrieved automatically require manual alignment in the backup system.
Details that help you choose appropriately and know what to expect.
Useful to know in advanceYes. Object Lock restricts modification and deletion of the protected version without preventing authorized reading and recovery. Valid permissions, encryption keys and a recoverable backup chain are still required.
No. Storage and backup settings must be enabled and aligned. Default protects new data written to a suitable destination; GFS protects full copies selected in the policy. Verify that the relevant versions actually received a lock.
Expiry alone does not delete the copy. Without Legal Hold or another protection, it may become eligible for deletion under permissions and the configured retention or lifecycle policy.
No. It protects a locked version against modification or deletion. It does not scan content or repair data damaged before backup. Combine it with cybersecurity, additional copies and recovery testing.
It depends on the provider and product integration. AWS, for example, permits enabling Object Lock on an existing bucket, but default retention does not automatically lock existing versions. Check backup support, existing versions and configuration requirements separately.
Start with how far back the business must recover, which points need long-term retention and the data volume. Locked copies continue using storage, so plan backup, retention and lock periods together.
Tell us what you back up and how long you need to retain it. We will explore how backup locking fits your environment.
Your data is worth protecting.