[
https://issues.apache.org/jira/browse/SOLR-15864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498942#comment-17498942
]
Michael Joyner commented on SOLR-15864:
---------------------------------------
Yes, s3 object locking. Currently I have our Wasabi account set to Compliance
Mode.
Objects placed in Compliance Mode remain immutable until after they have
reached the retain until date. This cannot be reversed for any reason, by any
user, regardless of user permissions.
> Add option for Immutable backups to S3 for Ransonware and Deleteware
> mitigation
> -------------------------------------------------------------------------------
>
> Key: SOLR-15864
> URL: https://issues.apache.org/jira/browse/SOLR-15864
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Michael Joyner
> Priority: Major
>
> It would be an extremely useful feature to add to the S3 backup repository
> (and possibly others, if supported) an option to be able to mark all uploaded
> objects as immutable for a defined period of time.
> If an file in the current backup already exists in the repository, simply
> extend its immutable until time.
> While I'm thinking of basic Ransomware and Deleteware mitigation, this also
> could be used for Compliance mode.
> Currently I'm backing up to a bucket with automatic locking, but this doesn't
> handle the situation where an already existing uploaded index file immutable
> until time ends earlier - leaving a timestamp gap and eventual immutable
> state no longer being active on some index files as compared to others for a
> particular backup opening up an avenue for attack.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
