BRENNEN

Industries / Finance and business services / Records management

Storage

Storage is keeping records safe, on shelves, in boxes, in off-site records centers and in computer systems, until they are needed or due for destruction.

6

Milestones achieved, from 1951 to 2024.

1

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1951

    Records in a mine

    In 1936 Herman Knaust bought a disused iron mine near Livingston, New York, to grow mushrooms. In 1951 he renovated it, put in new ventilation and a 28-ton vault door bought secondhand from a failed bank, and opened Iron Mountain Atomic Storage. He sold it to companies afraid that a nuclear attack would wipe out their records of deposits, insurance policies and inventory, by the account of J. B. Crawford in his newsletter on technology history. Iron Mountain Inc., the company that grew from it, dates its founding to 1951.

    computer.ripironmountain.com

    Credit

    Herman Knaust

  2. 1973

    No second copy

    On 12 July 1973 a fire at the National Personnel Records Center in St. Louis, Missouri, destroyed about 16 to 18 million Official Military Personnel Files, by NARA's estimate. That was 80% of the files of Army personnel discharged from 1 November 1912 to 1 January 1960, and 75% of the files of Air Force personnel discharged from 25 September 1947 to 1 January 1964 whose names come after "Hubbard, James E.". The fire burned out of control for 22 hours. About 6.5 million burned and water-damaged records were recovered, many of them dried in vacuum chambers at McDonnell Douglas that had been used to test conditions for the Mercury and Gemini space missions.

    LessonNo duplicate or microfilm copies of the files existed and no index had been made, so, in NARA's words, "a complete listing of the records that were lost is not available".

    archives.gov

    Credit

    NARA's National Personnel Records Center, which ran the recovery

  3. 2003

    A model for digital archives

    The International Organization for Standardization (ISO) published ISO 14721 in March 2003. It is the reference model for an Open Archival Information System (OAIS): a description of what an archive must do to keep digital information usable over the long term, covering "ingest, archival storage, data management, access, and dissemination". It sets "a minimal set of responsibilities" for an archive. A 2012 edition replaced it.

    iso.org

    Credit

    ISO

  4. 2014

    Fire at a records warehouse

    On 5 February 2014 fire destroyed an Iron Mountain warehouse in the Barracas district of Buenos Aires that stored bank and company archives. A wall collapsed onto the crews outside, and eight firefighters and two civil defense rescuers were killed, by Infobae's count. About 5,000 boxes of documents burned. Iron Mountain said the building had fire detection and a sprinkler system. In 2015 experts for Argentina's Federal Police found the fire had probably been set on purpose, and in 2023 the Buenos Aires Herald reported that 18 people accused of arson had been sent to trial.

    LessonA records warehouse can be a target in itself: by 2014, the Herald reported, Iron Mountain warehouses had caught fire seven times worldwide, and five of the fires were found to be intentional.

    infobae.comksl.combuenosairesherald.com

    Credit

    Federal Police of Argentina, fire investigation

  5. 2018

    Cloud storage that cannot delete

    Amazon Web Services (AWS) launched S3 Object Lock on 26 November 2018. It blocks deletion of stored files until a set date, or while a legal hold is on them. In compliance mode nobody can remove the lock, not even the account's root user. AWS presented it as a way to move records from WORM (write once, read many) systems into cloud storage. Cohasset Associates, a records management consultancy, assessed it against SEC Rule 17a-4(f), FINRA Rule 4511 and CFTC Regulation 1.31, the US recordkeeping rules for securities and commodities firms.

    aws.amazon.com

    Credit

    Amazon Web Services; assessed by Cohasset Associates

  6. 2024

    Paper transfers end

    A memo of 23 December 2022 from the White House Office of Management and Budget and NARA, numbered M-23-07, set 30 June 2024 as the deadline for federal agencies to manage their permanent records electronically. After that date NARA would "no longer accept new transfers of permanent or temporary analog records" without a limited exception, and agencies had to close the records storage facilities they ran themselves.

    archives.govrecords-express.blogs.archives.gov

    Credit

    Shalanda D. Young, Office of Management and Budget; Debra Steidel Wall, acting Archivist of the United States

Watch for

  1. Data in glass

    Microsoft Research says its Project Silica can now use lasers to write data into ordinary borosilicate glass, the kind used in oven doors, and that accelerated aging tests suggest "the data should remain intact for at least 10,000 years". The work was published in Nature. Microsoft says the research phase is complete, and it has announced no product.

    Achieved whenan outside laboratory repeats the aging tests, or a product ships and an archive reports using it.

    microsoft.com

    Claimed by

    Microsoft Research, February 2026

Open

  1. 01

    A test for locked storage

    An open-source test suite that tries to break the retention locks on object storage: Amazon S3 Object Lock, Azure immutable blob storage, Google Cloud Storage bucket lock, and the open-source MinIO and Ceph. For each one it tries every route a user, an administrator or a script has to delete or change a locked test record, such as deleting or overwriting the file, shortening the lock, lifting a legal hold, changing lifecycle rules, deleting the bucket and closing the account, and it records which attempts succeed.

    The brief
    Credit · unclaimed
  2. 02

    Records that survive a move

    A test of whether records keep their retention dates, legal holds, version history and audit trails when an organization moves them from one cloud service to another. Load test accounts in Microsoft 365, Google Workspace, Box and Dropbox with 1,000 synthetic records that carry retention labels, holds and several versions. Export them with each service's own tools, import them into the others, and count what survives.

    The brief
    Credit · unclaimed

Open 01 · the brief

A test for locked storage

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

An open-source test suite that tries to break the retention locks on object storage: Amazon S3 Object Lock, Azure immutable blob storage, Google Cloud Storage bucket lock, and the open-source MinIO and Ceph. For each one it tries every route a user, an administrator or a script has to delete or change a locked test record, such as deleting or overwriting the file, shortening the lock, lifting a legal hold, changing lifecycle rules, deleting the bucket and closing the account, and it records which attempts succeed.

Why it is still open

Locked storage reaches regulators through assessment reports. AWS tells customers to download Cohasset Associates' report and give it to their regulator when they start keeping regulated records on S3. Searches found no published test, across vendors, of attempts to defeat a lock.

aws.amazon.com

Built with what exists

low-cost accounts on each cloud; MinIO and Ceph run locally in Docker; each provider's own software development kit; pytest to run and report the attempts; Browser Use 1.0, an open-source agent that writes Python to drive Chrome, for routes that exist only in web consoles (see the Note "Deleting 80% to start over").

  1. First step

    List the deletion routes in AWS's Object Lock documentation and run them against a MinIO bucket on a laptop.

  2. Done looks like

    At least 40 deletion and change routes tried against at least 5 storage systems in compliance mode or its equivalent, all on test data, with a published table of every attempt and its result, rerun automatically each month.

Open 02 · the brief

Records that survive a move

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A test of whether records keep their retention dates, legal holds, version history and audit trails when an organization moves them from one cloud service to another. Load test accounts in Microsoft 365, Google Workspace, Box and Dropbox with 1,000 synthetic records that carry retention labels, holds and several versions. Export them with each service's own tools, import them into the others, and count what survives.

Why it is still open

The EU Data Act has applied since 12 September 2025, and its chapter on switching requires cloud providers to "facilitate interoperability and enable switching". The European Commission says the data that matters for switching includes "metadata, generated by the customer's use of the service". Searches found no published test of whether records metadata such as retention dates and holds survives a switch.

digital-strategy.ec.europa.eu

Built with what exists

test accounts in each service; their export tools, such as Microsoft Purview eDiscovery and Google Vault; a Python script that compares every field before and after; synthetic records written by a language model.

  1. First step

    Load 100 labelled test documents into one Microsoft 365 test account and export them with eDiscovery.

  2. Done looks like

    A published table for at least 4 services and 12 directions of travel, giving the share of records that keep each of 8 properties: retention date, retention label, hold, versions, author, created date, modified date and audit trail.