Difference between revisions of "Category:Software Assurance Maturity Model"
m (→SAMM Community)
|(One intermediate revision by the same user not shown)|
|Line 83:||Line 83:|
= SAMM Community =
= SAMM Community =
= Project =
= Project =
Revision as of 09:26, 24 July 2013
| For the latest project news and information,|
join the mailing list and visit the OpenSAMM website.
OWASP.org is a valuable resource for any company involved with online payment card transactions. Dell uses OWASP’s Software Assurance Maturity Model (OpenSAMM) to help focus our resources and determine which components of our secure application development program to prioritize. Participation in OWASP’s local chapter meetings and conferences around the globe helps us build stronger networks with our colleagues. , (Michael J. Craigue, Information Security & Compliance, Dell, Inc.)
The Software Assurance Maturity Model (SAMM) is an open framework to help organizations formulate and implement a strategy for software security that is tailored to the specific risks facing the organization. The resources provided by SAMM will aid in:
- Evaluating an organization’s existing software security practices
- Building a balanced software security assurance program in well-defined iterations
- Demonstrating concrete improvements to a security assurance program
- Defining and measuring security-related activities throughout an organization
SAMM was defined with flexibility in mind such that it can be utilized by small, medium, and large organizations using any style of development. Additionally, this model can be applied organization-wide, for a single line-of-business, or even for an individual project. Beyond these traits, SAMM was built on the following principles:
- An organization’s behavior changes slowly over time - A successful software security program should be specified in small iterations that deliver tangible assurance gains while incrementally working toward long-term goals.
- There is no single recipe that works for all organizations - A software security framework must be flexible and allow organizations to tailor their choices based on their risk tolerance and the way in which they build and use software.
- Guidance related to security activities must be prescriptive - All the steps in building and assessing an assurance program should be simple, well-defined, and measurable. This model also provides roadmap templates for common types of organizations.
The foundation of the model is built upon the core business functions of software development with security practices tied to each (see diagram below). The building blocks of the model are the three maturity levels defined for each of the twelve security practices. These define a wide variety of activities in which an organization could engage to reduce security risks and increase software assurance. Additional details are included to measure successful activity performance, understand the associated assurance benefits, estimate personnel and other costs.
|Project Name||Software Assurance Maturity Model (SAMM) Project|
|Short Project Description||
The Software Assurance Maturity Model (SAMM) project is committed to building a usable framework to help organizations formulate and implement a strategy for application security that's tailored to the specific business risks facing the organization. The goal is to create well-defined and measurable goals that can be used by small, medium,and large sized organizations in any line of business that involves software development.
Key Project Information
|Release Status||Main Links||Related Projects|
Project Activities 2013
Is available via this link
Project meeting minutes:
Download the latest OpenSAMM presentation (was presented by Seba at the Geneva chapter meeting on 25-June-2013) here
| This project has produced a book that can be downloaded or purchased.|
Feel free to browse the full catalog of available OWASP books.
Pages in category "Software Assurance Maturity Model"
The following 48 pages are in this category, out of 48 total.
- SAMM - Code Review - 1
- SAMM - Code Review - 2
- SAMM - Code Review - 3
- SAMM - Construction
- SAMM - Deployment
- SAMM - Design Review - 1
- SAMM - Design Review - 2
- SAMM - Design Review - 3
- SAMM - Education & Guidance - 1
- SAMM - Education & Guidance - 2
- SAMM - Education & Guidance - 3
- SAMM - Environment Hardening - 1
- SAMM - Environment Hardening - 2
- SAMM - Environment Hardening - 3
- SAMM - Governance
- SAMM - Operational Enablement - 1
- SAMM - Operational Enablement - 2
- SAMM - Operational Enablement - 3
- SAMM - Policy & Compliance - 1
- SAMM - Policy & Compliance - 2
- SAMM - Policy & Compliance - 3
- SAMM - Roadmap - Financial Services Organization
- SAMM - Roadmap - Government Organization
- SAMM - Roadmap - Independent Software Vendor
- SAMM - Roadmap - Online Service Provider
- SAMM - Secure Architecture - 1
- SAMM - Secure Architecture - 2
- SAMM - Secure Architecture - 3
- SAMM - Security Requirements - 1
- SAMM - Security Requirements - 2
- SAMM - Security Requirements - 3
- SAMM - Security Testing - 1
- SAMM - Security Testing - 2
- SAMM - Security Testing - 3
- SAMM - Strategy & Metrics - 1
- SAMM - Strategy & Metrics - 2
- SAMM - Strategy & Metrics - 3
- SAMM - Threat Assessment - 1
- SAMM - Threat Assessment - 2
- SAMM - Threat Assessment - 3
- SAMM - Verification
- SAMM - Vulnerability Management - 1
- SAMM - Vulnerability Management - 2
- SAMM - Vulnerability Management - 3