2009 International Conference on Availability, Reliability and Security (2009)
Fukuoka Institute of Technology, Fukuoka, Japan
Mar. 16, 2009 to Mar. 19, 2009
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ARES.2009.163
Code reviews with static analysis tools are today recommended by several security development processes. Developers are expected to use the tools' output to detect the security threats they themselves have introduced in the source code. This approach assumes that all developers can correctly identify a warning from a static analysis tool (SAT) as a security threat that needs to be corrected. We have conducted an industry experiment with a state of the art static analysis tool and real vulnerabilities. We have found that average developers do not correctly identify the security warnings and only developers with specific experiences are better than chance in detecting the security vulnerabilities. Specific SAT experience more than doubled the number of correct answers and a combination of security experience and SAT experience almost tripled the number of correct security answers.
security, vulnerabilities, static code analysis, coverity, prevent, industry experiment, static analysis, experience, software security
K. Petersen, B. Carlsson, D. Baca and L. Lundberg, "Static Code Analysis to Detect Software Security Vulnerabilities - Does Experience Matter?," 2009 International Conference on Availability, Reliability and Security(ARES), Fukuoka Institute of Technology, Fukuoka, Japan, 2009, pp. 804-810.