SSDF
Prepare the Organization
Secure development begins with clear responsibilities and a delivery environment that supports them. Preparation aligns development, security, operations and product leadership on the practices, tools, skills and release expectations that the team will actually follow.
How the work is approached
- Assign secure-development roles and decision responsibilities
- Define training, toolchain protections and security requirements
- Set review checkpoints and criteria for handling exceptions
Teams know which security activities belong in delivery and who is accountable. Preparation produces working practices that can be applied consistently across projects, rather than a policy that engineers cannot implement. The review should retain development responsibility matrix so the team can explain the decisions later.
Useful starting information
- Development roles and existing procedures
- Repository and build environment inventory
- Customer requirements and release expectations
Outputs to agree and review
- Development responsibility matrix
- Secure-development practices and training plan
- Toolchain and checkpoint requirements
A practical example
A small software team introduces peer review and a defined security exception process. Preparation identifies who can approve exceptions, what must be recorded and which checks still block a release.
What to watch for
Tool purchases do not replace ownership, training or review criteria. Start with a workflow the team can operate.
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 Prepare the Organization worksheet (CSV)Continue within this service
Framework reference
NIST SSDF publication. Use the baseline and direction applicable to your environment and engagement.
