Securing Deliveroo
summary
Deliveroo describes practical security work: create an internal security team, enforce single sign-on with two‑factor everywhere, and tighten physical access (locked doors, guest Wi‑Fi, printer disposal). Run a bug bounty via HackerOne with ~10 hour response targets and payouts up to ~$15k; first triage reduces noise but reveals real angular injections, cookie domain misses, and DNS takeover risks. Deploy Cloudflare for DDoS (migration takes weeks), store passwords with bcrypt, handle GDPR with an Inquisitor event-driven deletion/portability pipeline and defined data lifecycles.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:28Why now
- 3:32Lack of security
- 6:29Data protection regulation
- 11:18Lockdown
- 14:04HackerOne
- 17:05Insco
- 18:15Angular Injection
- 19:33Theists Attack
- 20:25Application Tier Traffic
- 21:03Defensive Design
- 22:16CloudFlare
- 24:30Personal Data
- 27:24Data Life Cycles








