Running a Bug Bounty Program @ SEEK
summary
SEEK runs a two‑week, production bug bounty POC via Bugcrowd with 50 researchers invited and a $15k USD pool, yielding 104 reports, 3 high severity findings and about 15 active submitters; typical rewards cluster around $200 while top payouts reach ~$2k. Testers uncover real issues: XML external entity exfiltration, password‑reset enumeration, and a chained Twitter SSO → support → Slack disclosure. Production testing holds up with no major outages and leads to an ongoing program.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:40Bug Bounty Programs
- 7:52The Dark Web
- 15:28Can We Make Our Web Apps 100 % Secure
- 16:28Car Safety Analogy
- 16:51The Red Cross Breach
- 18:12Conjoined Triangles of Success
- 23:11Benefits of a Private Program
- 26:11Can I Run a Bug Bounty Program
- 26:48What Is the Maturity of Your Website
- 31:07Risk Mitigations
- 46:17Xml Entity Attack
related talks
52mPractical Tips For Running A Successful Bug Bounty Program
43mHard Knock Lessons On Bug Bounties
35mSetting up a bug bounty program for your app
55mYour License for Bug Hunting Season
50mBug Bounty Programs: Successfully Controlling Complexity and Perpetual Temptation
11mBuilding a Bug Bounty Program: From the Trenches
40mDon't Let Bug Bounty Kill Your Appsec Posture
37mFrom DevSecOops to Security Success: The Bug Bounty Effect at FINN.no
