SPECIAL REPORT: Interop   See more>>

66% Of Security Software Submitted With Flaws

App testing firm Veracode reports that developers need significantly more training on secure-coding skills.

10 Massive Security Breaches
(click image for larger view)
Slideshow: 10 Massive Security Breaches
More than two-thirds of security applications and 82% of customer-focused applications initially have an unacceptable level of security quality, compared with just 58% of applications in general.

That's according to a report from Veracode, which analyzed 4,835 applications that were submitted to its application testing service.


More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Seeing higher numbers of vulnerabilities in security software is especially surprising, since "you're buying these applications to perform a security function, so you'd expect that these applications would be more secure than others," said Sam King, VP of product marketing for Veracode, in an interview.

The report also found that 80% of all submitted Web applications failed to mitigate the top 10 most dangerous vulnerabilities, as identified by the Open Web Application Security Project (OWASP). Interestingly, the Payment Card Industry Data Security Standard also uses the OWASP top 10 list to assess compliance with the standard.

In addition, the report found that since the beginning of 2009, cross-site scripting vulnerability volume has remained constant, while SQL injection vulnerabilities have decreased by 2.4% per quarter. Unfortunately, that's not good news, since just one vulnerability can be exploited by an attacker multiple times, across multiple sites, and as numerous reports have found, the number of attacks against Web applications continue to increase.

The good news, however, is that more than 90% of all software products seen by Veracode were resubmitted and went on to achieve an acceptable quality level within a month, while security products reached an acceptable level, on average, in just three days.

That includes more than just Web applications. Overall, the applications assessed by the report were written in Java (52%), .Net (27%), C/C++ (12%), PHP (6%), and ColdFusion (2%), a mix that Veracode said reflects a typical company's application portfolio. In terms of the industries that submitted software, one-third had software designed for content management and collaboration software (33%), followed by operations (25%), security (13%), finance (12%), and customer-centric software (11%).

When it comes to coding clean software, the finance industry remains the sector to beat. Interestingly, the finance and software industries together account for more than 75% of the businesses that require their third-party software suppliers to undergo formal code evaluation. But aerospace and defense are also starting to require much more code verification of suppliers, said King.

Veracode pitches its report as a "before" picture, compared with reports that assess the damage caused by attackers who exploit software vulnerabilities, for example in the Verizon Data Breach Investigations Report.

One sure-fire technique for increasing the quality of code and cutting down on data breaches is to create a secure development program with top-level backing. But the former part of that equation requires knowledge and expertise on the part of coders. In other words, they need training.

According to the report, many developers don't have secure-coding skills when they get hired, as "application security training and education is not a formal part of most computer science curriculums and certainly not a consistent theme in the professional development opportunities made available to technology professionals in companies," it said.

Servers running VMs are still just servers. Stick with security practices you know to minimize risk. Also in the new all-digital InformationWeek supplement: Trust but verify when it comes to hypervisor security. Download it now. (Free registration required.)

Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips 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.
Subscribe to RSS

Resource Links