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 "File:ISC2 SecureSDLC OWASP Achieving Compliance v1.0 2012-05-04.pptx"
Deleted user (talk | contribs) m |
Deleted user (talk | contribs) m |
||
| Line 1: | Line 1: | ||
Secure software development compliance requirements are becoming increasingly commonplace in enterprise software development contracts. Software assurance professional Mike Boberski discusses his recommendations for getting started working on both technical and process-related secure software development compliance requirements using the OWASP Top Ten and OpenSAMM as examples. Agile and iterative software development methodologies in particular are generally seen as being at odds with building security into enterprise applications during development. However, by looking at and working the problem from certain different angles, it turns out that secure software development compliance requirements can in fact be approached by developers in a familiar manner in order to achieve and maintain compliance. | Secure software development compliance requirements are becoming increasingly commonplace in enterprise software development contracts. Software assurance professional Mike Boberski discusses his recommendations for getting started working on both technical and process-related secure software development compliance requirements using the OWASP Top Ten and OpenSAMM as examples. Agile and iterative software development methodologies in particular are generally seen as being at odds with building security into enterprise applications during development. However, by looking at and working the problem from certain different angles, it turns out that secure software development compliance requirements can in fact be approached by developers in a familiar manner in order to achieve and maintain compliance. | ||
[[Category:OWASP Presentations]] | [[Category:OWASP Presentations]] | ||
| + | [[Category:OWASP Top Ten Project]] | ||
| + | [[Category:Software Assurance Maturity Model]] | ||
Latest revision as of 13:46, 17 May 2012
Secure software development compliance requirements are becoming increasingly commonplace in enterprise software development contracts. Software assurance professional Mike Boberski discusses his recommendations for getting started working on both technical and process-related secure software development compliance requirements using the OWASP Top Ten and OpenSAMM as examples. Agile and iterative software development methodologies in particular are generally seen as being at odds with building security into enterprise applications during development. However, by looking at and working the problem from certain different angles, it turns out that secure software development compliance requirements can in fact be approached by developers in a familiar manner in order to achieve and maintain compliance.
File history
Click on a date/time to view the file as it appeared at that time.
| Date/Time | Dimensions | User | Comment | |
|---|---|---|---|---|
| current | 13:44, 17 May 2012 | (1.45 MB) | Deleted user (talk | contribs) | Secure software development compliance requirements are becoming increasingly commonplace in enterprise software development contracts. Software assurance professional Mike Boberski discusses his recommendations for getting started working on both technic |
- You cannot overwrite this file.
File usage
There are no pages that link to this file.
