|
Vulnerability Management Buyer's Checklist Download here |
Mar 01, 2010 | 09:00 AM
By Kelly Jackson HigginsSAN FRANCISCO -- RSA Conference 2010 -- Even with all of the emphasis on writing software with security in mind, most software applications remain riddled with security holes, according to a new report released today about the actual security quality of all types of software.
Around 58 percent of the applications tested by application security testing service provider Veracode in the past year-and-a-half failed to achieve a successful rating in their first round of testing. "The degree of failure to meet acceptable standards on first submission is astounding -- and this is coming from folks who care enough to submit their software to our [application security testing] services," says Roger Oberg, senior vice president of marketing for Veracode. "The implication here is that more than half of all applications are susceptible to the kinds of vulnerabilities we saw at Heartland, Google, DoD, and others -- these were all application-layer attacks."
The data for Veracode's State of Software Security Report comes from a combination of static, dynamic, and manual testing of all types of software across multiple programming languages -- everything from non-Web and Web applications to components and shared libraries. Veracode tests commercial, internally developed, open-source, and outsourced applications, all of which were represented in its findings.
And nearly 90 percent of internally developed applications contained vulnerabilities in the SANS Top 25 and OWASP Top 10 lists of most common programming errors and flaws in the first round of tests, Oberg says.
So is software getting more or less secure? Hard to say, Veracode says, since this is the first such report, and there's nothing to compare it to. "We don't know if it's getting better or worse, but it's pretty bad," Oberg says. "Despite all of the awareness about breaches ... this awareness doesn't translate into sufficient action. We hope this report is a call to action."
Around 60 percent of the software tested by Veracode was internally developed applications; 30 percent, commercial applications; 8 percent, open source; and 2 percent, outsourced. The software was 60 percent Web applications, and 40 percent non-Web, according to Veracode, and came from companies across 15 different industries.
Despite the relatively gloomy picture of developers still missing the mark initially on security, there were some bright spots in the report: Open-source software isn't as risky as you'd think, and financial services organizations and government agencies tend to have more secure applications from the get-go; more than half of their apps passed as acceptable in the first submission to testing, according to Veracode's report.
"The conventional wisdom is that open source is risky. But open source was no worse than commercial software upon first submission. That's encouraging," Oberg says. And it was the quickest to remediate any flaws: "It took about 30 days to remediate open-source software, and much longer for commercial and internal projects," he says.
Meanwhile, financial services firms and government agencies were second-best in terms of remediation: They took anywhere from one to two tries to fix their vulnerabilities. "This is good news. But there's a lot of room for improvement," Oberg says.
The data showed that third-party software is often a part of internally developed apps -- 30 percent of them were based on third-party apps.
The vulnerability with the highest total count was cross-site scripting (XSS), and was the third most prevalent flaw. "There's been intense focus on cross-site scripting, and there are lots of different libraries and utilities available to eliminate it, but it's still extremely prevalent," says Chris Eng, director of security research for Veracode. Eng says it's likely due to a lack of education on how to quell XSS, plus it's not uncommon to find 100 XSS bugs in one application. "Cross-site scripting adds up real quickly," he says.
Around 20 percent of the applications carried a SQL injection flaw, and most of those were Web applications. And 44 percent of the apps had one or more cryptographic flaw issue, Eng says. "Crypto issues are not generally well-understood by developers," he says.
Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.
Applications Security: Eliminating Vulnerabilities in Enterprise Software
Most of the hacks that compromise enterprise security today are those that exploit flaws in applications. How can organizations find and fix these vulnerabilities—before they lead to a breach? Better yet, how can software developers identify flaws in their applications before the new software is ever deployed? In this special retrospective of recent news coverage, Dark Reading offers a look at some tips and tricks for software development and vulnerability assessment, as well as some advice on how to eliminate security flaws in the enterprise.
In a Fix? Try a Vulnerability Remediation Life Cycle
There are plenty of ways to detect vulnerabilities. But assigning priorities and determining the best way to fix them is another matter. Which vulnerabilities need to be dealt with immediately, and which can wait? What should you do when a simple patch won’t suffice? How do you ensure that the problems won’t recur? In this Dark Reading Tech Center report, we explain how to implement a vulnerability remediation process that improves security for the long haul.
Scanning Reality: Limits of Automated Vulnerability Scanners
Network-based vulnerability scanners and Web application scanning tools can be invaluable in identifying exploitable flaws in network devices and Internet-facing software, but they may have weaknesses as well. In this Dark Reading Vulnerability Management Tech Center report, we discuss three critical areas in which scanners fall short -- and how to pick up your security program where they leave off.
Other reports from the Vulnerability Management Tech Center:
| Sponsored by: | ![]() |
Four Steps to Cure Your Patch Management Headache
The need to speed up patch deployment across today’s highly complex and distributed IT environment has never been more important. The heat is on to proactively safeguard your systems and endpoints from the newest exploits as the time it takes hackers to exploit a known vulnerability shrinks.
Laying the IT Security Foundation: Key Steps to Preventing Cyber Attacks
Government systems are getting hit on a daily basis by new and ingenious external attacks. Federal, state and municipal agencies must find a way to adjust to this evolving threat landscape to prevent these threats from wreaking havoc. Government organizations must get back to the basics of security and lay a strong security foundation to weather these attacks by proactively addressing their root causes.
Why Free Patch Management Tools Could Cost You More
Although point patching products may look more attractive on the surface, closer inspection often reveals hidden costs and missing capabilities. The result: fragmented patch management and weaker security posture while also being a more costly and cumbersome option to maintain.
Integrate Desktop Power Savings with Patch Management
Organizations can save significant money by managing the power consumption of their IT systems, but if they aren't careful, they could save their way right into a security and operational nightmare. Conscientiously consider your tools, strategies and policies around power management if you’re seeking to go green without compromising operational efficiency or security.