How to secure your data and applications against ransomware
summary
Panel claims ransomware hits every 11 seconds and argues defense requires concrete steps: keep backups in separate accounts with different credentials, require multi-person MFA for destructive ops, keep air-gapped copy or immutable time-series recovery points, and automate sandboxed restores and forensic workflows. Examples: tape restores once took weeks to months; MIT moves to Rubrik to cut restore time and manage multi‑cloud data. Goal is assume breach, make workloads ephemeral where possible, and orchestrate fast, verifiable recovery.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:35Favorite thing to do in Vegas
- 2:19Introductions
- 3:18Ransomware
- 4:50How does ransomware threaten business continuity
- 8:33How do cloud platforms play a role in the challenges
- 11:08Whats your opinion on ensuring security across all these hybrid cloud environments
- 14:22Are there any best practices or operational workflows
- 18:48Is there a standard model or guidance you give customers
- 21:56How do you avoid paying the ransom
- 25:01How should infrastructure operations and security teams work together
- 27:33Additional thoughts
- 30:46Data security and perimeter defense
- 33:22Endpoints
- 35:43Ransomware recovery
- 39:16Cultural lift
- 40:29MITs cloud journey
- 43:25Closing thoughts
- 46:15Closing remarks
related talks
38mRansomware and Backups: A Multi-Layered Defense Strategy
06mA Battle Plan for Disaster Recovery in the Wake of Ransomare
14mIs a Ransomware Attack in your Future? How to Prevent an Attack
50mRansomware Readiness: Backup and Recovery in the Cloud
20mWhen ransomware strikes
27mRansomware: A database survival guide
35mDefeating Ransomware Attacks
21mRansomware Attack: Lessons Learned