Object Lock and Immutable Storage
What you'll learn: How to enforce write-once-read-many (WORM) policies that prevent data modification or deletion, protecting against ransomware and ensuring regulatory compliance.
What Is Immutable Storage?
Immutable storage makes data unchangeable after it's written. Think of it like inscribing text in stone—once carved, you can't erase or alter it. Object Lock is a cloud feature that enforces this principle by preventing objects from being overwritten or deleted for a specified retention period.
This protection operates at the storage layer itself, meaning even administrative users or compromised credentials cannot violate the lock. It's your last line of defense against ransomware that tries to encrypt or delete your backups, and it's often mandated by regulations like SEC 17a-4 or HIPAA.
Two WORM Modes
Governance mode allows specially-privileged users to bypass retention if absolutely necessary (useful for testing or exceptional circumstances).
Compliance mode is stricter—no one, not even the account owner, can delete or modify locked objects until retention expires. Once enabled, compliance mode itself cannot be disabled.
Retention Strategies
You can set retention in two ways:
- Retention period: Lock objects for a fixed duration (e.g., 7 years from creation)
- Legal hold: Indefinite lock until explicitly removed (useful during litigation)
These can be combined with versioning (which you've learned) to preserve all object versions, with locks applying per version.
Real-World Protection
A ransomware attack encrypts your production data. Thanks to Object Lock on your backup bucket with 30-day retention, attackers cannot delete those backups. You restore from immutable copies and recover operations—the lock prevented catastrophic data loss.
Key Takeaway: Object Lock enforces WORM policies that make data immutable for compliance and ransomware resilience, with compliance mode offering the strongest protection by preventing any modification until retention expires.