A framework to help organizations formulate and implement a strategy for software security tailored to their specific risks.
OWASP SAMM (Software Assurance Maturity Model) is a framework that helps organizations assess, formulate, and implement strategies for software security. It provides a structured approach to building security into software development processes by defining security practices across business functions with measurable maturity levels. The model enables organizations to evaluate their current security posture and create roadmaps for incremental improvement.
Security professionals, development teams, and organizational leaders responsible for implementing and improving software security practices across their development lifecycle.
SAMM offers a flexible, community-driven framework that can be tailored to any organization's specific needs, providing practical guidance rather than rigid requirements. Its maturity model approach allows organizations to start from their current position and make measurable progress toward better software security.
SAMM stands for Software Assurance Maturity Model.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Defines security practices across business functions with clear maturity levels, enabling organizations to measure and track incremental progress systematically.
Provides customizable questionnaires and metrics that allow organizations to evaluate their current security posture objectively, tailored to specific risk profiles.
Maintained by security professionals worldwide, ensuring the model incorporates diverse perspectives and stays updated with evolving best practices.
Offers guided, step-by-step plans for integrating security into the software development lifecycle, helping teams build practical improvement strategies.
The main GitHub repo is archived, leading to potential confusion and outdated documentation for new users, with development shifted to a new organization.
Requires significant organizational effort, expertise, and buy-in to tailor and deploy effectively, making it resource-intensive for smaller teams.
Emphasizes maturity assessment and strategic roadmaps over specific technical controls or automated solutions, which may not suit tool-heavy security approaches.