File:ISC2 SecureSDLC OWASP Achieving Compliance v1.0 2012-05-04.pptx

From OWASP
Jump to: navigation, search
ISC2_SecureSDLC_OWASP_Achieving_Compliance_v1.0_2012-05-04.pptx(file size: 1.45 MB, MIME type: application/vnd.openxmlformats-officedocument.presentationml.presentation)
Warning: This file type may contain malicious code. By executing it, your system may be compromised.

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/TimeDimensionsUserComment
current08: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.

There are no pages that link to this file.