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.
| To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Choosing the Right Vulnerability Scanner for Your Organization
Vulnerability scanners can be used to help detect and fix systemic problems in an organization's security program and monitor the effectiveness of security controls. However, a vulnerability scanner can improve the organization?s security posture only when it is used as part of a vulnerability management program, in which products, processes and people are working together to find, identify, prioritize and mitigate threats. Here are some tips on choosing and implementing vulnerability scanners in your enterprise.
Using Google to Find Vulnerabilities In Your IT Environment
Attackers are increasingly using a simple method for finding flaws in websites and applications: they Google them. Using Google code search, hackers can identify crucial vulnerabilities in application code strings, providing the entry point they need to break through application security. Sound scary? It is, but there is good news: You can use these same methods to find flaws before the bad guys do. In this special report, we outline methods for using search engines such as Google and Bing to identify vulnerabilities in your applications, systems and services--and to fix them before they can be exploited.
Security Pro's Guide to Patch Management
It's no longer sufficient to patch just Windows, Office and IE. With the massive array of applications now residing on enterprise PCs, and the proliferation of mobile and cloud-based applications, your business is far too vulnerable to exploitation unless you have a solid strategy for patch prioritization, deployment and quality assurance. Follow these steps to put your plan in place.
Other reports from the Vulnerability Management Tech Center:
MORE NEWSFEED >>>