📙 What a False Alarm Taught Us About Security as a 2-Person Startup 🔥
summary
Two-person startup with $4.2M seed and first enterprise customers migrates from EC2 to ECS Fargate and a hosted Neo4j Aura graph; a failed local login (password manager had the right password but wrong username) looks like a breach, logs show a successful sync from production, and panic leads to wiped devices and deleting the DB which loses local logs. No unauthorized access turns out. Concrete takeaways: follow IR playbooks, quarantine not wipe, centralize log forwarding, test EDR, and make tooling fast and usable.
AI-written summary · about
chapters (25)
- 0:00Introduction by hosts
- 0:22Meet the founders and Subage
- 1:47Our backgrounds and journey
- 3:11First enterprise customers and funding
- 3:53Security startup challenges
- 5:15Over-engineering security tools
- 6:17Introducing our product
- 7:00The infra migration plan
- 8:46First signs of trouble
- 10:11The moment of panic
- 10:53Initial incident response
- 13:21Data protection agreements
- 15:09Containing potential impact
- 16:34Mistakes and lost evidence
- 17:14Spiraling fears and questions
- 18:40Contacting Neo4j support
- 19:21The false alarm revealed
- 21:08Root cause and relief
- 23:16Key learnings from the incident
- 25:24Customer empathy gained
- 26:49Security tools and customer value
- 27:51Post-incident improvements
- 28:54Why we shared this story
- 29:17Closing remarks and thanks
- 29:39Q&A session
related talks
07mSuccess Breeds Panic: shares the story of his first security incident
22mDevSecOps - The Story of 3 Security Breaches
26mCloud Security Lessons
31mLog In Through the Front Door: Automating Defense Against...
39mPerils of the cloud
47mBreaking the Cloud to Rebuild It: A Tale of 3 ☁️ Breaches!
39mLocknote: Conclusions and Key Takeaways from Day 2
46mApplication security from start to finish