Securing S3 Backups Against Ransomware
summary
Cloud-native backups become ransomware-resistant by using S3 Object Locking plus bucket versioning and explicit retention (or legal holds) so backups cannot be overwritten or deleted; use the S3 APIs (PutObject with retention headers, PutObjectLegalHold, PutObjectRetention, and deleting by specific version IDs) and track every blob’s version ID. Real threats include Hildegard (Jan 2021) and buyable network access for $300–$10,000, so follow 3-2-1 plus immutability and always track version IDs for safe restores.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:50What is the need for mutual backups
- 4:30Targeted Kubernetes use cases
- 8:30Accidental deletion
- 9:45Prevent preventative tasks
- 12:00Immutable backups
related talks
50mProtegiendo sus datos en la nube de AWS ante un evento de ransomware
29mDesign secure protection environments with Veeam and AWS
38mRansomware and Backups: A Multi-Layered Defense Strategy
50mRansomware Readiness: Backup and Recovery in the Cloud
41mLet Your Cloud Native Storage Save You from Ransomware!
51mHow to secure your data and applications against ransomware
38mProtecting Database Backups From Ransomware and Malicious Intent
14mIs a Ransomware Attack in your Future? How to Prevent an Attack