Secure Coding SwA Pocket Guide - Build Security In - US-CERT

Create a Secure Development ProcessSecure software development is a process that involves many elements from requirements through design, coding and testing. Akey element in the process is the way information passes between the different teams during software construction. This processmust support secure coding efforts. [Howard 2006]The secure development lifecycle defines process elements for the entire development effort from the very beginning to the end.With respect to the coding process, the typical elements defined include:» Defined coding standards» Compiler settings for secure coding» Source code analysis tools and usage» Approved and banned functions» Secure coding checklist» Security gate checklistsThe primary purpose of the secure development lifecycle process is to engage the project management effort into the overallcoordinated effort. This is done to ensure the software meets the complete set of requirements—including security requirements.Expecting the development team to produce secure code without the coordinated efforts of all the other parties involved in theeffort is unrealistic. Many security issues result not from syntactic errors, but from design issues. Proper coordination betweenthe teams is the primary function of the secure development lifecycle process. A prime example of this cross-teamcommunication comes in the form of Threat Modeling. The threat modeling technique analyzes potential threats to a system anduses the results to design mitigations into the product. This requires communication between several teams, but results insoftware that embodies security thinking, thus thwarting potential threats. Additional information regarding coding standards andguidelines is discussed as part of the “Follow Secure Coding Standards and/or Guidelines” section.For more information regarding secure software design, please reference “Architecture and Design Considerations for SecureSoftware,” which is available in the SwA Pocket Guide Series library.Create an Application GuideBefore the development team can start the coding process, the organization must establish a policy in an application guide that isclear, understandable, and comprehensive enough to help other programmers write the specified code. This way any developercan easily maintain the code. The application guide should contain the following information [Grembi, 2008]:» Where to get specific software (i.e. URL address, servers)» Where to install software (directory structure, hard drives, servers)» Where to find license information» Where to find deployment instructions» How the software is tested and what tools to use» Where to push code into production (server names, IP addresses)» Procedures for checking in and checking out code» Identification of language coding standardsConsistent code is fundamental; however, it is not sufficient for achieving secure code. By following the guide, the developerscan ease readability and increase the likelihood of a healthy teamwork. If created correctly, this guide can be used throughoutthe organization. While the process may need to adjust to the requirements of different projects or departments, this guide shouldhelp disseminate and enforce code development guidelines throughout the organization.Software Assurance Pocket Guide Series:Development Volume VI – Version 2.0, , May 18, 2012Secure Coding6