Perils of the cloud
summary
Practical, AWS‑focused checklist: concrete breach stories where leaked credentials on GitHub let attackers terminate instances or run crypto mining in distant regions, and recovery costs get huge; exact mitigations including IAM least‑privilege, enforced MFA with a hardware token in a safe, and billing alerts plus CloudTrail->S3 logging. Demos of lightweight automation (Lambda that tags creators, pushing logs into Elasticsearch/Kibana) and notes on vaults versus encrypted deploy files show what was built, what failed, and which fixes actually worked.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:54Who is using cloud already
- 3:34What can go wrong
- 7:44Secure your account
- 9:48Control access
- 13:00Authentication
- 16:48Tokens
- 17:49Network
- 19:21Billing Alerts
- 22:19Security Status
- 25:32Attacks
- 29:05Credentials
- 34:26Conclusion
related talks
47mBreaking the Cloud to Rebuild It: A Tale of 3 ☁️ Breaches!
38mAdventures in Cloud Security: What DevOps Can Learn from a Security Engineer
29mPragmatic Security Automation and DevSecOps in the Cloud
45mProtecting you from you: Misconfiguration-caused breaches
40mAvoiding Pain When Operating in the Cloud
36mIAM Confused: Decoding 8 Real World Cloud Identity Breaches
32mDo This, Not That – Lessons from 7 Headline Grabbing Security Breaches
48mNine Cloud Security Reasons for Resting Breach Face