<HTML dir=ltr><HEAD><TITLE>Re: [Dataloss] rant: Abandon Ship! Data Loss Ahoy!</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText52770 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Something I haven't seen in this thread is...</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Many companies give either consultants or manufacturers loads of money to 'secure' them or 'verify' that they are secure. being a consultant myself I've seen this all too often. </FONT><FONT face=Arial size=2>This (obviously) does little to actually secure anything!</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>To properly secure something companies must create a culture of security - starting with solid policies that are more than pieces of paper that sit in a book until the auditor needs them.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Only with these policies that define the who, what, when, where, why, and how can good controls be put into place that support those policies.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Any old fool can purchase a firewall and put it on the network - but I could tell you stories of how many I've come across with the old Any/Any rule because of lack of proper policies.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>And then companies like Qualys... I think they offer a great service - but too many companies think that just because they use that service that they are secure. Qualys does NOTHING but offer information. How a company uses that information, if at all, is up to the company!</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Me personally? I'd take security out of the hands of the IT department! Give it to a non-IT CSO who is dedicated to developing that culture of security with the proper policies to back it up. With that, proper guidance can be passed on to the IT department to deploy the controls necessary to support them.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Tracy Blackmore, CISSP</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Independent Consultant</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>T.S. Lad, Inc.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2><A href="http://www.tslad.com">www.tslad.com</A></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> dataloss-bounces@attrition.org on behalf of James Ritchie, CISA, QSA<BR><B>Sent:</B> Thu 3/20/2008 1:44 PM<BR><B>To:</B> dataloss@attrition.org<BR><B>Subject:</B> Re: [Dataloss] rant: Abandon Ship! Data Loss Ahoy!<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Being compliant does not mean being secure and being secure does not<BR>mean being compliant. What most people forget with all the compliance<BR>is that constant vigilance must be maintained. Does that mean daily,<BR>weekly, monthly, quarterly, or annually that you have to verify that the<BR>controls are working appropriately? What I think will be the outcome is<BR>if appropriate due diligence and due care can be shown as fact, the<BR>liability will be reduced or eliminated. They will compare the actions<BR>taken and of similar size companies to see if what they had done was<BR>appropriate. To make any company 100% secure, the cost of security would<BR>be so prohibited, the company would be bankrupt. There has to be a<BR>balance and reasonable effort shown.<BR><BR>Adam Shostack wrote:<BR>> On Thu, Mar 20, 2008 at 10:13:08AM -0500, Allan Friedman wrote:<BR>> | > On the public policy issue, I agree. If you want companies to disclose<BR>> | > the exact circumstances around a breach (exact technical details), there<BR>> | > will have to be a shield that prevents plaintiffs attorney's from using<BR>> | > the information in lawsuits.<BR>> |<BR>> | You highlight an interesting trade-off. It may be the case that more<BR>> | disclosure would reduce incentives to prevent future breaches,<BR>> | depending on how we understand the problem.<BR>> |<BR>> | A standard policy tool for enforcing maximum diligence is the threat<BR>> | of lawsuits, massive ones that can wreck a corporation. If we follow<BR>> | this liability argument (as advanced by Schneier and other scholars of<BR>> | the economics of information security) then making concessions to<BR>> | corporate defendants can impede the end goal of less data retention<BR>> | and greater data protection.<BR>> |<BR>> | If we don't think we're ever going to get there, then more data about<BR>> | breaches for the purposes of research is clearly the greater good.<BR>> | This is a very interesting dynamic. I'll have to think about how to<BR>> | model it...<BR>><BR>> For this policy to be effective, costs must be aligned with a failure<BR>> to take effective measures. Today, we lack the data to asses how<BR>> effective various 'best practices' or standards are. Gene Kim and<BR>> company have done work showing that a few part of COBIT are key, and<BR>> others are not correlated with they outcomes they studied. (There's a<BR>> CERIAS talk video you can find.) There's claims that Hannaford was<BR>> PCI complaint. Shouldn't that have made them secure?<BR>><BR>> So lawsuits today are random. With better data, we may be able to<BR>> better attribute blame. Perhaps this shapes a temporary liability<BR>> shield, with a goal of revisiting it later, or allowing case law to<BR>> shape it for a while?<BR>><BR>> Adam<BR>><BR>> _______________________________________________<BR>> Dataloss Mailing List (dataloss@attrition.org)<BR>> <A href="http://attrition.org/dataloss">http://attrition.org/dataloss</A><BR>><BR>> Tenable Network Security offers data leakage and compliance monitoring<BR>> solutions for large and small networks. Scan your network and monitor your<BR>> traffic to find the data needing protection before it leaks out!<BR>> <A href="http://www.tenablesecurity.com/products/compliance.shtml">http://www.tenablesecurity.com/products/compliance.shtml</A><BR>><BR>> <BR><BR>--<BR>James Ritchie<BR>CISA, PCI-QSA, ASV, MCSE, MCP+I, M-CIW-D, CIW-CI, Inet+, Network+, A+<BR><BR>Linkedin <A href="http://www.linkedin.com/pub/1/b89/433">http://www.linkedin.com/pub/1/b89/433</A><BR><BR>Attachments with this email, not explicitly referenced, should not be opened. Always scan your email and their associated attachments for viruses prior to opening.<BR><BR>This message and any accompanying documents are confidential and may contain information covered under the Privacy Act, 5 USC 552(a), the Health Insurance Portability and Accountability Act (PL 104-191), or the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and its various implementing regulations and must be protected in accordance with those provisions. Unauthorized disclosure or failure to maintain the confidentiality of the information may result in civil or criminal sanctions. <BR><BR>This e-mail is strictly confidential and intended solely for the addressee. Should you not be the intended addressee you have no right to any information contained in this e-mail. If you received this message by mistake you are kindly requested to inform us of this and to destroy the message.<BR><BR>_______________________________________________<BR>Dataloss Mailing List (dataloss@attrition.org)<BR><A href="http://attrition.org/dataloss">http://attrition.org/dataloss</A><BR><BR>Tenable Network Security offers data leakage and compliance monitoring<BR>solutions for large and small networks. Scan your network and monitor your<BR>traffic to find the data needing protection before it leaks out!<BR><A href="http://www.tenablesecurity.com/products/compliance.shtml">http://www.tenablesecurity.com/products/compliance.shtml</A><BR></FONT></P></DIV></BODY></HTML>