<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Linus Torvalds: Security a matter of opinion</title>
	<atom:link href="http://www.bloginfosec.com/2007/10/03/linus-torvalds-security-a-matter-of-opinion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloginfosec.com/2007/10/03/linus-torvalds-security-a-matter-of-opinion/</link>
	<description>An Information Security Magazine in a Blog Format</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kenneth F. Belva</title>
		<link>http://www.bloginfosec.com/2007/10/03/linus-torvalds-security-a-matter-of-opinion/comment-page-1/#comment-128</link>
		<dc:creator>Kenneth F. Belva</dc:creator>
		<pubDate>Sat, 13 Oct 2007 12:19:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/2007/10/03/linus-torvalds-security-a-matter-of-opinion/#comment-128</guid>
		<description>Hi Dave,

While there are certainly ways to quantify metrics (see &lt;a href=&quot;http://www.securitymetrics.org&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt; and &lt;a href=&quot;http://www.bloginfosec.com/2006/11/21/improving-your-security-posture-the-citibank-scorecard/&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;), you&#039;re correct that this is generally a problem in today&#039;s environments.

Regarding zero days and standards/practices: one hopes that one has enough layers in place to prevent most zero day attacks: IPS / Firewall / DMZ / *EndPoint* Security would do a very good job of reducing many _generic_ zero day attacks. (Note that while endpoint security is important here and could prevent many 0-day attacks against workstations, this would not be true of of other assets, such as web apps.)

Thanks for reading and for a thoughtful reply.</description>
		<content:encoded><![CDATA[<p>Hi Dave,</p>
<p>While there are certainly ways to quantify metrics (see <a href="http://www.securitymetrics.org" target="_blank" rel="nofollow">here</a> and <a href="http://www.bloginfosec.com/2006/11/21/improving-your-security-posture-the-citibank-scorecard/" target="_blank" rel="nofollow">here</a>), you&#8217;re correct that this is generally a problem in today&#8217;s environments.</p>
<p>Regarding zero days and standards/practices: one hopes that one has enough layers in place to prevent most zero day attacks: IPS / Firewall / DMZ / *EndPoint* Security would do a very good job of reducing many _generic_ zero day attacks. (Note that while endpoint security is important here and could prevent many 0-day attacks against workstations, this would not be true of of other assets, such as web apps.)</p>
<p>Thanks for reading and for a thoughtful reply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Funk</title>
		<link>http://www.bloginfosec.com/2007/10/03/linus-torvalds-security-a-matter-of-opinion/comment-page-1/#comment-127</link>
		<dc:creator>David Funk</dc:creator>
		<pubDate>Thu, 11 Oct 2007 16:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloginfosec.com/2007/10/03/linus-torvalds-security-a-matter-of-opinion/#comment-127</guid>
		<description>I think that I agree with Linus a bit more than you.  In your disagreements:
1) Information Security has known testing methods.
Which are basically broken down into compliance testing, where the linkage to security is indirect at best and insignificant at worst (FISMA); and pen testing, which directly measures results, but we&#039;re a few years away from getting quantitave metrics from results.
2) Information Security has metrics that can be applied to help understand risk.
Problem is, Linus talked about quantification.  Yes todays metrics help to understand risk, but today it requires a priest of Delphi to understand it.  Linus (and I, and my CIO, and a lot of people) would like meaningful, reliable numbers.  The only reliable metric that I know of is &#039;what has been an organization&#039;s history with computer related incidents, and what is that organizations&#039;s environment?&#039;  Obviously the &#039;reliable&#039; part is all bound up in how good that they are watching (assuming that they are telling you the truth!)  The US Army has had some real problems with the Red Army, but they are being actively hacked by a pretty large, well organized, state-sponsored group.  The VA has had some problems, but they operate in a low to moderate threat environment.  I can make conclusions based on this data. But, I which I had some numbers that were worth more than the FISMA report card.
3)Our field has standards as well as generally accepted principles and pratices.
which your agreement #3 largely negates.  Standards and accepted practices are obviously the foundation, the bedrock to build a security program on.  However, a successful program is one where the people and procedures respond to changes in the environment.  If all your systems are up to standards and fully patched, but when a zero day exploit surfaces, your are unable to match it, you are vulnerable.  Only thing that you got from the effort at standards and pratices is you know (maybe) that you got hit.
Frankly, if all it took was standards and pratices, I wouldn&#039;t find computer security very interesting.

P.S. Thanks for an interesting blog.

Dave Funk</description>
		<content:encoded><![CDATA[<p>I think that I agree with Linus a bit more than you.  In your disagreements:<br />
1) Information Security has known testing methods.<br />
Which are basically broken down into compliance testing, where the linkage to security is indirect at best and insignificant at worst (FISMA); and pen testing, which directly measures results, but we&#8217;re a few years away from getting quantitave metrics from results.<br />
2) Information Security has metrics that can be applied to help understand risk.<br />
Problem is, Linus talked about quantification.  Yes todays metrics help to understand risk, but today it requires a priest of Delphi to understand it.  Linus (and I, and my CIO, and a lot of people) would like meaningful, reliable numbers.  The only reliable metric that I know of is &#8216;what has been an organization&#8217;s history with computer related incidents, and what is that organizations&#8217;s environment?&#8217;  Obviously the &#8216;reliable&#8217; part is all bound up in how good that they are watching (assuming that they are telling you the truth!)  The US Army has had some real problems with the Red Army, but they are being actively hacked by a pretty large, well organized, state-sponsored group.  The VA has had some problems, but they operate in a low to moderate threat environment.  I can make conclusions based on this data. But, I which I had some numbers that were worth more than the FISMA report card.<br />
3)Our field has standards as well as generally accepted principles and pratices.<br />
which your agreement #3 largely negates.  Standards and accepted practices are obviously the foundation, the bedrock to build a security program on.  However, a successful program is one where the people and procedures respond to changes in the environment.  If all your systems are up to standards and fully patched, but when a zero day exploit surfaces, your are unable to match it, you are vulnerable.  Only thing that you got from the effort at standards and pratices is you know (maybe) that you got hit.<br />
Frankly, if all it took was standards and pratices, I wouldn&#8217;t find computer security very interesting.</p>
<p>P.S. Thanks for an interesting blog.</p>
<p>Dave Funk</p>
]]></content:encoded>
	</item>
</channel>
</rss>

