<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: What Do We Mean by “Reasonable Controls?”</title>
	<atom:link href="http://securityblog.verizonbusiness.com/2008/06/19/reasonable-controls/feed/" rel="self" type="application/rss+xml" />
	<link>http://securityblog.verizonbusiness.com/2008/06/19/reasonable-controls/</link>
	<description>Risk Intelligence from Verizon Business Security Solutions powered by Cybertrust</description>
	<pubDate>Wed, 03 Dec 2008 21:52:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>By: Russ Cooper</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/19/reasonable-controls/#comment-17</link>
		<dc:creator>Russ Cooper</dc:creator>
		<pubDate>Wed, 25 Jun 2008 20:26:35 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=117#comment-17</guid>
		<description>Ben, we think that your use of the word "conventional" could be seen to be just as subjective as our use of "reasonable controls." It may very well carry a different meaning for you, the reader, and us.  We don't necessarily think conventional opinion is irrational.  Error was a factor in 62% of our caseload. We think the majority had defined a policy, based on conventional thinking, but they simply hadn't implemented it, or implemented it contrary to their own policy.
 
As you say, Ben, "The cost of locking down data includes much more than merely correcting particular mistakes." We don't disagree.  However, our data shows that eliminating error significantly reduces risk.  We believe in many cases one single defensive action can significantly reduce risk, and there are certainly instances where a handful of simple, inexpensive controls can reduce almost all significant risks.  There is a point at which implementing more does not achieve equivalent, or even significant, risk reduction. One cannot argue that doing what you have defined in your own policy is a "bad thing," only, possibly, that your policy need not be as elaborate as you may have it.
 
I'm sure we agree there are operational costs for any network, and I think we agree those costs include "vigilance, equipment upgrades, employee training, auditing, etc.  They may also possibly include "policing of business partners,” and definitely de-provisioning of network connections, etc. I'd hope you'd also agree characterizing them as purely security costs is too narrow in the extreme, versus reasonable network operational costs.  Whoops, there goes that word "reasonable" again! 
 
We're also not suggesting that myriad attack paths be "locked down."  Our risk-based approach considers paths of least resistance and greatest availability (i.e., areas of greatest risk).  Our study data shows opportunistic attacks of low skill level can be extremely successful.  Such attacks remain successful because the cost of attack is relatively low for the criminal.  We believe in implementing controls to the point an organization is no longer a target of opportunity (they become a target of choice). This doesn't mean the organization has plugged every hole, but it does mean they have made the cost of attack for the criminal higher than for other potential targets.
 
As you suggest, it is conceivable that the cost of attack could be increased by factors other than the implementation of internal controls. There may well be value, for instance, in making data less desirable or valuable to the criminal. Unfortunately, most organizations simply do not have the capacity to accomplish this, much less influence external changes on a scale comparable to the suggested revamp of the credit card system. It's hard to argue against such ideas. In the meantime, however, there remains a need for organizations to implement effective and efficient measures of securing the environment over which they have control.</description>
		<content:encoded><![CDATA[<p>Ben, we think that your use of the word &#8220;conventional&#8221; could be seen to be just as subjective as our use of &#8220;reasonable controls.&#8221; It may very well carry a different meaning for you, the reader, and us.  We don&#8217;t necessarily think conventional opinion is irrational.  Error was a factor in 62% of our caseload. We think the majority had defined a policy, based on conventional thinking, but they simply hadn&#8217;t implemented it, or implemented it contrary to their own policy.</p>
<p>As you say, Ben, &#8220;The cost of locking down data includes much more than merely correcting particular mistakes.&#8221; We don&#8217;t disagree.  However, our data shows that eliminating error significantly reduces risk.  We believe in many cases one single defensive action can significantly reduce risk, and there are certainly instances where a handful of simple, inexpensive controls can reduce almost all significant risks.  There is a point at which implementing more does not achieve equivalent, or even significant, risk reduction. One cannot argue that doing what you have defined in your own policy is a &#8220;bad thing,&#8221; only, possibly, that your policy need not be as elaborate as you may have it.</p>
<p>I&#8217;m sure we agree there are operational costs for any network, and I think we agree those costs include &#8220;vigilance, equipment upgrades, employee training, auditing, etc.  They may also possibly include &#8220;policing of business partners,” and definitely de-provisioning of network connections, etc. I&#8217;d hope you&#8217;d also agree characterizing them as purely security costs is too narrow in the extreme, versus reasonable network operational costs.  Whoops, there goes that word &#8220;reasonable&#8221; again! </p>
<p>We&#8217;re also not suggesting that myriad attack paths be &#8220;locked down.&#8221;  Our risk-based approach considers paths of least resistance and greatest availability (i.e., areas of greatest risk).  Our study data shows opportunistic attacks of low skill level can be extremely successful.  Such attacks remain successful because the cost of attack is relatively low for the criminal.  We believe in implementing controls to the point an organization is no longer a target of opportunity (they become a target of choice). This doesn&#8217;t mean the organization has plugged every hole, but it does mean they have made the cost of attack for the criminal higher than for other potential targets.</p>
<p>As you suggest, it is conceivable that the cost of attack could be increased by factors other than the implementation of internal controls. There may well be value, for instance, in making data less desirable or valuable to the criminal. Unfortunately, most organizations simply do not have the capacity to accomplish this, much less influence external changes on a scale comparable to the suggested revamp of the credit card system. It&#8217;s hard to argue against such ideas. In the meantime, however, there remains a need for organizations to implement effective and efficient measures of securing the environment over which they have control.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: benjaminwright</title>
		<link>http://securityblog.verizonbusiness.com/2008/06/19/reasonable-controls/#comment-13</link>
		<dc:creator>benjaminwright</dc:creator>
		<pubDate>Sun, 22 Jun 2008 14:17:08 +0000</pubDate>
		<guid isPermaLink="false">http://securityblog.verizonbusiness.com/?p=117#comment-13</guid>
		<description>Learned Friends at Verizon Business Security:   Reasonable security implies a cost/benefit analysis.  Conventional opinion irrationally assumes the benefit of preventing unauthorized access to data is always high.  Conventional thinking  ignores alternatives, such as: 1.  Maybe compensating external controls make it unlikely a particular breach will amount to anything important (even though the breach would sound bad if reported in the media).  2.  Maybe the credit card system as a whole needs to change so criminals who steal little units of data can’t use them.  

The cost of locking down data includes much more than merely correcting particular mistakes (e.g., retaining default usernames) that become obvious after an investigator conducts a postmortem on an incident.  The true costs include all the vigilance, equipment upgrades, employee training, auditing, policing of business partners, deprovisioning of network connections and on, and on and on that must be performed prospectively, constantly, repetitively, to prevent a breach from happening in any of the myriad ways it can happen.  –Ben
&lt;a href="//hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html”" rel="nofollow"&gt;http://hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Learned Friends at Verizon Business Security:   Reasonable security implies a cost/benefit analysis.  Conventional opinion irrationally assumes the benefit of preventing unauthorized access to data is always high.  Conventional thinking  ignores alternatives, such as: 1.  Maybe compensating external controls make it unlikely a particular breach will amount to anything important (even though the breach would sound bad if reported in the media).  2.  Maybe the credit card system as a whole needs to change so criminals who steal little units of data can’t use them.  </p>
<p>The cost of locking down data includes much more than merely correcting particular mistakes (e.g., retaining default usernames) that become obvious after an investigator conducts a postmortem on an incident.  The true costs include all the vigilance, equipment upgrades, employee training, auditing, policing of business partners, deprovisioning of network connections and on, and on and on that must be performed prospectively, constantly, repetitively, to prevent a breach from happening in any of the myriad ways it can happen.  –Ben<br />
<a href="//hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html”" rel="nofollow">http://hack-igations.blogspot.com/2007/12/does-lost-tape-equate-to-lost-data.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
