Wasabi Object Lock

Immutable Storage, Immediately Available

With Wasabi Object Lock, your data is offsite, unchangeable, and available at a moment’s notice should you need immediate access to your backups.

Try Free
Contact Sales

What is Wasabi Object Lock?

While offline tape backups or hard drives may seem like the safest place for all your essential data, removing them from the network means restorations can take many hours or even days. 

With cyberattacks, equipment failure, natural disasters, and plain old human error, you never know when you’ll need your backups to go live. Hours or days of downtime just won’t do.

Immutable storage increases cyber resilience

With Wasabi Object Lock, your data is secure, offsite, and available at a moment’s notice should you need immediate access to your backups. It’s also free with Wasabi, with no added API request charges or hidden fees to enable Object Lock or recover data.

Learn About Object Lock

Data protection

Create a modern air gap through encryption and hashing. Immutable objects, locked individually or as part of a broader bucket policy, cannot be deleted or altered in any way, not even by a system administrator.

Compliance

Use Wasabi Object Lock to ensure the chain of custody and regulatory compliance of data. It helps you meet multi-year and other data retention requirements for HIPAA, SEC, FINRA, FERPA, CJIS, and others.

Seamless integration

Easily connect Wasabi through a compatible S3 Object Lock API and set or manage retention periods per object or per bucket. We’re verified for Veeam Backup and Replication v10, v11, and v12 among other applications.

Veeam users and anyone looking for affordable long-term backup storage or facing ransomware attacks like us should sign up for Wasabi. The way it integrates, the ease of use, and its ability to protect your business’s backup data is unrivaled.  

Brian Fraley, Senior Enterprise Infrastructure Architect, Aquatech International 

Aquatech logo

We use both Veeam’s and Wasabi’s immutability. They’re perfect to prevent any sort of cyber-attack. We have a 365-day setting where those backups can’t be touched or deleted for a full year. 

– Kyle Begle, Network Administrator, Clarke University 

Clarke University Logo

Ready to lock out data loss with Wasabi?

Try Free

Case Study

Ensuring HIPAA compliance with affordable immutability

Discover how BrightStar Care protected their private medical and personnel data from ransomware attacks with Wasabi.

Read the Case Study
View all case studies

Wasabi’s Object Lock has been a game-changer for us. It allows us an additional level of ransomware protection that we did not have before. It’s easy to use and easy to manage.

Kyle Burnette, Director of IT Infrastructure, Brightstar Care

Covering all the bases

Understand how Wasabi Object Lock might play an essential role in your data protection and resilience strategy. 

Protect data from ransomware with immutable storage

Backups are a favorite target of cybercriminals because encrypting both your primary systems and backups increases the pressure to pay their ransom.  

Creating an immutable backup file adds failsafe protection to your defense-in-depth approach to cybersecurity. 

Explore Cyber Resilience
Secure

Easily integrated across solutions providers

Discover validated partner solutions supporting S3 Object Lock with immutable storage.

Find a Partner
Standard Veeam Logo
MSP360 Knockout
Backupassist-logo-white
Hycu Logo
Commvault Logo Knockout
SEP logo white
Veritas Logo White
Arcserve logo white
Atempo logo white
Naviko Logo White
Comet logo white
Kasken-k10-logo-wht
catalogic

Related Resources

More to discover

The Bucket Fallback
Blog

There’s a gaping hole in your ransomware protection plan

Got questions?

Check out answers to these frequently asked questions about Wasabi S3 Object Lock.

Object lock is a data storage feature of Wasabi Hot Cloud storage that allows customers to designate certain objects to be immutable, meaning they cannot be altered or deleted by any application or user during a fixed date range defined by the user.

Immutable storage is a class of data storage which cannot be altered or deleted until the end of a set period of time.

Immutable storage is recommended as part of a ransomware and cybersecurity strategy that includes spreading data backups across multiple storage mediums, including an immutable backup copy of critical data, to avoid having a single point of failure within your system.

Immutable storage cannot be altered or deleted by anyone, including Wasabi engineers. All immutable storage is created with a set retention period and at the end of this period the data stops being immutable. Once the files are no longer immutable, they can be deleted.

Data stored with Wasabi can be made immutable through Wasabi Object Lock or by placing it in an immutable bucket.

Object lock enables customers to customize immutability and retention periods for each individual object. This granular control makes object lock an excellent fit for data that needs to be protected but may change over its lifetime, like backup data.

In an immutable bucket, all objects share the same immutability and retention settings. Immutable storage buckets are ideal for long-term protection of data such as archives and primary data storage as well as an important element in a ransomware protection strategy.

With compliance mode, a protected file or object can’t be overwritten by anyone, including any level user or even Wasabi engineers. When an object is locked in compliance mode, its retention date can’t be shortened, and it will remain immutable until the end of its retention period.

With governance mode, only users with special permission, such as the root user in the account can reduce the retention settings. This allows you to grant special permission to some users if necessary.

There is no additional charge for using Object Lock and immutable storage with Wasabi.

No. To use Wasabi Object Lock it must be enabled at the time a bucket is created. Buckets using object lock must also have versioning enabled. This is the same process required when using AWS S3.