DOCSLIB.ORG

Best Practices for the Use of Static Code Analysis Within a Real-World Secure Development Lifecycle

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Best Practices for the Use of Static Code Analysis Within a Real-World Secure Development Lifecycle An NCC Group Publication Best Practices for the use of Static Code Analysis within a Real-World Secure Development Lifecycle Prepared by: Jeremy Boone © Copyright 2015 NCC Group Contents 1 Executive Summary ....................................................................................................................................... 3 2 Purpose and Motivation ................................................................................................................................. 3 3 Why SAST Often Fails ................................................................................................................................... 4 4 Methodology .................................................................................................................................................. 4 5 Integration with the Secure Development Lifecycle....................................................................................... 5 5.1 Training ................................................................................................................................................. 6 5.2 Requirements ....................................................................................................................................... 6 5.3 Design ................................................................................................................................................... 7 5.4 Implementation ..................................................................................................................................... 7 5.5 Verification ............................................................................................................................................ 7 5.6 Release................................................................................................................................................. 7 5.7 Response and Sustainment ................................................................................................................. 8 6 Evaluating and Deploying a SAST Solution .................................................................................................. 8 6.1 Programming Language Support ......................................................................................................... 8 6.2 Selecting Natural and Artificial Code Bases ......................................................................................... 9 6.3 Development Support Systems ............................................................................................................ 9 6.3.1 Compiler and Build System ..................................................................................................... 9 6.3.2 Integrated Development Environment ................................................................................... 10 6.3.3 Continuous Integration........................................................................................................... 10 6.3.4 Collaborative Peer Code Review Systems ............................................................................ 11 6.3.5 Nightly Builds ......................................................................................................................... 11 6.3.6 Distributed Analysis ............................................................................................................... 12 6.3.7 Bug Trackers ......................................................................................................................... 12 6.3.8 Revision Control System ....................................................................................................... 12 6.4 The Analysis Engine ........................................................................................................................... 13 6.4.1 Defect Classes ....................................................................................................................... 13 6.4.2 Accuracy and Precision ......................................................................................................... 13 6.4.3 Sensitivity ............................................................................................................................... 14 6.4.4 False Positive Suppression ................................................................................................... 14 6.4.5 Dealing with Legacy Defects ................................................................................................. 15 6.4.6 Creating Custom Rulesets ..................................................................................................... 15 6.4.7 Analysis Speed ...................................................................................................................... 16 6.5 Defect Triage Maturity ........................................................................................................................ 16 6.5.1 Severity .................................................................................................................................. 16 6.5.2 Detailed Trace and Remediation Guidance........................................................................... 17 6.5.3 Collapse Similar Defects........................................................................................................ 17 6.5.4 Support for Multiple Branches ............................................................................................... 17 6.5.5 Triage Workflow and Multi-User Collaboration ...................................................................... 17 6.5.6 Isolate Users or Teams .......................................................................................................... 17 6.5.7 Report Generation ................................................................................................................. 18 6.6 Vendor Roadmap ............................................................................................................................... 19 7 Final Words .................................................................................................................................................. 20 NCC Group | Page 2 © Copyright 2015 NCC Group 1 Executive Summary Static application security testing (SAST) is the analysis of computer software that is performed without the need to actually execute the program. The term is usually applied to analysis performed by an automated tool, whereas human analysis is typically called security-focused code review. The primary objective of SAST is to gain an understanding of the software’s behaviour, usually with the aim of uncovering security, privacy, and quality defects. In recent years, commercial SAST solutions have matured considerably, and they now offer numerous methods of integrating with various development processes and support systems: continuous integration, bug trackers, revision control, peer code review tools, and so on. However, NCC Group routinely encounters ineffective or suboptimal static analysis deployments that either fail to accommodate the requirements of a secure development lifecycle (SDLC) or tend to impose a significant burden on development staff, leading to disengagement and patterns of misuse. These shortcomings frequently result in the SAST solution failing to serve its primary purpose: to improve software security. In this paper we describe a methodology for evaluating and selecting the most appropriate static code analysis solution for your software organisation, as well as best practice guidance for effectively integrating that solution with your development procedures as part of a mature secure development lifecycle. Unfortunately, we must intentionally avoid recommending a specific SAST solution, because in our experience there is no “one size fits all” solution; besides which, vendors typically place DeWitt clauses1 in their EULAs, to prevent the publishing of benchmark data. 2 Purpose and Motivation The primary motivator that drives the use of static code analysis within a software development organisation is the ability to deliver higher-quality and more secure products at a cheaper price. Studies indicate that automated static code analysis can detect up to 60% of post-release failures2. This metric becomes significant when you consider that a single failure can lead to widespread and costly product recalls. For example: In 2002, the National Institute of Standards and Technology (NIST) showed that the annual cost of software defects to the American economy is approximately $59.5 billion3. In 2015, Charlie Miller and Chris Valasek discovered security defects that led to the recall of 1.4 million Fiat Chrysler vehicles4. In 2011, the FDA stated that 24% of medical device recalls can be attributed to software defects5. So it becomes easy to imagine how a modest investment in SAST can help to avoid expensive recalls or patching of in-field products. Fearmongering aside, it should be recognised that static code analysis is neither a silver bullet nor a panacea. Forrester’s TechRadar Q2 2015 Application Security report 6 summarised it well: SAST provides a significant value to its customers — it has a proven track record and provides extensive benefits. To gain maximum advantage from SAST […] teams must be fairly mature and capable of systematic follow-through on remediation. SAST will continue to see significant success […] for another five to 10 years as application environments become
Load more

Recommended publications
  • Parasoft Dottest REDUCE the RISK of .NET DEVELOPMENT
    Parasoft dotTEST REDUCE THE RISK OF .NET DEVELOPMENT TRY IT https://software.parasoft.com/dottest Complement your existing Visual Studio tools with deep static INCREASE analysis and advanced PROGRAMMING EFFICIENCY: coverage. An automated, non-invasive solution that the related code, and distributed to his or her scans the application codebase to iden- IDE with direct links to the problematic code • Identify runtime bugs without tify issues before they become produc- and a description of how to fix it. executing your software tion problems, Parasoft dotTEST inte- grates into the Parasoft portfolio, helping When you send the results of dotTEST’s stat- • Automate unit and component you achieve compliance in safety-critical ic analysis, coverage, and test traceability testing for instant verification and industries. into Parasoft’s reporting and analytics plat- regression testing form (DTP), they integrate with results from Parasoft dotTEST automates a broad Parasoft Jtest and Parasoft C/C++test, allow- • Automate code analysis for range of software quality practices, in- ing you to test your entire codebase and mit- compliance cluding static code analysis, unit testing, igate risks. code review, and coverage analysis, en- abling organizations to reduce risks and boost efficiency. Tests can be run directly from Visual Stu- dio or as part of an automated process. To promote rapid remediation, each problem detected is prioritized based on configur- able severity assignments, automatical- ly assigned to the developer who wrote It snaps right into Visual Studio as though it were part of the product and it greatly reduces errors by enforcing all your favorite rules. We have stuck to the MS Guidelines and we had to do almost no work at all to have dotTEST automate our code analysis and generate the grunt work part of the unit tests so that we could focus our attention on real test-driven development.
    [Show full text]
  • Parasoft Static Application Security Testing (SAST) for .Net - C/C++ - Java Platform
    Parasoft Static Application Security Testing (SAST) for .Net - C/C++ - Java Platform Parasoft® dotTEST™ /Jtest (for Java) / C/C++test is an integrated Development Testing solution for automating a broad range of testing best practices proven to improve development team productivity and software quality. dotTEST / Java Test / C/C++ Test also seamlessly integrates with Parasoft SOAtest as an option, which enables end-to-end functional and load testing for complex distributed applications and transactions. Capabilities Overview STATIC ANALYSIS ● Broad support for languages and standards: Security | C/C++ | Java | .NET | FDA | Safety-critical ● Static analysis tool industry leader since 1994 ● Simple out-of-the-box integration into your SDLC ● Prevent and expose defects via multiple analysis techniques ● Find and fix issues rapidly, with minimal disruption ● Integrated with Parasoft's suite of development testing capabilities, including unit testing, code coverage analysis, and code review CODE COVERAGE ANALYSIS ● Track coverage during unit test execution and the data merge with coverage captured during functional and manual testing in Parasoft Development Testing Platform to measure true test coverage. ● Integrate with coverage data with static analysis violations, unit testing results, and other testing practices in Parasoft Development Testing Platform for a complete view of the risk associated with your application ● Achieve test traceability to understand the impact of change, focus testing activities based on risk, and meet compliance
    [Show full text]
  • Devnet Module 3
    Module 3: Software Development and Design DEVASCv1 1 Module Objectives . Module Title: Software Development and Design . Module Objective: Use software development and design best practices. It will comprise of the following sections: Topic Title Topic Objective 3.1 Software Development Compare software development methodologies. 3.2 Software Design Patterns Describe the benefits of various software design patterns. 3.3 Version Control Systems Implement software version control using GIT. 3.4 Coding Basics Explain coding best practices. 3.5 Code Review and Testing Use Python Unit Test to evaluate code. 3.6 Understanding Data Formats Use Python to parse different messaging and data formats. DEVASCv1 2 3.1 Software Development DEVASCv1 3 Introduction . The software development process is also known as the software development life cycle (SDLC). SDLC is more than just coding and also includes gathering requirements, creating a proof of concept, testing, and fixing bugs. DEVASCv1 4 Software Development Life Cycle (SDLC) . SDLC is the process of developing software, starting from an idea and ending with delivery. This process consists of six phases. Each phase takes input from the results of the previous phase. SDLC is the process of developing software, starting from an idea and ending with delivery. This process consists of six phases. Each phase takes input from the results of the previous phase. Although the waterfall methods is still widely used today, it's gradually being superseded by more adaptive, flexible methods that produce better software, faster, with less pain. These methods are collectively known as “Agile development.” DEVASCv1 5 Requirements and Analysis Phase . The requirements and analysis phase involves the product owner and qualified team members exploring the stakeholders' current situation, needs and constraints, present infrastructure, and so on, and determining the problem to be solved by the software.
    [Show full text]
  • Metrics for Gerrit Code Reviews
    SPLST'15 Metrics for Gerrit code reviews Samuel Lehtonen and Timo Poranen University of Tampere, School of Information Sciences, Tampere, Finland [email protected],[email protected] Abstract. Code reviews are a widely accepted best practice in mod- ern software development. To enable easier and more agile code reviews, tools like Gerrit have been developed. Gerrit provides a framework for conducting reviews online, with no need for meetings or mailing lists. However, even with the help of tools like Gerrit, following and monitoring the review process becomes increasingly hard, when tens or even hun- dreds of code changes are uploaded daily. To make monitoring the review process easier, we propose a set of metrics to be used with Gerrit code review. The focus is on providing an insight to velocity and quality of code reviews, by measuring different review activities based on data, au- tomatically extracted from Gerrit. When automated, the measurements enable easy monitoring of code reviews, which help in establishing new best practices and improved review process. Keywords: Code quality; Code reviews; Gerrit; Metrics; 1 Introduction Code reviews are a widely used quality assurance practice in software engineer- ing, where developers read and assess each other's code before it is integrated into the codebase or deployed into production. Main motivations for reviews are to detect software defects and to improve code quality while sharing knowledge among developers. Reviews were originally introduced by Fagan [4] already in 1970's. The original, formal type of code inspections are still used in many com- panies, but has been often replaced with more modern types of reviews, where the review is not tied to place or time.
    [Show full text]
  • Code Review Guide
    CODE REVIEW GUIDE 2.0 RELEASE Project leaders: Larry Conklin and Gary Robinson Creative Commons (CC) Attribution Free Version at: https://www.owasp.org 1 F I 1 Forward - Eoin Keary Introduction How to use the Code Review Guide 7 8 10 2 Secure Code Review 11 Framework Specific Configuration: Jetty 16 2.1 Why does code have vulnerabilities? 12 Framework Specific Configuration: JBoss AS 17 2.2 What is secure code review? 13 Framework Specific Configuration: Oracle WebLogic 18 2.3 What is the difference between code review and secure code review? 13 Programmatic Configuration: JEE 18 2.4 Determining the scale of a secure source code review? 14 Microsoft IIS 20 2.5 We can’t hack ourselves secure 15 Framework Specific Configuration: Microsoft IIS 40 2.6 Coupling source code review and penetration testing 19 Programmatic Configuration: Microsoft IIS 43 2.7 Implicit advantages of code review to development practices 20 2.8 Technical aspects of secure code review 21 2.9 Code reviews and regulatory compliance 22 5 A1 3 Injection 51 Injection 52 Blind SQL Injection 53 Methodology 25 Parameterized SQL Queries 53 3.1 Factors to Consider when Developing a Code Review Process 25 Safe String Concatenation? 53 3.2 Integrating Code Reviews in the S-SDLC 26 Using Flexible Parameterized Statements 54 3.3 When to Code Review 27 PHP SQL Injection 55 3.4 Security Code Review for Agile and Waterfall Development 28 JAVA SQL Injection 56 3.5 A Risk Based Approach to Code Review 29 .NET Sql Injection 56 3.6 Code Review Preparation 31 Parameter collections 57 3.7 Code Review Discovery and Gathering the Information 32 3.8 Static Code Analysis 35 3.9 Application Threat Modeling 39 4.3.2.
    [Show full text]
  • Nudge: Accelerating Overdue Pull Requests Towards Completion
    Nudge: Accelerating Overdue Pull Requests Towards Completion CHANDRA MADDILA, Microsoft Research SAI SURYA UPADRASTA, Microsoft Research CHETAN BANSAL, Microsoft Research NACHIAPPAN NAGAPPAN, Microsoft Research GEORGIOS GOUSIOS, Delft University of Technology ARIE van DEURSEN, Delft University of Technology Pull requests are a key part of the collaborative software development and code review process today. However, pull requests can also slow down the software development process when the reviewer(s) or the author do not actively engage with the pull request. In this work, we design an end-to-end service, Nudge, for accelerating overdue pull requests towards completion by reminding the author or the reviewer(s) to engage with their overdue pull requests. First, we use models based on effort estimation and machine learning to predict the completion time for a given pull request. Second, we use activity detection to filter out pull requests that may be overdue, but for which sufficient action is taking place nonetheless. Lastly, we use actor identification to understand who the blocker of the pull request is and nudge the appropriate actor (author or reviewer(s)). We also conduct a correlation analysis to understand the statistical relationship between the pull request completion times and various pull request and developer related attributes. Nudge has been deployed on 147 repositories at Microsoft since 2019. We perform a large scale evaluation based on the implicit and explicit feedback we received from sending the Nudge notifications on 8,500 pull requests. We observe significant reduction in completion time, by over 60%, for pull requests which were nudged thus increasing the efficiency of the code review process and accelerating the pull request progression.
    [Show full text]
  • The Impact of Code Review Coverage and Code Review Participation on Software Quality
    The Impact of Code Review Coverage and Code Review Participation on Software Quality A Case Study of the Qt, VTK, and ITK Projects Shane McIntosh1, Yasutaka Kamei2, Bram Adams3, and Ahmed E. Hassan1 1Queen’s University, Canada 2Kyushu University, Japan 3Polytechnique Montréal, Canada 1{mcintosh, ahmed}@cs.queensu.ca [email protected] [email protected] ABSTRACT 1. INTRODUCTION Software code review, i.e., the practice of having third-party Software code reviews are a well-documented best practice team members critique changes to a software system, is a for software projects. In Fagan's seminal work, formal design well-established best practice in both open source and pro- and code inspections with in-person meetings were found prietary software domains. Prior work has shown that the to reduce the number of errors detected during the testing formal code inspections of the past tend to improve the qual- phase in small development teams [8]. Rigby and Bird find ity of software delivered by students and small teams. How- that the modern code review processes that are adopted in a ever, the formal code inspection process mandates strict re- variety of reviewing environments (e.g., mailing lists or the view criteria (e.g., in-person meetings and reviewer check- Gerrit web application1) tend to converge on a lightweight lists) to ensure a base level of review quality, while the mod- variant of the formal code inspections of the past, where ern, lightweight code reviewing process does not. Although the focus has shifted from defect-hunting to group problem- recent work explores the modern code review process qual- solving [34].
    [Show full text]
  • Modern Code Review: a Case Study at Google
    Modern Code Review: A Case Study at Google Caitlin Sadowski, Emma Söderberg, Alberto Bacchelli Luke Church, Michal Sipko University of Zurich Google, Inc. bacchelli@ifi.uzh.ch {supertri,emso,lukechurch,sipkom}@google.com ABSTRACT novel context. Rigby and Bird quantitatively analyzed code Employing lightweight, tool-based code review of code changes review data from software projects spanning varying domains (aka modern code review) has become the norm for a wide as well as organizations and found five strongly convergent variety of open-source and industrial systems. In this pa- aspects [33], which they conjectured can be prescriptive to per, we make an exploratory investigation of modern code other projects. The analysis of Rigby and Bird is based on the review at Google. Google introduced code review early on value of a broad perspective (that analyzes multiple projects and evolved it over the years; our study sheds light on why from different contexts). For the development of an empirical Google introduced this practice and analyzes its current body of knowledge, championed by Basili [7], it is essential status, after the process has been refined through decades of to also consider a focused and longitudinal perspective that code changes and millions of code reviews. By means of 12 analyzes a single case. This paper expands on work by Rigby interviews, a survey with 44 respondents, and the analysis and Bird to focus on the review practices and characteristics of review logs for 9 million reviewed changes, we investigate established at Google, i.e., a company with a multi-decade motivations behind code review at Google, current practices, history of code review and a high-volume of daily reviews to and developers’ satisfaction and challenges.
    [Show full text]
  • What Makes a Code Review Trustworthy?
    What makes a Code Review Trustworthy? Stacy Nelson† and Johann Schumann‡ †Nelson Consulting Company, [email protected] ‡RIACS / NASA Ames, [email protected] Abstract then, a rich body of checklists, coding standards, and litera- ture about this topic has been published. Despite the exist- Code review is an important step during the process of ing lists of properties, the actual decision of which proper- certifying safety-critical software because only code that ties are most important is usually based on the experience of passes review can be implemented. Reviews are performed the person in charge. In this paper, we address the question by review boards composed of highly skilled and experi- how code review can contribute to certification of trustwor- enced computer scientists, engineers and analysts who gen- thy code. erally rely upon a checklist of properties ranging from high- We made a survey within NASA and the Aerospace in- level requirements to minute language details. While many dustry regarding which of the properties are most impor- checklists and coding standards exist, the actual decision of tant during the code review, and if there exists a subset of which properties are most important is generally based on properties, that, when fulfilled, the code is considered to be the experience of the person in charge. trustworthy. This paper addresses the questions: How can code re- For a better presentation, we have developed a classifica- view ensure certification of trustworthy code? and Is code tion of the most common properties along different ”views”, review trustworthy? We surveyed technical leaders at NASA for example, a standards-oriented view (defined as the prop- and the Aerospace industry to find out which properties are erties needed to satisfy a specific standard like IEEE 12207, most important during the code review.
    [Show full text]
  • Large-Scale Analysis of Modern Code Review Practices and Software Security in Open Source Software
    Large-Scale Analysis of Modern Code Review Practices and Software Security in Open Source Software Christopher Thompson Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2017-217 http://www2.eecs.berkeley.edu/Pubs/TechRpts/2017/EECS-2017-217.html December 14, 2017 Copyright © 2017, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. Acknowledgement I want to thank the people who have supported and guided me along my path to eventually finishing this dissertation. My parents, who encouraged me to explore my various wild fascinations while I was growing up, and who supported me through my undergraduate studies. Nick Hopper, who mentored me throughout my undergraduate studies, and who gave me a chance to learn my love of computer security and research. David Wagner, my doctoral advisor, who has been a constant sounding board for my ideas (including what led to this dissertation), for always having something interesting to teach me, and for always wanting to learn from me as I explored new ideas. And finally, thank you to Hina, who has supported me through graduate school with love and lots of understanding.
    [Show full text]
  • By Gerard Coleman School of Computer Applications, Dublin City University, Glasnevin, Dublin 9. M. Sc., September 1997
    A Quality Software Process for Rapid Application Development By Gerard Coleman School of Computer Applications, Dublin City University, Glasnevin, Dublin 9. M. Sc., September 1997 A Quality Software Process for Rapid Application Development A Dissertation Presented in Fulfilment of the Requirement for the M.Sc. Degree September 1997 Gerard Coleman School of Computer Applications Dublin City University Supervisor: Mr. Renaat Verbruggen Declaration I hereby certify that this material, which I now submit for assessment on the programme of study leading to the award of M.Sc. is entirely my own work and has not been taken from the work of others save and to the extent that such work has been cited and acknowledged within the text of my work. Date: Acknowledgements I would like to thank Renaat for his assistance, insight and guidance during the research. I would also like to thank my wife, Fiona, for her encouragement and understanding throughout the compilation of this work. Finally, I would like to thank Patrick O’Beime, Shay Curtin and Gerard McCloskey who gave so generously of their time to review this work. iv Abstract Having a defined and documented standardised software process, together with the appropriate techniques and tools to measure its effectiveness, offers the potential to software producers to improve the quality of their output. Many firms have yet to define their own software process. Yet without a defined process it is impossible to measure success or focus on how development capability can be enhanced. To date, a number of software process improvement frameworks have been developed and implemented.
    [Show full text]
  • Parasoft C/C++ Testing Starter Kit "C/C++ Error-Detection Techniques" White Paper Inomed Case Study NEC Case Study Bovie Case Study Parasoft C/C++Test Data Sheet
    Parasoft C/C++ Testing Starter Kit "C/C++ Error-Detection Techniques" White Paper Inomed Case Study NEC Case Study Bovie Case Study Parasoft C/C++test Data Sheet Integrated Error-Detection Techniques: Find More Bugs in Embedded C Software Software verification techniques such as pattern-based static code analysis, runtime memory monitoring, unit testing, and flow analysis are all valuable techniques for finding bugs in embedded C software. On its own, each technique can help you find specific types of errors. However, if you restrict yourself to applying just one or some of these techniques in isolation, you risk having bugs that slip through the cracks. A safer, more effective strategy is to use all of these complementary techniques in concert. This establishes a bulletproof framework that helps you find bugs which are likely to evade specific techniques. It also creates an environment that helps you find functional problems, which can be the most critical and difficult to detect. This paper will explain how automated techniques such as pattern-based static code analysis, runtime memory monitoring, unit testing, and flow analysis can be used together to find bugs in an embedded C application. These techniques will be demonstrated using Parasoft C++test, an integrated solution for automating a broad range of best practices proven to improve software development team productivity and software quality. As you read this paper—and whenever you think about finding bugs—it’s important to keep sight of the big picture. Automatically detecting bugs such as memory corruption and deadlocks is undoubtedly a vital activity for any development team.
    [Show full text]