DOCSLIB.ORG

(Draft) Mitigating the Risk of Software Vulnerabilities by Adopting A

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
(Draft) Mitigating the Risk of Software Vulnerabilities by Adopting A NIST CYBERSECURITY WHITE PAPER (DRAFT) CSRC.NIST.GOV 1 Mitigating the Risk of Software 2 Vulnerabilities by Adopting a Secure 3 Software Development Framework (SSDF) 4 5 Donna Dodson 6 Applied Cybersecurity Division 7 Information Technology Laboratory 8 9 Murugiah Souppaya 10 Computer Security Division 11 Information Technology Laboratory 12 13 Karen Scarfone 14 Scarfone Cybersecurity 15 Clifton, VA 16 17 18 June 11, 2019 19 20 21 22 NIST CYBERSECURITY WHITE PAPER (DRAFT) MITIGATING THE RISK OF SOFTWARE JUNE 11, 2019 VULNERABILITIES BY ADOPTING AN SSDF 23 Abstract 24 Few software development life cycle (SDLC) models explicitly address software security in detail, 25 so secure software development practices usually need to be added to each SDLC model to ensure 26 the software being developed is well secured. This white paper recommends a core set of high- 27 level secure software development practices, called a secure software development framework 28 (SSDF), to be added to each SDLC implementation. The paper facilitates communications about 29 secure software development practices amongst business owners, software developers, and 30 cybersecurity professionals within an organization. Following these practices should help software 31 producers reduce the number of vulnerabilities in released software, mitigate the potential impact 32 of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of 33 vulnerabilities to prevent future recurrences. Software consumers can reuse and adapt the practices 34 in their software acquisition processes. 35 Keywords 36 secure software development; secure software development framework (SSDF); secure software 37 development practices; software acquisition; software development; software development life 38 cycle (SDLC); software security. 39 Disclaimer 40 Any mention of commercial products or reference to commercial organizations is for information 41 only; it does not imply recommendation or endorsement by NIST, nor does it imply that the 42 products mentioned are necessarily the best available for the purpose. 43 Additional Information 44 For additional information on NIST’s Cybersecurity programs, projects and publications, visit the 45 Computer Security Resource Center. Information on other efforts at NIST and in the Information 46 Technology Laboratory (ITL) is also available. 47 48 Public Comment Period: June 11, 2019 through August 5, 2019 49 National Institute of Standards and Technology 50 Attn: Computer Security Division, Information Technology Laboratory 51 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 52 Email: [email protected] 53 All comments are subject to release under the Freedom of Information Act (FOIA). 54 55 ii NIST CYBERSECURITY WHITE PAPER (DRAFT) MITIGATING THE RISK OF SOFTWARE JUNE 11, 2019 VULNERABILITIES BY ADOPTING AN SSDF 56 Acknowledgments 57 The authors wish to thank all the individuals and organizations who provided comments on the 58 preliminary ideas and drafts, particularly BSA | The Software Alliance, the Information Security 59 and Privacy Advisory Board (ISPAB), and the members of the Software Assurance Forum for 60 Excellence in Code (SAFECode). 61 Audience 62 There are two primary audiences for this white paper. The first is software producers (e.g., 63 commercial-off-the-shelf [COTS] product vendors, government-off-the-shelf [GOTS] software 64 developers, custom software developers) regardless of size, sector, or level of maturity. The second 65 is software consumers, both federal government agencies and other organizations. Readers of this 66 document are not expected to be experts in secure software development in order to understand it, 67 but such expertise is required to implement its recommended practices. 68 Personnel within the following Workforce Categories and Specialty Areas from the National 69 Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework [1] are most 70 likely to find this publication of interest: 71 • Securely Provision (SP): Risk Management (RSK), Software Development (DEV), 72 Systems Requirements Planning (SRP), Test and Evaluation (TST), Systems Development 73 (SYS) 74 • Operate and Maintain (OM): Systems Analysis (ANA) 75 • Oversee and Govern (OV): Training, Education, and Awareness (TEA), Cybersecurity 76 Management (MGT), Executive Cyber Leadership (EXL), Program/Project Management 77 (PMA) and Acquisition 78 • Protect and Defend (PR): Incident Response (CIR), Vulnerability Assessment and 79 Management (VAM) 80 • Analyze (AN): Threat Analysis (TWA), Exploitation Analysis (EXP) 81 Trademark Information 82 All registered trademarks or trademarks belong to their respective organizations. 83 Note to Reviewers 84 This white paper is intended as a starting point for discussing the concept of a secure software 85 development framework (SSDF), and it does not provide a comprehensive view of SSDFs. Future 86 work will expand on the material in this white paper, potentially covering topics such as how an 87 SSDF may apply to and vary for different software development methodologies, and how an 88 organization can transition from using just their current software development practices to also 89 incorporating the practices specified by the SSDF. It is likely that the future work will primarily 90 take the form of use cases so the insights will be more readily applicable to certain types of 91 development environments. iii NIST CYBERSECURITY WHITE PAPER (DRAFT) MITIGATING THE RISK OF SOFTWARE JUNE 11, 2019 VULNERABILITIES BY ADOPTING AN SSDF 92 Table of Contents 93 1 Introduction ............................................................................................................ 1 94 2 Secure Software Development Framework (SSDF) ............................................. 3 95 References ................................................................................................................... 17 96 Appendix A— Acronyms ............................................................................................ 19 97 iv NIST CYBERSECURITY WHITE PAPER (DRAFT) MITIGATING THE RISK OF SOFTWARE JUNE 11, 2019 VULNERABILITIES BY ADOPTING AN SSDF 98 1 Introduction 99 A software development life cycle (SDLC) is a formal or informal methodology for designing, 100 creating, and maintaining software. There are many models for SDLCs, including waterfall, spiral, 101 agile, and Development and Operations (DevOps). Few SDLC models explicitly address software 102 security in detail, so secure software development practices usually need to be added to and 103 integrated within each SDLC model to ensure the software being developed under that model is 104 well secured. Regardless of which SDLC model is used to develop software, secure software 105 development practices should be integrated throughout it for three reasons: to reduce the number 106 of vulnerabilities in released software, to mitigate the potential impact of the exploitation of 107 undetected or unaddressed vulnerabilities, and to address the root causes of vulnerabilities to 108 prevent future recurrences. Most aspects of security can be addressed at multiple places within an 109 SDLC, but in general, the earlier in the SDLC security is addressed, the less effort is ultimately 110 required to achieve the same level of security. 111 There are many existing documents on secure software development practices. This white paper 112 does not introduce new practices or define new terminology; instead, it describes a subset of high- 113 level practices based on established standards, guidance, and secure software development practice 114 documents. These practices, collectively called a secure software development framework (SSDF), 115 should be particularly helpful for the target audiences to achieve security software development 116 objectives. 117 This white paper expresses secure software development practices but does not prescribe exactly 118 how to implement them. The most important thing is implementing the practices and not the 119 mechanisms used to do so. For example, one organization might automate a particular step, while 120 another might use manual processes instead. Advantages of specifying the practices at a high level 121 include the following: 122 • Can be used by organizations in any sector or community, regardless of size or 123 cybersecurity sophistication 124 • Can be applied to software developed to support information technology (IT), industrial 125 control systems (ICS), cyber-physical systems (CPS), or the Internet of Things (IoT) 126 • Can be integrated into any existing software development workflow and automated 127 toolchain; should not negatively affect organizations that already have robust secure 128 software development practices in place 129 • Makes the practices broadly applicable—not specific to particular technologies, platforms, 130 programming languages, SDLC models, development environments, operating 131 environments, tools, etc. 132 • Can help an organization document its secure software development baseline today and 133 define its future target baseline as part of its continuous improvement process. 134 • Can assist an organization currently using a classic software development model in 135 transitioning its secure software development practices for use with a modern software 136 development model (e.g., agile, DevOps). 137 This white paper also provides a common language to describe fundamental secure software 138 development practices. This is similar
Load more

Recommended publications
  • Vulnerability Assessment and Secure Coding Practices for Middleware Part 1
    Vulnerability Assessment and Secure Coding Practices for Middleware Part 1 James A. Kupsch Computer Sciences Department University of Wisconsin © 2007-2008, James A. K1upsch. All rights reserved. Tutorial Objectives • Show how to perform the basics of a vulnerability assessment • Create more people doing vulnerability assessments • Show how different types of vulnerabilities arise in a system • Teach coding techniques that can prevent certain types of vulnerabilities • Make your software more secure 2 Roadmap • Part 1: Vulnerability Assessment Process – Introduction – Evaluation process – Architectural analysis – Computer process – Communication channels – Resource analysis – Privilege analysis – Data Flow Diagrams – Component analysis – Vulnerability Discovery Activities • Part 2: Secure Coding Practices 3 Security Problems Are Real Everyone with a computer knows this. If you’re not seeing vulnerability reports and fixes for a piece of software, it doesn’t mean that it is secure. It probably means the opposite; they aren’t looking or aren’t telling. The grid community has been largely lucky (security through obscurity). 4 Many Avenues of Attack We’re looking for attacks that exploit inherent weakness in your system. Internet Firewall: www server Attack web using www protocols Compromised host Internal bad guy 5 Impact of Vulnerabilities FBI estimates computer security incidents cost U.S. businesses $67 billion in 2005 [CNETnews.com] Number of reported vulnerabilities each year is increasing [CERT stats] 8000 6000 4000 2000 0 1994 1998
    [Show full text]
  • Rogue Automation: Vulnerable and Malicious Code in Industrial
    In partnership with Rogue Automation Vulnerable and Malicious Code in Industrial Programming Federico Maggi Marcello Pogliani Trend Micro Research Politecnico di Milano Rogue Automation Vulnerable and Malicious Code in Industrial Programming Published by TREND MICRO LEGAL DISCLAIMER Trend Micro Research The information provided herein is for general information and educational purposes only. It is not intended and should not be construed to constitute legal advice. The information contained herein may not be applicable to all situations and may not reflect the most Written by current situation. Nothing contained herein should be relied on or acted upon without the benefit of legal advice based on the particular facts and circumstances presented and Federico Maggi nothing herein should be construed otherwise. Trend Micro reserves the right to modify Trend Micro Research the contents of this document at any time without prior notice. Marcello Pogliani Translations of any material into other languages are intended solely as a convenience. Politecnico di Milano Translation accuracy is not guaranteed nor implied. If any questions arise related to the accuracy of a translation, please refer to the original language official version of the document. Any discrepancies or differences created in the translation are not binding and With contributions from have no legal effect for compliance or enforcement purposes. Martino Vittone, Although Trend Micro uses reasonable efforts to include accurate and up-to-date Davide Quarta, information herein, Trend Micro makes no warranties or representations of any kind as to Stefano Zanero its accuracy, currency, or completeness. You agree that access to and use of and reliance Politecnico di Milano on this document and the content thereof is at your own risk.
    [Show full text]
  • Web Application Vulnerabilities and Insecure Software Root Causes: the OWASP Top 10
    Vulnerability Analysis, Secure Development and Risk Management of Web 2.0 Applications Marco Morana OWASP OWASP Cincinnati Chapter, November 2010 Meeting Copyright © 2010 - The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License. The OWASP Foundation http://www.owasp.org What is OWASP? OWASP 2 Agenda For Today’s Presentation 1. The Evolution of Web 2.0 2. Web 2.0 Vulnerability Analysis 3. Building Secure Web 2.0 Applications 4. Web 2.0 Risk Management OWASP 3 The Evolution of the Internet to Web 2.0 OWASP 4 General Web 2.0 Background Can be defined as: “Web applications that facilitate interactive information sharing and collaboration, interoperability, and user-centered design on the World Wide Web” … the main characteristics of web 2.0 are: 1. Encourage user’s participation and collaboration through a virtual community of social networks/sites. Users can and add and update their own content, examples include Twitter and social networks such as Facebook, Myspace, LinkedIn, YouTube 2. Transcend from the technology/frameworks used AJAX, Adobe AIR, Flash, Flex, Dojo, Google Gears and others 3. Combine and aggregate data and functionality from different applications and systems, example include “mashups” as aggregators of client functionality provided by different in-house developed and/or third party services (e.g. web services, SaaS) OWASP 5 Web 2.0 As Evolution of Human Knowledge Source http://digigogy.blogspot.com/2009/02/digital-blooms-visual.html
    [Show full text]
  • From Secure Coding to Secure Software
    From Secure Coding to Secure Software Table of Contents From Secure Coding to Secure Software ........................................................................................ 4 Why Software Security? .................................................................................................................. 6 Software and security failures are rampant ................................................................................... 7 Software and security failures are expensive ................................................................................. 8 Polling Question 2 ........................................................................................................................... 9 Engineering and Development ..................................................................................................... 10 Most Vulnerabilities Are Caused by Programming Errors ............................................................ 11 Secure Software Development ..................................................................................................... 12 Sources of Software Insecurity ..................................................................................................... 13 Polling Question 3 ......................................................................................................................... 15 Coding rules – 2016 Edition .......................................................................................................... 17 CWE Guidance ..............................................................................................................................
    [Show full text]
  • Vulnerabilities, Threats, and Secure Coding Practices
    Vulnerabilities, Threats, and Secure Coding Practices Barton P. Miller Elisa Heymann Computer Sciences Department Computer Sciences Department University of Wisconsin University of Wisconsin [email protected] & Universitat Autònoma de Barcelona [email protected] NSF CyberSecurity Summit 2015 Arlington, August 17 2015 1 What do we do • Assess Middleware: Make cloud/grid software more secure • Train: We teach tutorials for users, developers, sys admins, and managers • Research: Make in-depth assessments more automated and improve quality of automated code analysis http://www.cs.wisc.edu/mist/papers/VAshort.pdf 2 Our History 2001: “Playing Inside the Black Box” paper, first demonstration of hijacking processes in the Cloud. 2004: First formal funding from US NSF. 2004: First assessment activity, based on Condor, and started development of our methodology (FPVA). 2006: Start of joint effort between UW and UAB. 2006: Taught first tutorial at San Diego Supercomputer Center. 2007: First NATO funding, jointly to UAB, UW, and Ben Gurion University. 2008: First authoritative study of automated code analysis tools. 2009: Published detailed report on our FPVA methodology. 2009: U.S. Dept. of Homeland Security funding support. 2012: DHS Software Assurance Marketplace (SWAMP) research center. 3 Our experience includes Condor, University of Wisconsin Batch queuing workload management system 15 vulnerabilities 600 KLOC of C and C++ Google Chrome, Google Web browser 1 vulnerability 2396 KLOC of C and C++ MyProxy, NCSA Credential Management System 5 vulnerabilities
    [Show full text]
  • Software Analysis for Security
    Software Analysis for Security Spiros Mancoridis Department of Computer Science College of Engineering Drexel University Philadelphia, PA 19147, USA E-mail: [email protected] Abstract ware architecture to assure the system’s security. The qual- ity of a security architecture, however, also depends on the This is a survey of the processes, practices, and technolo- security of the applications that constitute the system. In gies that can help software maintenance engineers improve low security operating environments, such as most commer- the security of software systems. A particular emphasis is cial operating systems, it is assumed, albeit optimistically, placed on validating security architectures, verifying that that these applications are trustworthy. Therefore, it is im- the implementation of an architecture’s constituent appli- portant to articulate the practices to support the secure cod- cations adhere to secure coding practices, and protecting ing of applications and the tools for detecting malware. Se- software systems against malicious software. In addition to cure coding involves programming practices and run-time surveying the state-of-the-art, research challenges pertain- mechanisms that can be used to limit the vulnerabilityof ap- ing to software security are posed to the software mainte- plications to dangerous malware that exploit, for example, nance research community. buffer overflows, format string vulnerabilities, and integer vulnerabilities to attack computer systems. One approach to software security is to verify that (a) the security mechanisms used are trustworthy; (b) the security 1. Introduction architecture has been validated against the security policy; and (c) the software applications that constitute the system The goal of computer security is to protect computer as- are trustworthy (e.g., they have been developed using secure sets (e.g., servers, applications, web pages, data) from cor- coding practices, or they are not malware).
    [Show full text]
  • Security Training for Developers
    Security Training for Developers Trusted Advisor for All Your Information Security Needs ® ZERODAYLAB Increasing Cyber Resilience by Coding with the Hacker in Mind Our Security Training for Developers has a simple objective, educating software engineers to reinforce security best practice when developing software to reduce the accidental introduction of security vulnerabilities. By training your development team in the latest secure coding practices, you can bring your overall security costs down by: Reducing the number of incidents Conducting fewer penetration tests and re-tests as fewer vulnerabilities are found Changing the way developers think and increasing their ability to identify other risks Following best practice so that code has fewer bugs overall Using tried-and-tested methods to reduce the need for further corrective coding further down the line and resulting in a faster development cycle. Specialists in Face-to-Face Security Training ZeroDayLab delivers security training courses across the world for staff and management at all levels of an organisation, with or without technical knowledge. Drawn from a wealth of experience from the security projects we deliver for clients every day, we specialise in intensive, face-to-face training with specialist content designed to address the issues your organisation faces. ® ZERODAYLAB Security Training for Developers Security Training for Developers is a comprehensive, on-site training programme based around the 2017 OWASP Top 10. This two-day course will assess, educate and re-test to raise your software engineers’ information security knowledge. As a result, they will develop code with fewer vulnerabilities, expand their knowledge of current threats and tactics and learn hacking techniques.
    [Show full text]
  • Secure Coding Frameworks for the Development of Safe, Secure and Reliable Code
    Building Cybersecurity from the Ground Up Secure Coding Frameworks For the Development of Safe, Secure and Reliable Code Tim Kertis October 2015 The 27 th Annual IEEE Software Technology Conference Copyright © 2015 Raytheon Company. All rights reserved. Customer Success Is Our Mission is a registered trademark of Raytheon Company. Who Am I? Tim Kertis, Software Engineer/Software Architect Chief Software Architect, Raytheon IIS, Indianapolis Master of Science, Computer & Information Science, Purdue Software Architecture Professional through the Software Engineering Institute (SEI), Carnegie-Mellon University (CMU) 30 years of diverse Software Engineering Experience Advocate for Secure Coding Frameworks (SCFs) Author of the JAVA Secure Coding Framework (JSCF) Inventor of Cybersecurity thru Lexical And Symbolic Proxy (CLaSP) technology (patent pending) Secure Coding Frameworks 10/22/2015 2 Top 5 Cybersecurity Concerns … 1 - Application According to the 2015 ISC(2) Vulnerabilities Global Information Security 2 - Malware Workforce Study (Paresh 3 - Configuration Mistakes Rathod) 4 - Mobile Devices 5 - Hackers Secure Coding Frameworks 10/22/2015 3 Worldwide Market Indicators 2014 … Number of Software Total Cost of Cyber Crime: Developers: $500B (McCafee) 18,000,000+ (www.infoq.com) Cost of Cyber Incidents: Number of Java Software Low $1.6M Developers: Average $12.7M 9,000,000+ (www.infoq.com) High $61.0M (Ponemon Institute) Software with Vulnerabilities: 96% (www.cenzic.com) Secure Coding Frameworks 10/22/2015 4 Research
    [Show full text]
  • OWASP Secure Coding Practices Quick Reference Guide
    November 2010 OWASP Secure Coding Practices Quick Reference Guide Copyright and License Copyright © 2010 The OWASP Foundation. This document is released under the Creative Commons Attribution ShareAlike 3.0 license. For any reuse or distribution, you must make clear to others the license terms of this work. http://creativecommons.org/licenses/by-sa/3.0/ Version 2.0 1 November 2010 Table of Contents Introduction .................................................................................................. 3 Software Security and Risk Principles Overview ............................................. 4 Secure Coding Practices Checklist .................................................................. 5 Input Validation: .......................................................................................... 5 Output Encoding: ......................................................................................... 5 Authentication and Password Management: ..................................................... 6 Session Management:.................................................................................... 7 Access Control: ............................................................................................ 8 Cryptographic Practices: ................................................................................ 9 Error Handling and Logging: ......................................................................... 9 Data Protection:...........................................................................................10
    [Show full text]
  • Software Development Guidelines Jan 2019
    SECURE Software Development Guidelines Jan 2019 CONTENT 01 Introduction 02 Secure Software Development 03 Good coding practices 04 Principles of secure code design 05 Examples Secure Software Development Guidelines 2 01 Introduction Introduction Information technology is part of the life-blood The purpose of this presentation is to stand on of modern-day business operations. the shoulders of existing good practices, not Organisations are dependent on reliable and replace recognised ways of secure coding. This secure communications and IT systems. guide provides an overview of good working practices and techniques for assuring the Furthermore, the secure development of development of secure software. software is essential for ensuring the confidentiality, integrity, and availability of It is impractical to eliminate all security information processed within software vulnerabilities. However, by following applications, running upon information recognised good practices, this guide will communication technologies. facilitate changes in behaviours to reduce the likelihood of main security threats. Secure Software Development Guidelines 4 02 Secure Software Development and Standards Overview: Secure Development “Buffer overflows”, “zero-day vulnerabilities”, Secure software development is the art, rather “SQL injection”, are all buzz-words that signify than science, of reducing the likelihood of security problems in software that have systems compromise, given known, common, allowed, for example, a website, or a fat-client insecure development practices. application to become compromised and cracked into by an organised gang, an individual for financial or reputation gain. The sources of these attacks are many and varied (but are explored later on). However what they have in common is an open field to plough and reap financial gain from miss- configured, and insecurely programmed software applications.
    [Show full text]
  • Software Assurance: an Overview of Current Industry Best Practices
    Software Assurance: An Overview of Current Industry Best Practices February 2008 Executive Summary Software Assurance: An Overview of Current Industry Best Practices Software underpins the information infrastructure that govern- ments, critical infrastructure providers and businesses worldwide depend upon for daily operations and business processes. These organizations widely and increasingly use commercial off-the- shelf software (“COTS”) to automate processes with information technology. At the same time, cyber attacks are becoming more stealthy and sophisticated, creating a complex and dynamic risk environment for IT-based operations that users are working to better understand and manage. As such, users have become in- creasingly concerned about the integrity, security and reliability of commercial software. To address these concerns and meet customer requirements, vendors have undertaken significant efforts to reduce vulner- abilities, improve resistance to attack and protect the integrity of the products they sell. These efforts are often referred to as “software assurance.” Software assurance is especially impor- tant for organizations critical to public safety and economic and national security. These users require a high level of confidence that commercial software is as secure as possible, something only achieved when software is created using best practices for secure software development. This white paper provides an overview of how SAFECode mem- bers approach software assurance, and how the use of best practices for software
    [Show full text]
  • Oracle Software Security Assurance Oracle’S Methodology for the Development and Maintenance of Security in Its Products
    ORACLE BRIEF Oracle Software Security Assurance Oracle’s methodology for the development and maintenance of security in its products As organizations increasingly rely on software controls to protect their computing environments and data, ensuring that these controls operate in the way they were intended has become a paramount concern. Software security assurance encompasses all the activities involved in ensuring that software operates at an expected and predictable level of security. Managing security incidents, meeting complex regulatory and auditing requirements, and keeping current with security releases can add tremendous costs to an organization’s IT budget; thus organizations must give careful consideration to how their software providers approach software security assurance. Security built in, not bolted on S T A T I C CODE ANALYSIS Encompassing every phase of the product development lifecycle, Oracle Software Static security analysis of source code Security Assurance is Oracle's methodology for building security into the design, build, is used during the entire product testing, delivery, and maintenance of its products. Oracle's goal is to ensure that development cycle. This type of analysis works very well for identifying Oracle's products, as well as the customer systems that leverage those products, buffer overflows and memory leaks in remain as secure as possible. C/C++ code, resource handling issues Secure Coding Standards in J2EE and .NET, finding improper Secure software does not happen by itself. It requires consistently applied credentials handling, various injections, incorrect system configurations, etc. methodologies across each organization; methodologies that conform to stated policies, objectives, and principles. D Y N A M I C C O D E ANALYSIS Oracle Secure Coding Standards are a guide for developers in their efforts to produce Dynamic analysis activity always takes secure code.
    [Show full text]