Storage immutability
Storage immutability prevents specified data from being overwritten or deleted under an enforced retention rule or hold.
Scope and bypass rights depend on the implementation. S3 Object Lock protects a specific object version, not the object name as a whole; new versions and delete markers remain possible. Governance bypass requires permission and an explicit bypass request. Compliance blocks user deletion during retention, including by the account root user, but is not protection against account deletion. Removing a legal hold does not end a concurrent retention period. [3]
Relations
- related
- WORM storage, Object storage, Air-gapped backup, Backup verification, Restore test, Backup manifest, Object versioning, Object lock, Legal hold (storage)
Advantages
- Can enforce retention of a protected object version. [3]
Limitations
- A policy name alone does not describe bypass permissions or hold-removal rights. [3]
- Retaining data does not establish recoverability; test restoration separately. [2]
- A retained version can contain pre-existing compromise; selecting a trusted recovery point is a separate task. [5]
- S3 Object Lock does not prevent encryption-key deletion or loss of key access; retained ciphertext may be unreadable. [6]
Citations
- NIST SP 800-53 Rev. 5: CP-9(1), CP-9(2) and CP-10
- Amazon S3 User Guide: Locking objects with Object Lock
- Strunk et al.: Self-Securing Storage: Protecting Data in Compromised Systems, OSDI 2000, sections 2.2, 3.3 and 5
- Amazon S3: Object Lock considerations