This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP/Training/OWASP Software Assurance Maturity Model"
| Line 21: | Line 21: | ||
| Material = | | Material = | ||
| | ||
| − | *[http://www.owasp.org/images/d/df/OpenSAMM.pdf Software Assurance Maturity Model - | + | * [http://www.owasp.org/images/8/83/OWASP_OpenSAMM.ppt PPT][http://www.owasp.org/images/d/df/OpenSAMM.pdf Software Assurance Maturity Model - PDF] |
*[http://www.opensamm.org/downloads/SAMM-1.0.pdf Software Assurance Maturity Model PDF File] | *[http://www.opensamm.org/downloads/SAMM-1.0.pdf Software Assurance Maturity Model PDF File] | ||
*[http://www.owasp.org/images/d/df/OpenSAMM.pdf Software Assurance Maturity Model PDF File 2] | *[http://www.owasp.org/images/d/df/OpenSAMM.pdf Software Assurance Maturity Model PDF File 2] | ||
}} | }} | ||
Revision as of 13:16, 16 April 2010
| MODULE | |
| OWASP Software Assurance Maturity Model | |
| Overview & Goal | |
| SAMM is an open framework that helps formulate and implement a strategy for software security. The main drivers for SAMM is, an organization’s behavior changes slowly over time. It is based on princliple that somebody has to learn to walk first before they can run. That is the reason changes has to be iterative while working toward long-term goals. There is no single recipe that works for all organizations. A solution must provide enough details for non-security-people. Overall, must be simple, well-defined, and measurable. | |
| Contents | Materials |
|
SAMM can help an organization evaluate existing software security practices and build a balanced software security assurance program in well-defined iterations. It can demonstrate concrete improvements to a security assurance program. It can also help in defining and measuring security-related activities. At the highest level, SAMM defines four critical Business Functions:
Each Business Function is the nuts-and-bolts of software development. For each Business Function, SAMM defines three Security Practices. So overall, there are twelve Security Practices that will help an organization build secure applications.
|
|
