Bugs on a Plane: Implementing a Bug Bounty in an Airline IT/OT Environment
summary
An airline moves from a public VDP to a Bugcrowd-run bug bounty, running a VDP for almost two years then an eight‑month bug bounty that surfaces 13 critical reports and four earlier VDP criticals, including a patched “fly for free” payment flow exploit. Legal flags on liability and disclosure privilege force procurement and contract work, triage relies on red/blue/purple teams plus interns, and deployment uses Bugcrowd’s iframe, security.txt, and an initial private program before expanding scope from the payment flow.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 1:52Bug bounty in aviation
- 4:42Bug bounty vs disclosure
- 7:55Air Canada’s bug bounty
- 14:01Legal and cultural hurdles
- 19:19Critical vulnerabilities learned
- 24:57Internal relationships
- 28:52Private programs engagement
- 33:12Internal champions
- 37:49Expanding scope future
- 41:41Regulatory trends transparency
- 45:13Airline-researcher collaboration
- 46:15Closing advice
related talks
50mBug Bounty Programs: Successfully Controlling Complexity and Perpetual Temptation
46mHow to run a successful bug bounty programme
55mYour License for Bug Hunting Season
43mHard Knock Lessons On Bug Bounties
11mBuilding a Bug Bounty Program: From the Trenches
56mRunning a Bug Bounty Program @ SEEK
52mPractical Tips For Running A Successful Bug Bounty Program
15m"You've Got Your Nice List of Bugs, Now What?" Vulnerability Discovery and Management
