The bug bounty market is growing quickly. While an increasing number of organizations are embracing the concept, there still remains some confusion and ambiguity around paying hackers for vulnerabilities. Events like recently disclosed Uber breach illustrate this confusion. I’ll take this opportunity to clarify and define this rapidly evolving market.
Posts by David Baker
Last week, we released our second annual Inside the Mind of a Hacker 2.0 report. We dove into different hacker profiles, their motivations for hacking, and the impact building a relationship makes on a successful bug bounty program. We found lots of interesting stats on our bug hunting community, both expected and surprising.
It’s common knowledge that the security industry has been facing a massive shortage of resources. Add the fact that companies are accelerating their cloud presence and growing an API ecosystem of their own. CISOs are up-leveling their security strategy by adding bug bounty programs to their toolbox.
Google recently announced that the company has raised its top reward for remote code execution bugs in its Google, Blogger and YouTube domains by 50 percent, saying “Because high-severity vulnerabilities have become harder to identify over the years, researchers have needed more time to find them. We want to demonstrate our appreciation for the significant time researchers dedicate to our program.”
Today, as I embark on a new journey with Bugcrowd, I reflect on the most common question I have heard: “why leave Okta?” It’s a good question. I am honored to have served as the Chief Security Officer at Okta, building a world-class security program for a truly innovative company. Moreover, the ride at Okta was meteoric and I know they will continue on their path to world domination. But now, it’s time for disruption. To be more specific, the opportunity to completely change the information security industry. That is where Bugcrowd is going – and that train is leaving the station with me on it.