Eoin, I think your take on SAMM is interesting. I think the difference is not to look for evidence but to measure against controls. Auditors use the notion of controls to figure out good vs bad and is less fluid / abstract that simply seeking evidence. I wonder if Pravir or others that thought about expanding SAMM to include audit language.
________________________________ From: owasp-leaders-boun...@lists.owasp.org [mailto:owasp-leaders-boun...@lists.owasp.org] On Behalf Of Eoin Sent: Wednesday, November 04, 2009 11:07 AM To: owasp-lead...@lists.owasp.org Cc: sc-l@securecoding.org Subject: Re: [Owasp-leaders] Question on ISACA Re understanding what secure codeing is: Taking a look at the OWASP development guides and Code review guide is a start: The intro sections cover what a secure SDLC whould look like etc. Looking at SAMM can indicate what is required also by examining the domains and mapping onto the SDLC Re auditing: (it's not just secure coding, its the whole kahuna) Evidence of developer training is a good start Evidence Secure coding guidelines are nice to see, event better if they have a review history (looked used!). A generic secure application development policy could be used which can be linked to technolofy specific guidelines Evidence of review and adherence to them. Evidence of negative testing, negative use cases anti patterns & threat modeling but there is more....... 2009/11/4 McGovern, James F. (eBusiness) <james.mcgov...@thehartford.com> John Morency of Gartner just finished giving a presentation to our IT executives and one of the observations is that IT auditors have zero clue as to how to audit a secure coding practice. IT audit right now is limited to simply looking at "control" documents and viewing things through the lens of "infrastructure". Is there something we as a community should be doing to make auditors smarter? ************************************************************ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************ _______________________________________________ OWASP-Leaders mailing list owasp-lead...@lists.owasp.org https://lists.owasp.org/mailman/listinfo/owasp-leaders -- Eoin Keary OWASP Code Review Guide Lead Author OWASP Ireland Chapter Lead OWASP Global Committee Member (Industry) http://asg.ie/ https://twitter.com/EoinKeary ************************************************************ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************
_______________________________________________ Secure Coding mailing list (SC-L) SC-L@securecoding.org List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l List charter available at - http://www.securecoding.org/list/charter.php SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com) as a free, non-commercial service to the software security community. _______________________________________________
