Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

9/29/2016
09:10 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

A Bug Bounty Reality-Check

New study shows that bug bounties without a secure application development program and testing can be costly.

Bug bounty programs are all the rage lately, but these vulnerability reward initiatives can cost an organization more than they bargained for if they don't have sufficient software development processes in place.

A new study published today shows the dangers of relying mainly on bug bounties to scare up vulnerabilities in software: nearly 60% of IT decision-makers say they found it's more expensive for them to fix security vulnerabilities outed in bug bounty programs than it is to secure the code during the software development cycle.

The new data, gathered by Wakefield Research and commissioned by software security firm Veracode, found that 44% of the 500 respondents have spent $1 million or more on their bug bounty programs and nearly 80% say organizations with secure application development programs fork out less money on bug bounties than those that don't.

Bug bounty programs are hot among big companies and organizations such as Facebook, Google, Microsoft, the US Department of Defense, and most recently, Apple. Some 36% of the respondents in the Veracode survey say they have invested in a bug bounty program, with 98% of them reporting that they often fix their app bugs via that program.

But three-quarters of those with bug bounties say their organizations lean too heavily on those programs to find bugs; the majority say that most vulnerabilities spotted via bug bounties could have been thwarted beforehand by secure development training and testing.

The survey underscores what many appsec experts preach about bug bounty programs:  they are rarely an all-or-nothing strategy for securing applications.

Chris Wysopal, co-founder and CTO of Veracode, says it makes sense that it's cheaper to spot flaws in the development phase rather than when software is in production. "Seventy-nine percent said appsec in the software development cycle lowers bug bounty spending. I truly believe that, and it's interesting to see that [these organizations] also understand that," Wysopal says.

"You don't just want to do a bug bounty program," he says. In addition to having a development program that emphasizes secure coding, organizations also should conduct internal testing before releasing code to bug bounty hackers.

"Run a baseline test on a few apps before opening them to the bug bounty world," he says. "If you find cross-site scripting and SQL injection, those are easy issues for bug bounty researchers to find and you can find them right away" beforehand, he says. Flaws in the business logic and authorization categories, for instance, are typically found via manual testing.

Bug bounty expert Katie Moussouris, who helped launch the DoD's Hack The Pentagon program earlier last year, says launching a bug bounty program prematurely can backfire.

"Before you run a marathon on a bug bounty program, you need to do the training of vulnerability discovery," she says. "It doesn't make sense to start out with a bug bounty program."

The exception would be a small startup company with a single app that's simultaneously building a secure development program, for instance, says Moussouris, who recently founded Luta Security, a consulting firm that helps organizations work with security researchers.

She says it's not unusual for an organization to pursue a bug bounty program because they believe it's more cost-effective than penetrating testing or buying expensive vulnerability testing tools that require training as well. "If you don't have the security basics in the first place, you'll be quickly overwhelmed with low-hanging fruit [vulnerability] issues. The triage alone will easily overwhelm their resources," she says.

"If you're doing bug hunting and not trying to write secure code, you're missing the point. Everyone should be doing secure development," Moussouris says.

It's a balance between proactive testing and bug bounty programs, Veracode's Wysopal notes.  With bug bounties, "Don't go into it blind," he advises.

Related Content:

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25514
PUBLISHED: 2020-09-22
Sourcecodester Simple Library Management System 1.0 is affected by Incorrect Access Control via the Login Panel, http://<site>/lms/admin.php.
CVE-2020-25515
PUBLISHED: 2020-09-22
Sourcecodester Simple Library Management System 1.0 is affected by Insecure Permissions via Books > New Book , http://<site>/lms/index.php?page=books.
CVE-2020-14022
PUBLISHED: 2020-09-22
Ozeki NG SMS Gateway 4.17.1 through 4.17.6 does not check the file type when bulk importing new contacts ("Import Contacts" functionality) from a file. It is possible to upload an executable or .bat file that can be executed with the help of a functionality (E.g. the "Application Star...
CVE-2020-14023
PUBLISHED: 2020-09-22
Ozeki NG SMS Gateway through 4.17.6 allows SSRF via SMS WCF or RSS To SMS.
CVE-2020-14024
PUBLISHED: 2020-09-22
Ozeki NG SMS Gateway through 4.17.6 has multiple authenticated stored and/or reflected XSS vulnerabilities via the (1) Receiver or Recipient field in the Mailbox feature, (2) OZFORM_GROUPNAME field in the Group configuration of addresses, (3) listname field in the Defining address lists configuratio...