Home  ›  Glossary  ›  WORM

What is WORM (write once, read many)?

WORM, or write once read many, is a storage model where data is written a single time, read as often as needed and never changed or deleted during a retention period. It is the model behind immutability, and it only counts when the storage itself enforces it.

Where did WORM come from?

The name comes from optical discs. Data burned onto a write-once disc could be read repeatedly and could not be rewritten, and regulated industries used them for records that had to stay as originally written. The same idea now lives in software: a storage system applies a retention period at write time and rejects every change or delete request, from any user, until the period expires. Reads stay unlimited throughout.

How is WORM delivered today?

In object storage it is usually S3 Object Lock, in compliance or governance mode. Writing an object with a retention date starts the timer. Edits create new versions, deletes of the locked version are refused, and the stored data is unchanged until the date. The three terms are often confused, so it helps to separate them: immutability is the outcome, WORM is the model that produces it and Object Lock is the mechanism that implements the model in S3.

Why does enforcement location matter more than the label?

A backup application can offer a WORM setting. If the application enforces it, whoever controls the application can switch it off, and a stolen administrator login controls the application. The data underneath is still ordinary writable storage with a rule in front of it. Real WORM is enforced where the data sits: the storage platform refuses the change whoever asks, administrators included. The check is whether the lock survives the loss of the backup software. If turning off a toggle in the application unlocks the data, it was a policy, not WORM. Related pressure is described under backup tampering, where retention changes and early deletions are a standard step before encryption.

Who needs it?

  • Financial firms, where broker-dealer record rules have long required non-rewritable storage for certain records. The US SEC amended Rule 17a-4 in 2022 to allow an audit-trail alternative alongside WORM.
  • Healthcare and legal teams holding records that have to be shown unaltered in audits or proceedings.
  • Security teams protecting audit logs, since logs that an intruder can edit stop being evidence.
  • Backup administrators, where WORM on the backup target gives an immutable backup that survives a stolen login.

What are the limits of WORM?

WORM keeps stored data fixed and nothing else. It does not stop reads, so locked data can still be copied out. It keeps bad data as faithfully as good, so a system encrypted before its backup ran is preserved in encrypted form. And it is not a deletion policy: data under WORM lingers until retention ends, so capacity grows with every locked copy and retention periods deserve care in retention policy design.

Frequently asked questions

Is WORM the same as immutable?

Immutability describes the state of the data. WORM is a storage model that creates that state by accepting a single write and rejecting later changes.

Can WORM data ever be deleted?

Yes, after its retention period ends. Before that, a correctly enforced WORM system refuses deletion from every user, and in compliance mode no administrator can shorten the period.

Does WORM require special hardware?

Not any longer. Optical discs and dedicated appliances came first, but the model is now delivered in software on standard storage systems.