Object Immutability from MinIO

Protecting data from deletion (accidental or intentional) is a key compliance component that touches every industry. MinIO supports a complete range of functionality including object locking, retention, legal holds, governance, and compliance. Object locking can be used in conjunction with MinIO versioning to ensure data immutability and eliminate the risk of data tampering or destruction.

Object Retention

Object storage retention rules ensure that an object is WORM protected for some period of time. Object storage retention policy specifies retention periods set on an object version either explicitly or through a bucket default setting. A default lock configuration set at the bucket level applies to objects that are created subsequently, and does not apply retroactively to versions of objects created previously.

When the bucket default setting is used, a duration is set in either days or years that defines the length of time for which every object version placed in the bucket should be protected. A new object placed in the bucket inherits the protection duration as set for the bucket.

Retention periods may be set explicitly for an object version. Explicit retention periods specify a Retain Until Date for the object version. The Retain Until Date setting is stored in the object version's metadata and protects the object version until the retention period expires.

After the retention period expires, the object version can be deleted unless a legal hold was also placed on the object version.

Explicit retention mode settings override default bucket settings.

Retention periods can be extended easily by submitting a new lock request.

There are two types of modes used to set a retention period for objects and buckets in the Retention framework:

Governance Mode

Governance mode is used to protect objects from being deleted by standard users. Some users, however, will need to retain the permissions required to modify the retention settings or delete the objects. Those users will require special permissions such as the s3:BypassGovernanceRetention permission and DeleteObject permission.

Compliance Mode

Compliance mode is more restrictive and cannot be undone within the retention period. As a result, Compliance mode ensures that no one, including the root user, can delete an object during its retention period.

MinIO Data Immutability Meets or Exceeds Cohasset Certification Standards

The gold standard in object locking, retention, and legal holds is validation from Cohasset Associates. MinIO's object storage retention and data immutability have earned a positive assessment from Cohasset Associates, specifically regarding SEC Rule 17a-4(f), FINRA Rule 4511, and CFTC Regulation 1.31. Rule 17a-4 has specific requirements for electronic data storage, including many aspects of record management, such as the duration, format, quality, availability, and accountability of broker-dealer record retention.

A copy of the Cohasset Associates Assessment report can be downloaded in its entirety and shared with the appropriate regulator when storing data on MinIO. It details exactly how to configure MinIO to meet the requirements as well as the logic underpinning the object locking features.

Learn more about Object Immutability on MinIO

MinIO earns Immutability badge from the Veeam Ready Program
Blog
MinIO earns Immutability badge from the Veeam Ready Program
Read Story
Object Locking, Versioning, Holds and Modes in MinIO
Blog
Object Locking, Versioning, Holds and Modes in MinIO
Read Story
Cohasset Associates Report
White Paper
Cohasset Associates Report
Read

You are using Internet Explorer version 11 or lower. Due to security issues and lack of support for web standards, it is highly recommended that you upgrade to a modern browser.