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
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
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We are really excited about our new two tone authentication system!
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4126
PUBLISHED: 2020-12-01
HCL iNotes is susceptible to a sensitive cookie exposure vulnerability. This can allow an unauthenticated remote attacker to capture the cookie by intercepting its transmission within an http session. Fixes are available in HCL Domino and iNotes versions 10.0.1 FP6 and 11.0.1 FP2 and later.
CVE-2020-4129
PUBLISHED: 2020-12-01
HCL Domino is susceptible to a lockout policy bypass vulnerability in the LDAP service. An unauthenticated attacker could use this vulnerability to mount a brute force attack against the LDAP service. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 FP6 and 11.0.1 FP1 and later.
CVE-2020-9115
PUBLISHED: 2020-12-01
ManageOne versions 6.5.1.1.B010, 6.5.1.1.B020, 6.5.1.1.B030, 6.5.1.1.B040, ,6.5.1.1.B050, 8.0.0 and 8.0.1 have a command injection vulnerability. An attacker with high privileges may exploit this vulnerability through some operations on the plug-in component. Due to insufficient input validation of ...
CVE-2020-9116
PUBLISHED: 2020-12-01
Huawei FusionCompute versions 6.5.1 and 8.0.0 have a command injection vulnerability. An authenticated, remote attacker can craft specific request to exploit this vulnerability. Due to insufficient verification, this could be exploited to cause the attackers to obtain higher privilege.
CVE-2020-14193
PUBLISHED: 2020-11-30
Affected versions of Automation for Jira - Server allowed remote attackers to read and render files as mustache templates in files inside the WEB-INF/classes & <jira-installation>/jira/bin directories via a template injection vulnerability in Jira smart values using mustache partials. The ...