There is a text box in "Software Security" about this with some language I 
copied (with permission) from jack danahy of ounce labs.



 -----Original Message-----
From:   Kenneth Van Wyk [mailto:[EMAIL PROTECTED]
Sent:   Tue Mar 13 12:23:16 2007
To:     Secure Coding
Subject:        Re: [SC-L] Information Protection Policies

On Mar 9, 2007, at 5:27 PM, McGovern, James F ((HTSC, IT)) wrote:
> Ken, in terms of a previous response to your posting in terms of  
> getting customers to ask for secure coding practices from vendors,  
> wouldn't it start with figuring out how they could simply cut-and- 
> paste InfoSec policies into their own?

Using someone's "boilerplate" policies as a starting point is great,  
as long as they go beyond just infosec policies and include examples/ 
guidelines for writing contracts for outsourcing software development  
and acquisition.

Steve Christey pointed to OWASP's example at 
index.php/OWASP_Secure_Software_Contract_Annex.  While I haven't  
(yet) looked at this AND while I'm certainly no authority on contract  
writing, I'd bet that this OWASP example will at least provide some  
pretty good food for thought for anyone who is contracting software  

I firmly believe that we as consumers and as a whole, are not doing  
an adequate job at demanding more in the way of software security  
from the software we purchase and outsource.  IMHO, that shouldn't be  
horribly difficult to change in the short- to medium-term.  Better  
contracts and contractor oversight (e.g., independent architectural  
risk analysis, static code analysis, and rigorous security testing)  
should go a long way.  I know I'm over-simplifying things here, but  


Kenneth R. van Wyk
SC-L Moderator
KRvW Associates, LLC

This electronic message transmission contains information that may be
confidential or privileged.  The information contained herein is intended
solely for the recipient and use by any other party is not authorized.  If
you are not the intended recipient (or otherwise authorized to receive this
message by the intended recipient), any disclosure, copying, distribution or
use of the contents of the information is prohibited.  If you have received
this electronic message transmission in error, please contact the sender by
reply email and delete all copies of this message.  Cigital, Inc. accepts no
responsibility for any loss or damage resulting directly or indirectly from
the use of this email or its contents.
Thank You.

Secure Coding mailing list (SC-L)
List information, subscriptions, etc -
List charter available at -
SC-L is hosted and moderated by KRvW Associates, LLC (
as a free, non-commercial service to the software security community.

Reply via email to