Difference between revisions of "Source Code Analysis Tools"

Revision as of 14:31, 6 January 2009

Source Code Analysis tools are designed to analyze source code and/or compiled version of code in order to help find security flaws. Ideally, such tools would automatically find security flaws with a high degree of confidence that what is found is indeed a flaw. However, this is beyond the state of the art for many types of application security flaws. Thus, such tools frequently serve as aids for an analyst to help them zero in on security relevant portions of code so they can find flaws more efficiently, rather than a tool that simply finds flaws automatically.

Some tools are starting to move into the IDE. For the types of problems that can be detected during the software development phase itself, this is a powerful phase within the development lifecycle to employ such tools, as it provides immediate feedback to the developer on issues they might be introducing into the code during code development itself. This immediate feedback is very useful as compared to finding vulnerabilities much later in the development cycle.

Strengths and Weaknesses of such tools

Strengths

• Scales Well (Can be run on lots of software, and can be repeatedly (like in nightly builds))
• For things that such tools can automatically find with high confidence, such as buffer overflows, SQL Injection Flaws, etc. they are great.

Weaknesses

• Many types of security vulnerabilities are very difficult to find automatically, such as authentication problems, access control issues, insecure use of cryptography, etc. The current state of the art only allows such tools to automatically find a relatively small percentage of application security flaws. Tools of this type are getting better, however.
• High numbers of false positives.
• Frequently can't find configuration issues, since they are not represented in the code.
• Difficult to 'prove' that an identified security issue is an actual vulnerability.
• Many of these tools have difficulty analyzing code that can't be compiled. Analysts frequently can't compile code because they don't have the right libraries, all the compilation instructions, all the code, etc.

Important Selection Criteria

• Requirement: Must support your language, but not usually a key factor once it does.

• Types of Vulnerabilities it can detect (Out of the OWASP Top Ten?) (plus more?)
• Does it require a fully buildable set of source?
• Can it run against binaries instead of source?
• Can it be integrated into the developer's IDE?

OWASP Tools Of This Type

• OWASP LAPSE Project

Open Source or Free Tools Of This Type

• FindBugs - Find Bugs (including some security flaws) in Java Programs
• FxCop (Microsoft) - FxCop is an application that analyzes managed code assemblies (code that targets the .NET Framework common language runtime) and reports information about the assemblies, such as possible design, localization, performance, and security improvements.
• PreFast (Microsoft) - PREfast is a static analysis tool that identifies defects in C/C++ programs
• RATS (Fortify) - Scans C, C++, Perl, PHP and Python source code for security problems like buffer overflows and TOCTOU (Time Of Check, Time Of Use) race conditions
• SWAAT - Simplistic Beta Tool - Languages: Java, JSP, ASP .Net, and PHP

Commercial Tools from OWASP Members Of This Type

These vendors have decided to support OWASP by becoming members. OWASP appreciates the support from these organizations, but cannot endorse any commercial products or services.

• Static Source Code Analysis with CodeSecure™ (Armorize Technologies)
• Source Code Analysis (Fortify)
• Ounce (Ounce Labs)

Other Well Known Commercial Tools Of This Type

• Prevent (Coverity)
• Insight (KlocWork)

More Info

• TODO: add comments from: http://lists.owasp.org/pipermail/owasp-dotnet/2006-August/000002.html
• Appendix A: Testing Tools
• NIST's list of Source Code Security Analysis Tools