Secure SDLC Cheat Sheet - Revision history

Dominique RIGHETTO: Migration to GitHub of the project

2019-02-16T10:21:15Z

Migration to GitHub of the project

Dominique RIGHETTO: Add the DELETE marker. Refer to CS cleanup phase

2018-08-25T09:23:09Z

Add the DELETE marker. Refer to CS cleanup phase

David Taylor: Updated a broken link

2018-05-28T03:39:29Z

Updated a broken link

Dinis.cruz: added link to project

2016-10-08T16:35:23Z

added link to project

Michaelbester: /* How to Apply */

2015-11-09T15:25:21Z

‎How to Apply

Michaelbester: /* Background */

2015-11-09T15:24:21Z

‎Background

Michaelbester at 18:00, 2 November 2015

2015-11-02T18:00:32Z

Michaelbester: Made changes as per OPENSAMM v1.1 Quick Start guide.

2015-11-02T18:00:05Z

Made changes as per OPENSAMM v1.1 Quick Start guide.

Show changes

Michaelbester: /* Introduction */

2015-11-02T17:18:49Z

‎Introduction

Michaelbester: /* Introduction */

2015-10-05T11:48:02Z

‎Introduction

@@ Line 1: / Line 1: @@
-= DRAFT CHEAT SHEET - WORK IN PROGRESS =
+ __NOTOC__
-= Background =
+The Cheat Sheet Series project has been moved to [https://github.com/OWASP/CheatSheetSeries GitHub]!
-This cheat sheet provides a quick reference on the most important initiatives to build security into multiple parts of software development processes. This cheat sheet is based on the OWASP Software Assurance Maturity Model ([[OWASP_SAMM_Project|SAMM]]) which can be integrated into any existing SDLC.
+An [https://github.com/OWASP/CheatSheetSeries/issues/13 open discussion] is pending about to exclude or not this cheat sheet of the V2 of the project.

← Older revision		Revision as of 09:23, 25 August 2018
Line 135:		Line 135:

	[[Category:Cheatsheets]] [[Category:OWASP_Builders]]		[[Category:Cheatsheets]] [[Category:OWASP_Builders]]
		+
		+	{{taggedDocument\| type=delete\| comment=Tagged via fixme/delete.}}

@@ Line 65: / Line 65: @@
 Online Self Assessment Tool
-https://ssa.asteriskinfosec.com.au
+https://github.com/AsteriskLabs/ssa
 Both of these resources provide you with:

@@ Line 3: / Line 3: @@
 = Background =
-This cheat sheet provides a quick reference on the most important initiatives to build security into multiple parts of software development processes. This cheat sheet is based on the OWASP Software Assurance Maturity Model (SAMM) which can be integrated into any existing SDLC.
+This cheat sheet provides a quick reference on the most important initiatives to build security into multiple parts of software development processes. This cheat sheet is based on the OWASP Software Assurance Maturity Model ([[OWASP_SAMM_Project|SAMM]]) which can be integrated into any existing SDLC.
 SAMM is based around a set of 12 security practices, which are grouped into 4 business functions. Every security practice contains a set of activities, structured into 3 maturity levels. The activities on a lower maturity level are typically easier to execute and require less formalization than the ones on a higher maturity level.

@@ Line 32: / Line 32: @@
 '''Identify Stakeholders'''
 Ensure that important stakeholders supposed to support and execute the project are identified and well aligned
 '''Spread the word'''
 Inform people about the initiative and provide them with information to understand what you will be doing
 | '''Consider involving at least:'''

@@ Line 7: / Line 7: @@
 SAMM is based around a set of 12 security practices, which are grouped into 4 business functions. Every security practice contains a set of activities, structured into 3 maturity levels. The activities on a lower maturity level are typically easier to execute and require less formalization than the ones on a higher maturity level.
-The structure and setup of the '''SAMM maturity model''' are made to support (i) the '''assessment''' of the current software assurance posture, (ii) the definition of the '''strategy''' (i.e. the target) that the organization should take, (iii) the formulation of an implementation '''roadmap''' of how to get there and (iv) prescriptive advice on how to '''implement''' particular activities.
+The structure and setup of the '''SAMM maturity model''' are made to support:
+# The '''assessment''' of the current software assurance posture
-In that sense, the value of SAMM lies in providing a means to know where your organization is on its journey towards software assurance, and to understand what is recommended to move to a next level of maturity. Note that SAMM does not insist that all organizations achieve maturity level 3 in every category. Indeed, you determine the target maturity level for each Security Practice that is the best fit for your organization and its needs. SAMM provides a number of templates for typical organizations to this end, but you can adapt these as you see fit.
+# The definition of the '''strategy''' (i.e. the target) that the organization should take
 = How to Apply =

@@ Line 124: / Line 124: @@
 The best way to grasp SAMM is to start using it. This document has presented a number of concrete steps and supportive material to execute these. Now it’s your turn. We warmly invite you to spend a day or two on following  the first steps, and you will quickly understand and appreciate the added value of the model. Enjoy! Suggestions for improvements are very welcome. And if you’re interested, consider to join the mailinglist or become part of the OpenSAMM community
 {{Cheatsheet_Navigation}}
 [[Category:Cheatsheets]] [[Category:OWASP_Builders]]

@@ Line 3: / Line 3: @@
 = Introduction =
-This cheat sheet provides an "at a glance" quick reference on the most important initiatives to build security into multiple parts of software development processes. They broadly relate to "level 1" of the Open Software Assurance Maturity Model (Open SAMM).
+This cheat sheet provides an "at a glance" quick reference on the most important initiatives to build security into multiple parts of software development processes. This cheat sheet is based on the OWASP Software Assurance Maturity Model (SAMM) which can be integrated into any existing SDLC.
 = Purpose =