Ransomware groups learned years ago to delete backups before they encrypt anything. If your backup server can delete its offsite copy, so can anyone who takes over the backup server.

Object Lock fixes this at the storage layer. Each object gets a retention date, and until that date nobody can delete or overwrite it, including the bucket owner. Stonebridge 3.4 sets that date on every chunk it uploads.

Create a bucket with Object Lock

Object Lock has to be turned on when the bucket is created. You can’t add it later.

AWS S3

aws s3api create-bucket --bucket acme-backups \
  --object-lock-enabled-for-bucket

MinIO

mc mb --with-lock local/acme-backups

Backblaze B2

b2 bucket create --file-lock-enabled acme-backups allPrivate

Point Stonebridge at it

sb target add offsite \
  --s3 https://s3.eu-central-1.amazonaws.com/acme-backups \
  --object-lock compliance --retention 30d

Use compliance mode. In governance mode, a user with the right permission can still remove the lock, which is exactly the permission an attacker goes looking for.

Test it

Try to delete a chunk with the same credentials Stonebridge uses. It should fail with AccessDenied. If it succeeds, the bucket was created without Object Lock, and you need a new one.