Risk
7/22/2013
07:12 AM
Quick Hits
Quick Hits
Quick Hits
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Integrating Vulnerability Management Into The Application Development Process

App developers often fail to do proper vulnerability scanning. Here are some ways to plug those holes

[The following is excerpted from "Integrating Vulnerability Management Into the Application Development Process," a new report posted this week on the Dark Reading Vulnerability Management Tech Center.]

Software developers are only human, which means that complex application code will include errors and bugs. This means that scanning and combing new application code for security flaws are part of virtually every software development process. But not all developers approach vulnerability discovery the same way -- and very few of them catch all of their code vulnerabilities on the first try.

The effects of coding errors can be crippling. In 2003, a bug in General Electric's monitoring software cut off power to an estimated 50 million people. More recently, Knight Capital's computers erroneously executed a series of automatic stock orders that brought the company to the edge of bankruptcy, while HTC America has had to settle a civil suit with the Federal Trade Commission after a modification to the software on its Android- and Windows-based phones introduced numerous security vulnerabilities.

The pressure to get new products ready for market imposes accelerated timetables on developers, resulting in even more mistakes. When first released, Apple's Maps app, for example, was plagued with errors, damaged Apple's reputation and cost the executive held responsible his job. (It also led to a very public apology from Apple CEO Tim Cook.)

However, while the problem of vulnerabilities in complex applications is big, that doesn't mean it can't be tackled. Organizations may never attain completely error-free nirvana, but they can certainly make it a goal. One of the keys to getting as close as possible is the tight integration of vulnerability management in the application development process.

According to recent Cambridge University research, the global cost of debugging software has risen to $312 billion annually, with software developers spending on average 50% of their programming time discussing, finding, addressing and debugging software flaws. Other, less obvious costs are associated with fixing software as well: missed and unreliable deadlines, overtime and duplicated effort, disgruntled customers, reputation damage and even legal action.

Research and the experience of companies such as Microsoft show that the most effective way to avoid these problems and keep overall development time and costs down is to minimize the number of coding errors made during development and to catch those that do occur as early as possible during the application development life cycle. The cost of discovering defects after release is up to 30 times more than when they are caught in the design and architectural phase.

To learn more about vulnerability scanning and how it can be integrated into the software development process, download the free report.

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

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

CVE-2014-2392
Published: 2014-04-24
The E-Mail autoconfiguration feature in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 places a password in a GET request, which allows remote attackers to obtain sensitive information by reading (1) web-server access logs, (2) web-server Referer log...

CVE-2014-2393
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in Open-Xchange AppSuite 7.4.1 before 7.4.1-rev11 and 7.4.2 before 7.4.2-rev13 allows remote attackers to inject arbitrary web script or HTML via a Drive filename that is not properly handled during use of the composer to add an e-mail attachment.

CVE-2011-5279
Published: 2014-04-23
CRLF injection vulnerability in the CGI implementation in Microsoft Internet Information Services (IIS) 4.x and 5.x on Windows NT and Windows 2000 allows remote attackers to modify arbitrary uppercase environment variables via a \n (newline) character in an HTTP header.

CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

Best of the Web