← All categories
Friday, 20 November 2026Today · official
AWS ArchitectDifficulty ★★★★☆2026-11-20

Ransomware hits production — can you trust your backups?

Your organization runs critical workloads on AWS across multiple accounts. A security team confirms a ransomware event in the production environment. The incident response process has begun, but the team quickly realizes that the production account's IAM identities, KMS keys, and possibly the backups themselves may have been compromised during the attacker's dwell period. Restoring directly into production carries the risk of reintroducing the threat. Restoring from the most recent backup may pull in encrypted or tampered data. The backup storage itself could have been targeted for deletion. Engineers are debating whether to restore in-place, how to verify that a backup is safe, and how to structure accounts and trust boundaries so that a compromised production identity cannot affect the recovery process. The CFO wants a confirmed recovery timeline by end of week, and the board needs assurance that the same attack surface cannot be exploited again during recovery. What architectural approach would you bring to the war room to structure the recovery environment and protect the integrity of the entire recovery process?

Skills:Disaster recoveryMulti-tenancySecurityGovernanceResilience
Attempt 1of 5

Submit sends whatever you have — empty, typed-without-select, or a picked suggestion. Each submission counts as one attempt and unlocks a hint if wrong.