Nine Cloud Security Reasons for Resting Breach Face
summary
Nine concrete cloud breaches and what actually failed: Log4j → ONUS, attackers find AWS keys, delete S3 data and expose ~2 million users after a $5M ransom demand; a misconfigured instance lets NetWalker pivot from cloud to on‑prem and touch ~1,800 systems; Pfizer leaves GCS buckets publicly readable with hundreds of PII transcripts; malicious AMIs and leaked root keys enable large crypto‑mining campaigns; PURPLEURCHIN automates free‑trial abuse across 30 GitHub, 2,000 Heroku, 900 Buddy accounts; PyTorch supply‑chain package is downloaded ~2,000 times. Actions, numbers, and failures are explicit; fixes focus on least privilege, real‑time visibility, secrets management and runtime verification.
AI-written summary · about
chapters (12)
- 0:00Introduction to cloud security
- 1:07The evolving cloud threat
- 2:58Ransomware and log4j impacts
- 7:21Pivot attacks and visibility
- 12:30Misconfigured storage buckets
- 15:13Supply chain crypto mining
- 20:26Compromised credentials
- 23:18API access vulnerabilities
- 25:52Free-tier account abuse
- 33:26Advanced lateral movement
- 39:13Software dependency risks
- 42:52Cloud security best practices
related talks
32mDo This, Not That – Lessons from 7 Headline Grabbing Security Breaches
45mProtecting you from you: Misconfiguration-caused breaches
47mBreaking the Cloud to Rebuild It: A Tale of 3 ☁️ Breaches!
36mIAM Confused: Decoding 8 Real World Cloud Identity Breaches
26mCloud Security Lessons
22mDevSecOps - The Story of 3 Security Breaches
39mPerils of the cloud
36mCloud Hacking Scenarios