Information technology — Cybersecurity — Secure software development framework
Introduction: A software development life cycle (SDLC) is a formal or informal methodology for designing, creating, and maintaining software (including code built into hardware). There are many models for SDLCs, including waterfall, spiral, agile, and agile combined with software development and IT operations (DevOps) practices. Regardless of which SDLC model is used, secure software development practices should be integrated throughout it for three reasons: to reduce the number of vulnerabilities in released software, to reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and to address the root causes of vulnerabilities to prevent recurrences. Vulnerabilities include not just bugs caused by coding flaws, but also weaknesses caused by security configuration settings, incorrect trust assumptions, and outdated risk analysis. Most aspects of security can be addressed multiple times within an SDLC, but in general, the earlier in the SDLC that security is addressed, the less effort and cost is ultimately required to achieve the same level of security. This principle, known as shifting left, is critically important regardless of the SDLC model. Shifting left minimizes any technical debt that would require remediating early security flaws late in development or after the software is in production. Shifting left can also result in software with stronger security and resiliency.
Contents:
- Foreword
- Introduction
- Scope
- 4.1 Approach
- 4.2 SSDF Use
- 4.3 The Secure Software Development Framework
- 5.1 Define Security Requirements for Software Development
- 5.1.1 Identify and document security requirements for software development infrastructures
- 5.1.2 Identify and document security requirements for developed software
- 5.1.3 Communicate requirements
- 5.2 Implement Roles and Responsibilities
- 5.2.1 Update role definitions
- 5.2.2 Provide training
- 5.2.3 Obtain and convey management commitment
- 5.3 Implement Supporting Toolchains
- 5.3.1 Specify tools
- 5.3.2 Secure tools and toolchains
- 5.3.3 Configure tools to generate artifacts
- 5.4 Define and Use Criteria for Software Security Checks
- 5.4.1 Define security check criteria
- 5.4.2 Gather and safeguard information for security checks
- 5.5 Implement and Maintain Secure Environments for Software Development
- 5.5.1 Separate and protect environments
- 5.5.2 Secure and harden endpoints
- 6.1 Protect All Forms of Code from Unauthorized Access and Tampering
- 6.1.1 Securely store code
- 6.2 Provide a Mechanism for Verifying Software Release Integrity
- 6.2.1 Share software integrity verification information
- 6.3 Archive and Protect Each Software Release
- 6.3.1 Retain software releases