Technical Recovery Plan (TRP) Exercise in a Cloud-Native Environment: Practical Lessons ...
summary
Practical case study of a ransomware Technical Recovery Plan exercise triggered by a 2023 Toyota Financial Services incident, focused on Amazon Aurora MySQL and concrete recovery choices: Backtrack is limited to six hours so the team uses PITR (up to 35 days) to spawn a new cluster, preserving the original for forensics. 70 participants in four teams simulate an EC2 gateway compromise; TRP steps are isolate, snapshot, replace. Database restores succeed to the pre‑encryption point but product teams manually recover intervening changes, yielding clear SLA and privileged‑account gaps.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:22Why TRP exercise needed
- 5:16Preparing and running TRP
- 15:12TRP exercise overview
- 15:57Results and lessons
- 20:37Final recommendations
- 20:57Q&A
related talks
06mA Battle Plan for Disaster Recovery in the Wake of Ransomare
17mRansomware & disaster recovery with AWS Elastic Disaster Recovery
49mTips and Tricks: Protecting Cloud Infrastructure
54mExperience a simulated ransomware event: Learn now to prevail later
47mTough Cases: Ransomware Recovery in High-Availability Environments
47mDisaster Recovery Strategies for SQL Server
11mProtect and Recover with Autonomous Recovery
41mMore Than Backups and Hope