How to prepare for the next evolution of cyberattacks
summary
Druva runs about 4 billion backups a year across 300 PB of de‑duplicated data in 16 AWS regions and separates metadata (DynamoDB) from data (S3) while enforcing customer‑held keys and private subnets with no SSH, MFA and IMDSv2. Recommended controls: keep backups in a separate account, centralize and retain logs offsite, maintain a cloud sandbox to restore and scan prior to production, and test Active Directory recovery and workload‑specific playbooks regularly so recovery succeeds without paying ransom.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:22Statistics
- 2:56Who am I
- 3:54Scope and scale
- 4:49What do we do
- 5:39Security vs Backup
- 7:10Data encryption
- 12:27Creating a resilient platform
- 17:05Incident response plan
- 20:12Monitoring your production environment
- 23:48Recovery
- 28:11Ransomware
- 35:09Recovering the environment
- 35:40Standardisation
- 40:51Working remotely
- 44:36Druva
- 48:32Endpoints
- 49:08Key takeaways
- 51:14Sales pitch
- 53:39Druva booth
- 54:24Conclusion
related talks
58mDefend your data at scale: 3 steps to increase cyber security
57mCloud security, data responsibility, and recovery: 10 key strategies
50mProtegiendo sus datos en la nube de AWS ante un evento de ransomware
41mMore Than Backups and Hope
29mDesign secure protection environments with Veeam and AWS
20mSimplifying cost-optimized cyber response & recovery at massive scale
35mDefeating Ransomware Attacks
22mNavigating a cybersecurity event in real time