Standard

Object Lock / WORM Semantics

An S3 API extension that provides write-once-read-many (WORM) protection for objects, preventing deletion or modification for a specified retention period.

10 connections3 resources

Summary

What it is

An S3 API extension that provides write-once-read-many (WORM) protection for objects, preventing deletion or modification for a specified retention period.

Where it fits

Object Lock is the compliance and data protection layer of S3. It enables tamper-proof storage for regulatory requirements (SEC 17a-4, GDPR), ransomware protection (immutable backups), and legal hold — all through the standard S3 API.

Misconceptions / Traps
  • Object Lock has two modes: Governance (allows override with special permissions) and Compliance (no one, including root, can delete until retention expires). Choosing the wrong mode can make data undeletable.
  • Not all S3-compatible implementations support Object Lock. MinIO, Dell ECS, and NetApp StorageGRID do; others may not. Verify before relying on it for compliance.
Key Connections
  • scoped_to S3 API — an extension to the S3 API
  • enables Immutable Backup Repository on Object Storage — the mechanism for tamper-proof backups
  • enables Ransomware-Resilient Object Backup Architecture — core protection mechanism
  • solves Retention Governance Friction — API-enforced retention replaces manual governance

Definition

What it is

An S3 API extension that enables write-once-read-many (WORM) protection on objects, preventing deletion or modification for a specified retention period. Supports both governance and compliance modes.

Why it exists

Regulatory requirements (SEC 17a-4, GDPR, HIPAA) mandate immutable data retention. Object Lock provides tamper-proof protection at the storage layer, making S3 suitable for compliance-driven archival and ransomware-resistant backup.

Primary use cases

Regulatory-compliant data retention, ransomware-proof backup vaults, legal hold enforcement, immutable audit logs.

Recent developments

Latest signals
  • Semantics-Aware Backdoor Attack in Federated Learning. Duplicate entry. Federated learning security paper, not storage/WORM related. Per arxiv.org (2026-04-07).

  • Semantics-Aware Backdoor Attack in Federated Learning. Accepted at IEEE/IFIP DSN 2026. Not directly related to Object Lock/WORM — federated learning backdoor attack using semantics-aware triggers. Per arxiv.org (2026-04-07).

  • IBM Cloud Object Storage adds GOVERNANCE retention mode to Object Lock (January 2026). Previously only COMPLIANCE mode and Legal Hold were supported; GOVERNANCE mode gives privileged users override ability under defined conditions while still enforcing baseline immutability. Per IBM Cloud Object Storage — release notes.

  • Governance mode is deletion-resistant, not immutable — true immutability requires storage-layer enforcement unreachable from the protected environment's identity plane. Most backup architectures deploy governance mode and market it as "immutable," but a privileged account can still lift the retention lock; only compliance mode (or an equivalent storage-layer enforcement that ordinary admin credentials cannot reach) delivers actual WORM guarantees. Per Rack2Cloud — Backup Architecture: Control Plane, Immutability & Recovery.

  • AWS CloudTrail Lake's closure to new customers (May 31, 2026) exposes its immutability gap — S3 Object Lock is the deletion-survival backstop it cannot provide on its own. CloudTrail Lake has no S3-level immutability and an all-or-nothing deletion model; the recommended compensating control is a parallel standard trail written to S3 with Object Lock in COMPLIANCE mode, which survives even privileged deletion attempts that would destroy Lake's full history in one call. Per ZTA Security Reference — AWS CloudTrail Lake.

  • EU AI Act Article 12 drives WORM adoption for high-risk AI system logs — 10-year immutable retention, no deletion or modification by anyone until expiry. Combined with Italy's Law 132/2025, execution logs for high-risk AI systems must be retained in immutable format; the referenced implementation pattern is AWS S3 Object Lock in Compliance Mode (or an equivalent sovereign service). Per Interconnectd — AI Regulation in Italy: A Survival Guide for Tech Startups. Sources: arxiv.org · arxiv.org

Connections10

Outbound4
Inbound6

Resources3