The Secure Software Development Framework (SSDF), SP 800-218, is a set of fundamental, sound, and secure software development practices based on established secure software development practice documents from organizations such as BSA, OWASP, and SAFECode
Showing 42 controls
PO.1.1
Identify and document all security requirements for the organization’s software development infrastructures and processes, and maintain the requirements over time.
PO.1.2
Identify and document all security requirements for organization-developed software to meet, and maintain the requirements over time.
PO.1.3
Communicate requirements to all third parties who will provide commercial software components to the organization for reuse by the organization’s own software. [Formerly PW.3.1]
PO.2.1
Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as n...
PO.2.2
Provide role-based training for all personnel with responsibilities that contribute to secure development. Periodically review personnel proficiency and role-based training, and update the training as...
PO.2.3
Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development-related roles and responsibilities.
PO.3.1
Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other.
PO.3.2
Follow recommended security practices to deploy, operate, and maintain tools and toolchains.
PO.3.3
Configure tools to generate artifacts of their support of secure software development practices as defined by the organization.
PO.4.1
Define criteria for software security checks and track throughout the SDLC.
PO.4.2
Implement processes, mechanisms, etc. to gather and safeguard the necessary information in support of the criteria.
PO.5.1
Separate and protect each environment involved in software development.
PO.5.2
Secure and harden development endpoints (i.e., endpoints for software designers, developers, testers, builders, etc.) to perform development-related tasks using a risk-based approach.
PW.1.1
Use forms of risk modeling – such as threat modeling, attack modeling, or attack surface mapping – to help assess the security risk for the software.
PW.1.2
Track and maintain the software’s security requirements, risks, and design decisions.
PW.1.3
Where appropriate, build in support for using standardized security features and services (e.g., enabling software to integrate with existing log management, identity management, access control, and v...
PW.2.1
Have 1) a qualified person (or people) who were not involved with the design and/or 2) automated processes instantiated in the toolchain review the software design to confirm and enforce that it meets...
PW.4.1
Acquire and maintain well-secured software components (e.g., software libraries, modules, middleware, frameworks) from commercial, open-source, and other third-party developers for use by the organiza...
PW.4.2
Create and maintain well-secured software components in-house following SDLC processes to meet common internal software development needs that cannot be better met by third-party software components.
PW.4.4
Verify that acquired commercial, open-source, and all other third-party software components comply with the requirements, as defined by the organization, throughout their life cycles.
PW.5.1
Follow all secure coding practices that are appropriate to the development languages and environment to meet the organization’s requirements.
PW.6.1
Use compiler, interpreter, and build tools that offer features to improve executable security.
PW.6.2
Determine which compiler, interpreter, and build tool features should be used and how each should be configured, then implement and use the approved configurations.
PW.7.1
Determine whether code review (a person looks directly at the code to find issues) and/or code analysis (tools are used to find issues in code, either in a fully automated way or in conjunction with a...
PW.7.2
Perform the code review and/or code analysis based on the organization’s secure coding standards, and record and triage all discovered issues and recommended remediations in the development team’s wor...
PW.8.1
Determine whether executable code testing should be performed to find vulnerabilities not identified by previous reviews, analysis, or testing and, if so, which types of testing should be used.
PW.8.2
Scope the testing, design the tests, perform the testing, and document the results, including recording and triaging all discovered issues and recommended remediations in the development team’s workfl...
PW.9.1
Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the securit...
PW.9.2
Implement the default settings (or groups of default settings, if applicable), and document each setting for software administrators.
PS.1.1
Store all forms of code – including source code, executable code, and configuration-as-code – based on the principle of least privilege so that only authorized personnel, tools, services, etc. have a...
PS.2.1
Make software integrity verification information available to software acquirers.
PS.3.1
Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software release.
PS.3.2
Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials [SBOM]).
RV.1.1
Gather information from software acquirers, users, and public sources on potential vulnerabilities in the software and third-party components that the software uses, and investigate all credible repor...
RV.1.2
Review, analyze, and/or test the software’s code to identify or confirm the presence of previously undetected vulnerabilities.
RV.1.3
Have a policy that addresses vulnerability disclosure and remediation, and implement the roles, responsibilities, and processes needed to support that policy.
RV.2.1
Analyze each vulnerability to gather sufficient information about risk to plan its remediation or other risk response.
RV.2.2
Plan and implement risk responses for vulnerabilities.
RV.3.1
Analyze identified vulnerabilities to determine their root causes.
RV.3.2
Analyze the root causes over time to identify patterns, such as a particular secure coding practice not being followed consistently.
RV.3.3
Review the software for similar vulnerabilities to eradicate a class of vulnerabilities, and proactively fix them rather than waiting for external reports.
RV.3.4
Review the SDLC process, and update it if appropriate to prevent (or reduce the likelihood of) the root cause recurring in updates to the software or in new software that is created.