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.

Risk

5/12/2011
10:28 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Enterprises Skimp On Testing Third-Party Code

Seventy percent run security, vulnerability assessments on internal code, but only 35 percent do the same for third-party code they bring in-house, Forrester/Coverity report finds

Most organizations use third-party code, but few actually vet it with the rigor they do for their internally written code.

A new survey by Forrester Research, commissioned by Coverity Software, found that while organizations are increasingly testing their internally developed applications, they aren't doing the same for the third-party applications or code they use.

Nearly 70 percent say they perform automated testing on their in-house developed code, but only 44 percent test the third-party code they use in-house. And while 70 percent run risk, security, or vulnerability assessments of their internal code, just 35 percent do the same for third-party code, the survey found. Some 68 percent perform manual code review of their internally written apps, while only 35 percent do the same for third-party software.

"The biggest surprise here was the data on third-party testing. We had seen a rise in third-party software, but we didn't expect to see the gap between the level of their testing for in-house code versus third-party code," says Jennifer Johnson, director of product marketing for Coverity. "Even if you have the most mature and rigorous [secure development] for your in-house software, that's only half the battle."

Coverity's Johnson says the report validates the shift in how code is developed. More than 90 percent of respondents -- more than half of which offer commercial software or services -- say they use some form of third-party software in their supply chain. "There are hundreds of suppliers in the software supply chain -- this could be open source, offshore, outsourced, or third-party component suppliers," she says.

Many organizations, including large software companies, are using third-party code to meet time-to-market pressures, as well as to lower their overhead. "Open source is free, [for example], and a way to get innovation and a competitive advantage supporting their brand," she says.

But using outside code has its disadvantages. More than 40 percent of the survey respondents say that product delays, vulnerabilities, increased development time, or revenue impact resulting from problems in their third-party code is leading them to look more closely at that code.

Forrester surveyed 336 software development professionals in North America and Europe for the report. A full copy of the report is available for download here.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

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 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.