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 Executive Editor at DarkReading.com. 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This is a secure windows pc.
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.