Break the Cloud
The disaster simulator.
Your mission
You run a cloud service that thousands of students depend on. Choose its defences, then unleash disasters on it: crashed servers, failed drives, a deleted folder, ransomware, a stolen disk and more. Find out which protection saves you from which disaster, and why keeping a service running is not the same as keeping data safe.
Explore
This is the control room of a cloud service that thousands of students use. Tap the three gauges, the defences, and then unleash your first disaster.
Three gauges tell you how the service is doing: is it running, is the data all there, and is it private? Different disasters hit different gauges, and need different protections. Tap the gauges first.
0 of 6 discoveries made
Experiment
Switch defences on and off, unleash every disaster, and find out which protection stops which one.
Disaster drills
Try each one. They tick themselves off.
0 of 5 experiments done
Challenge
Six rounds: match every disaster with its protection, and every security need with its control.
Incident commander's notes
- Hardware failure → redundancy and failover (RAID, more servers)
- Deleted files → recoverable backups or snapshots
- Ransomware → isolate, security controls, clean backups
- In transit · at rest · authentication · permissions · updates
- Availability ≠ security ≠ recoverability
Finish all 6 rounds to finish this stage.
Understand
Here is what the control room was showing you, in the words you need for the exam.
Different incidents, different protections
| Incident (problem) | Possible protection (recovery) |
|---|---|
| Server hardware failure: a server or drive stops working (disk failure, server crash) | Redundancy and failover: use replicated data (e.g. RAID, multiple servers) and automatically switch to a healthy system to keep services available. |
| Accidental file deletion: important files deleted by mistake | Recoverable backup or suitable snapshots: restore the file from a recent backup (e.g. a daily backup), or use snapshots or version history to recover a previous version. |
| Ransomware attack: files encrypted by malicious software, with a demand for payment | Isolation, security controls and clean backups: isolate the affected device or network to stop the spread, use security controls (e.g. firewalls, anti-malware, updates), and restore the data from a clean, independent backup (e.g. offline or off-site copy). |
Key takeaway: availability, security and recoverability are different. A system can keep running during a drive failure (availability) but still lose data through deletion or a cyberattack.
Five layers of protection for cloud and NAS data
- Encryption in transit: protects your data while it is being transmitted (e.g. HTTPS, VPN).
- Encryption at rest: keeps your data encrypted when it is stored (e.g. on a NAS or in the cloud).
- Authentication: verifies your identity before granting access (e.g. strong passwords, two-factor authentication (2FA)).
- Access permissions: control who can view, edit or share specific files and folders.
- Software updates: keep the NAS, operating system and apps up to date to fix security vulnerabilities.
Security requires multiple layers of protection: no single control covers every need.
Authentication vs permissions
Authentication checks who you are (a password, a 2FA code). Access permissions decide what you may do once you are in (view, edit, share). The nosy intern was properly signed in, which is exactly why permissions were needed.
In transit vs at rest
Encryption in transit stopped the eavesdropper on the café Wi-Fi, but it does not protect files once they are stored. Encryption at rest made the stolen disk unreadable. You need both.
Words to know
- Availability
- The service keeps running and stays accessible.
- Recoverability
- Lost or damaged data can be brought back.
- Redundancy and failover
- Extra resources, and switching to them automatically.
- Snapshot
- A saved earlier version of the data to roll back to.
- Ransomware
- Malware that encrypts files and demands payment.
- Two-factor authentication (2FA)
- A second proof of identity besides the password.
- Vulnerability
- A weakness in software that attackers can use; updates fix them.
Exam tip
Match the protection to the problem, and name it precisely. Data travelling across the Internet: encryption in transit. Files stored on drives: encryption at rest. Verifying who someone is: authentication. Limiting what a user can change: access permissions. Known software weaknesses: software updates. For a hardware failure say redundancy and failover; for a deleted or encrypted file say backup (a clean, independent copy) or snapshots. Explain why no single control covers everything.