<?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: Security Fixation</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=334" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=334</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Andy</title>
		<link>http://spiresecurity.com/?p=334&#038;cpage=1#comment-482</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Tue, 20 Mar 2007 02:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=334#comment-482</guid>
		<description><![CDATA[I&#039;m coming very late to this debate. Sorry about that.

As should be clear - security vulnerabilities are different than other product defects.  A faulty brake system on a truck is a vulnerability, but it isn&#039;t something that generally people will try to exploit for their gain.

The same can not be said for other technologies.

Were pinto owners angry when people tried to show how easily they blow up.  yes, but it was because of a loss of resale value and fear for their own safety in regular circumstances, not because they feared intentional rear-ending that would cause them to burst into flames.

The same isn&#039;t true for security vulnerabilities.  People do attempt to exploit them, with a notable increase in issues as a result of disclosure.
]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m coming very late to this debate. Sorry about that.</p>
<p>As should be clear &#8211; security vulnerabilities are different than other product defects.  A faulty brake system on a truck is a vulnerability, but it isn&#8217;t something that generally people will try to exploit for their gain.</p>
<p>The same can not be said for other technologies.</p>
<p>Were pinto owners angry when people tried to show how easily they blow up.  yes, but it was because of a loss of resale value and fear for their own safety in regular circumstances, not because they feared intentional rear-ending that would cause them to burst into flames.</p>
<p>The same isn&#8217;t true for security vulnerabilities.  People do attempt to exploit them, with a notable increase in issues as a result of disclosure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Wysopal</title>
		<link>http://spiresecurity.com/?p=334&#038;cpage=1#comment-481</link>
		<dc:creator>Chris Wysopal</dc:creator>
		<pubDate>Wed, 28 Feb 2007 00:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=334#comment-481</guid>
		<description><![CDATA[Pete,
Your ideas of requiring a positive cost-benefit equation or a significance requirement are nice in theory but not in the real world.  Who would enforce this?  How would significance be defined?  You have to allow for insignificant disclosures or you have to ban all disclosure.  To not be able to describe any vulnerabilities or any attack techniques keeps the field of security from advancing.

I&#039;m all for delaying the release of detailed vulnerability information until people have a chance to patch because a timeline can be defined.  Cost-benefit equations and significance cannot.  If you have ideas how I would like to hear them.

-Chris
]]></description>
		<content:encoded><![CDATA[<p>Pete,<br />
Your ideas of requiring a positive cost-benefit equation or a significance requirement are nice in theory but not in the real world.  Who would enforce this?  How would significance be defined?  You have to allow for insignificant disclosures or you have to ban all disclosure.  To not be able to describe any vulnerabilities or any attack techniques keeps the field of security from advancing.</p>
<p>I&#8217;m all for delaying the release of detailed vulnerability information until people have a chance to patch because a timeline can be defined.  Cost-benefit equations and significance cannot.  If you have ideas how I would like to hear them.</p>
<p>-Chris</p>
]]></content:encoded>
	</item>
</channel>
</rss>
