You don't have access to this class

Keep learning! Join and start boosting your career

Aprovecha el precio especial y haz tu profesión a prueba de IA

Antes: $249

Currency
$209
Suscríbete

Termina en:

1 Días
14 Hrs
8 Min
11 Seg

Modelo de Madurez para el Aseguramiento del Software

16/19
Resources

What is the OWASP SAM model and why is it essential for secure software development?

The OWASP SAM (Software Assurance Maturity Model) is a comprehensive approach that will allow you not only to develop software securely, but also to assess the security of the applications you acquire. This model focuses on maturing security practices in five business functions: governance, design, implementation, verification and operations. Consider this as a compass that guides the way to robust and secure software.

How does OWASP SAM relate to the Top 10?

While the OWASP Top 10 is a well-known benchmark for the most critical application security risks, OWASP SAM takes that knowledge a step further. Rather than just identifying risks, SAM offers a structured methodology for assessing and improving those areas through a progressive maturity model. This model allows realistic and measurable goals to be set within each business function, providing a clear framework for safe development.

How to improve design and security practices with OWASP SAM?

When applying OWASP SAM in software design, it is crucial to perform threat assessments to identify explicit risks to applications under development. This involves understanding the stakeholders and their motivations, as well as defining specific security requirements. For example, following this analysis, you might determine the need to implement specific encryption to protect sensitive data. This approach ensures that security measures are not just reactive, but integral from the software's conception.

How to apply OWASP SAM in practice?

One of the great benefits of OWASP SAM is the ability to adapt its application depending on the current maturity level of your organization.

What does continuous verification involve in the SAM model?

Verification is fundamental to the SAM model. In early stages, it is recommended to incorporate security testing before releasing the software to production. As a higher level of maturity is reached, this testing is integrated into the ongoing development of the product with techniques such as static and dynamic testing. This approach ensures that security is an inherent part of the software lifecycle.

How to use the OWASP SAM tool to measure maturity?

OWASP SAM provides tools, such as a toolbox for Excel or Google Sheets, that make it easy to assess the current security maturity level of your practices. This process starts with an interview where you are asked about your current practices and classified according to three maturity levels. You can then visualize your current status on a radar chart, allowing you to identify areas for improvement and create a realistic action plan to advance the maturity of your security practices.

What role does the business model play in security maturity?

It is crucial to adapt the SAM model to the characteristics of each organization. For example, a software company might not require the same level of compliance as one in the financial or healthcare sector. Therefore, the phases of the model should be customizable according to the needs and priorities of the business, which helps to define the speed and target level of maturity.

How to get the most out of OWASP SAM?

To maximize the benefits of OWASP SAM, it is vital to embark on an initial exercise to tailor the recommendations to the specific conditions and needs of the organization. This process will allow you to experiment and, over time, adjust security practices, thus ensuring continuous improvement in the development and acquisition of secure software.

OWASP SAM is not just a checklist, but a powerful tool for integrating effective security practices, promoting a more secure and robust development environment. Remember that in the world of software development, the race to security has no end goal, but every step you take will bring you closer to excellence.

Contributions 6

Questions 0

Sort by:

Want to see more contributions, questions and answers from the community?

OWASP SAMM - Software Assurance Maturity Model Evaluar el software que se desarrolla o adquiere. Es una serie de funciones de negocio: 1. Gobernanza. 2. Diseño. 3. Implantación. 4. Verificación. 5. Operaciones. Se ponen metas sobre objetivos en las prácticas de seguridad. Entender el estado actual para → Definir a dónde se quiere ir. La velocidad de maduración dependerá de cada negocio. No hay una dirección estándar para los cambios en cada una de las funciones.
**OWASP SAMM** es un marco de trabajo de código abierto desarrollado por la Open Web Application Security Project (OWASP) para ayudar a las organizaciones a **evaluar y mejorar su postura de seguridad de software**. Este utiliza un modelo de madurez que se divide en **cinco niveles**: * **Nivel 1 - Inicial:** Las prácticas de seguridad de software son ad-hoc e informales. * **Nivel 2 - Repetible:** Se han establecido algunas prácticas básicas de seguridad de software, pero aún no se han formalizado. * **Nivel 3 - Definido:** Se han definido y documentado las prácticas de seguridad de software, pero la implementación puede no ser coherente. * **Nivel 4 - Gestionado:** Las prácticas de seguridad de software se gestionan activamente y se miden. * **Nivel 5 - Optimizado:** Las prácticas de seguridad de software se optimizan continuamente para mejorar la eficacia general.

Imagino que como el curso es nuevo, se fueron algunos detalles. En la sección de recursos no hay enlaces, ni archivos comentados por el docente. Espero avisen cuando los carguen.

Gracias !

No logré descargar el toolkit. Indica que el archivo ya no esta disponible. Saludos.
![](https://static.platzi.com/media/user_upload/image-650da25b-916d-4133-a6a9-e26347359f5a.jpg)