security breach - lessons learned
summary
BrowserStack got breached and the team publishes a white paper detailing what went wrong and what fixed it. The useful specifics are multi‑location monitoring, alerts for table locks, removing wildcard grants in databases and ACLs, scoped API keys plus 2FA, separate staging credentials, off‑site encrypted backups with a different provider, regular CVE scans (poodle shellshock venom) via OpenVAS, centralized logging that records who booted what (CloudTrail), IDS/malware scanners, and a tightly integrated incident response team and regular red‑teaming.
AI-written summary · about
chapters (7)
related talks
22mDevSecOps - The Story of 3 Security Breaches
46mApplication security from start to finish
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
26mCloud Security Lessons
32mDo This, Not That – Lessons from 7 Headline Grabbing Security Breaches
14mSecurity lifecycle management in a multicloud world
46mStories from the cutting edge: Cloud security in 2023
48mNine Cloud Security Reasons for Resting Breach Face