SSDF
Produce Well-Secured Software
Producing well-secured software means applying security thinking during design, implementation, review and testing. The work combines sound engineering with checks suited to the software’s architecture, dependencies and operating environment.
How the work is approached
- Identify abuse cases and security requirements during design
- Review changes, dependencies and security-sensitive implementation choices
- Test relevant behavior and disposition findings before release
Security findings enter the same accountable delivery process as other engineering work. Evidence shows which practices were applied, what was found and how release decisions were made. The review should retain design and code-review records so the team can explain the decisions later.
Useful starting information
- Software architecture and feature requirements
- Code, dependencies and review practices
- Testing approach and known weaknesses
Outputs to agree and review
- Design and code-review records
- Security test and dependency findings
- Remediation and release-decision evidence
A practical example
A new file-upload feature is reviewed for authorization, accepted formats, size limits and unsafe content handling. Tests exercise both expected use and abuse cases before the feature is released.
What to watch for
Passing a scanner does not establish that the design is safe. Include human review and tests for the application’s specific trust boundaries.
Scope, ownership and acceptance criteria should be agreed for the actual environment. The example describes a planning approach, not a promised result or a determination of compliance.
Planning worksheet
Use this short worksheet to record your starting information, action owners and evidence locations before a detailed review.
Download the Produce Well-Secured Software worksheet (CSV)Continue within this service
Framework reference
NIST SSDF publication. Use the baseline and direction applicable to your environment and engagement.
