Hi :-)
Both Wasabi and BackBlaze (and properly many more) have support for anti-ransomware by locking backups up until a unlock date in the future. The unlock date is predefined when doing the backup and this is safeguarding from ransomware events.
Incremental backup can never support lockups (or whatever you want to call it) but complete backups can but JetBackup 5 is not yet supporting it.
So, a hacker can actually set the "keep number of copies" to 0 and do a new backup of their hacked (encrypted) files and the company owner can do nothing about it as there are no older backups to restore from as the hacker via JetBackup has deleted them this way.
I have been talking with the developers about this issue some months ago but I again got an enquiry from a client and I am now making it a feature request here.
We are solving it for now by having a NAS that is offline except when we do a manuel backup. This is an extra backup besides the online backups we do to Wasabi and BackBlaze each night.
Thank you :-)
I like this idea
Hello,
Thank you for opening your feature request and sharing your idea with us! We will review your request and provide updates accordingly. Please note that we utilize the voting system to gauge demand for new features. The more votes a request has, the more likely it will be up for consideration by our developers.
Thank you,
Richard, JetApps Team.
Hello,
Thank you for opening your feature request and sharing your idea with us! We will review your request and provide updates accordingly. Please note that we utilize the voting system to gauge demand for new features. The more votes a request has, the more likely it will be up for consideration by our developers.
Thank you,
Richard, JetApps Team.
We need this too :-)
We need this too :-)
Hello Jens,
Thank you for opening a new feature request. May you please verify if the following Feature Request - Immutable (WORN) backups on AWS S3 with Object Lock - covers the same feature you are currently requesting. In order to avoid confusion and to ensure the maximum number of votes for this feature, we would like to merge the two Feature Requests if they are similar.
With that said, our developers will review your request and provide updates accordingly.
Thank you,
JetApps Team
Hello Jens,
Thank you for opening a new feature request. May you please verify if the following Feature Request - Immutable (WORN) backups on AWS S3 with Object Lock - covers the same feature you are currently requesting. In order to avoid confusion and to ensure the maximum number of votes for this feature, we would like to merge the two Feature Requests if they are similar.
With that said, our developers will review your request and provide updates accordingly.
Thank you,
JetApps Team
Adding to this:
Both Wasabi and BackBlaze (and properly many more) have support for anti-ransomware by locking backups up until a unlock date in the future. The unlock date is predefined when doing the backup and this is safeguarding from ransomware events.
Incremental backup can never support lockups (or whatever you want to call it) but complete backups can but JetBackup 5 is not yet supporting it.
So, a hacker can actually set the "keep number of copies" to 0 and do a new backup of their hacked (encrypted) files and the company owner can do nothing about it as there are no older backups to restore from as the hacker via JetBackup has deleted them this way.
I have been talking with the developers about this issue some months ago but I again got an enquiry from a client and I am now making it a feature request here.
We are solving it for now by having a NAS that is offline except when we do a manuel backup. This is an extra backup besides the online backups we do to Wasabi and BackBlaze each night.
Adding to this:
Both Wasabi and BackBlaze (and properly many more) have support for anti-ransomware by locking backups up until a unlock date in the future. The unlock date is predefined when doing the backup and this is safeguarding from ransomware events.
Incremental backup can never support lockups (or whatever you want to call it) but complete backups can but JetBackup 5 is not yet supporting it.
So, a hacker can actually set the "keep number of copies" to 0 and do a new backup of their hacked (encrypted) files and the company owner can do nothing about it as there are no older backups to restore from as the hacker via JetBackup has deleted them this way.
I have been talking with the developers about this issue some months ago but I again got an enquiry from a client and I am now making it a feature request here.
We are solving it for now by having a NAS that is offline except when we do a manuel backup. This is an extra backup besides the online backups we do to Wasabi and BackBlaze each night.
...
...
Hello everyone,
Thank you for reaching out and creating this feature request. We are pleased to let you know the immutable retained backups are now planned for JetBackup 5. We will keep this request updated when the feature is completed and available.
Thank you,
The JetApps Team
Hello everyone,
Thank you for reaching out and creating this feature request. We are pleased to let you know the immutable retained backups are now planned for JetBackup 5. We will keep this request updated when the feature is completed and available.
Thank you,
The JetApps Team
Replies have been locked on this page!