Secure Coding mailing list archives
Information Protection Policies
From: James.McGovern at thehartford.com (McGovern, James F (HTSC, IT))
Date: Fri, 9 Mar 2007 17:27:07 -0500
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? -----Original Message----- From: sc-l-bounces at securecoding.org [mailto:sc-l-bounces at securecoding.org]On Behalf Of McGovern, James F (HTSC, IT) Sent: Thursday, March 08, 2007 11:17 AM To: SC-L at securecoding.org Subject: [SC-L] Information Protection Policies Hopefully lots of the consultants on this list have been wildly successful in getting Fortune enterprises to embrace secure coding practices. I am curious to learn of those who have also been successful in getting these same Fortune enterprises to incorporate the notion of secure coding practices into an information protection policy and whether there are any publicly available examples. ************************************************************************* 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. *************************************************************************
Current thread:
- Information Protection Policies McGovern, James F (HTSC, IT) (Mar 08)
- Information Protection Policies McGovern, James F (HTSC, IT) (Mar 09)
- Information Protection Policies Steven M. Christey (Mar 10)
- Information Protection Policies Kenneth Van Wyk (Mar 13)
- <Possible follow-ups>
- Information Protection Policies Gary McGraw (Mar 13)
- Information Protection Policies McGovern, James F (HTSC, IT) (Mar 09)