Fortify Software announced May 15 that it is joining the FindBugs project as a sponsor and is offering its static code analysis technology to help open-source developers find dangerous security vulnerabilities and other software bugs in Java programs.
Fortify, based in Palo Alto, Calif., will integrate the FindBugs static analysis tool with its Source Code Analysis product to allow developers to use both tools and to load and view the results from various Fortify tools such as Fortify Audit Workbench and Fortify Software Security Manager.
This gives Java developers a central view of all results with which to catch potential flaws and quality bugs.
FindBugs, with 200,000 downloads, is considered the most widely used open-source bug finding tool for Java. Originally developed by David Hovemeyer and Bill Pugh at the University of Maryland, FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns.
It is written in Java, and can be run with any virtual machine compatible with Suns JDK 1.4. FindBugs can analyze programs written for any version of Java and can be run from the command line, from within Ant, a GUI tool, or IDEs (integrated development environments) such as Eclipse and NetBeans.
According to FindBugs Pugh, the deal “is a win for everyone.”
“[Originally], I was worried that we wouldnt be able to maintain the level of engineering support that a widely used tool such as FindBugs needs, or do many other useful things not easily be funded by academic research grants,” Pugh said. With the new sponsorship, Pugh said the project will get funds to support and improve the open-source FindBugs infrastructure.
Fortify recently inked a deal with Oracle to integrate its code scanning products into the development process for Oracles server technologies.
Oracle has licensed Fortifys software for use with the Oracle Database Server, Application Server, Enterprise Management, Collaboration Suite and identity management products. Oracle is using the technology to find buffer overflows, heap overflows and other common security holes in code under development.
Code scanning technology is also a big part of a U.S. government-funded software auditing project aimed at beefing up the security and reliability of several widely deployed open-source products.
The “Vulnerability Discovery and Remediation Open Source Hardening Project” uses source code analysis technology from San Francisco-based Coverity to pinpoint and correct security vulnerabilities and other potentially dangerous defects in key open-source packages.
Coveritys automated scans have pinpointed several bugs in the LAMP (Linux, Apache, MySQL and Perl/Python/PHP) stack, including a critical vulnerability in the X Window System code, but security experts warn that total dependence on static code scanning is a mistake.
While static analysis tools are useful, they are no replacement for the human intellect, said Michael Howard, senior security program manager at Microsoft, in Redmond, Wash.
“If a developer does not know how to code securely or if a designer does not know how to design secure systems, and testers dont know how to validate the security posture of code, tools will provide little, if any, help,” said Howard, who co-wrote Microsofts SDL (Security Development Lifecycle).
Editors Note: This story was updated to include information and comments from Michael Howard.
