<?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: Is responsible disclosure dead?</title>
	<atom:link href="http://newschoolsecurity.com/2009/10/is-responsible-disclosure-dead/feed/" rel="self" type="application/rss+xml" />
	<link>http://newschoolsecurity.com/2009/10/is-responsible-disclosure-dead/</link>
	<description>The Blog Inspired By The Book</description>
	<lastBuildDate>Wed, 08 Feb 2012 09:21:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tim</title>
		<link>http://newschoolsecurity.com/2009/10/is-responsible-disclosure-dead/#comment-461</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 28 Oct 2009 20:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://newschoolsecurity.com/?p=825#comment-461</guid>
		<description>In the civilized world, responsible disclosure will continue so long as lawyers exist. If you have any financial assets worth suing, you should consider disclosing responsibly, not disclosing at all, or be prepared to suffer the natural consequences of foolish behavior.</description>
		<content:encoded><![CDATA[<p>In the civilized world, responsible disclosure will continue so long as lawyers exist. If you have any financial assets worth suing, you should consider disclosing responsibly, not disclosing at all, or be prepared to suffer the natural consequences of foolish behavior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chandler</title>
		<link>http://newschoolsecurity.com/2009/10/is-responsible-disclosure-dead/#comment-427</link>
		<dc:creator>Chandler</dc:creator>
		<pubDate>Tue, 27 Oct 2009 13:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://newschoolsecurity.com/?p=825#comment-427</guid>
		<description>The issue I take with Grossman&#039;s article is that he ignores the inconvenient branches of his logical tree.  This is not an either-or debate.

Sure, there is increasing State-Sponsored vulnerability research (see http://www.uscc.gov/researchpapers/2009/NorthropGrumman_PRC_Cyber_Paper_FINAL_Approved%20Report_16Oct2009.pdf for China-specific examples of this) as governments become more attuned to the need for both offensive as well as defensive computer security capabilities.  But that&#039;s not evidence of a Crowding Out effect--exactly the opposite, actually.

Stereotypical &quot;Mom&#039;s Basement&quot; hackers are not going away just because governments are funding vulnerability research, they&#039;re just increasing their odds of making a buck from the comfort of their dungeon lairs.

Third parties, often in the Grey Hat world or just flat-out Black Hats are being hired or commissioned to do this work.  Soldiers are being trained in how to utilize these tools.  The technical capabilities and available labor pool is being expanded in, I fear, the worst ways possible.

My personal opinion is that we are seeing growing pools of people for whom this kind of work is a legitimate living, and they will work for whomever is willing to pay them to do it.  This is dramatically increasing the risk of running a a typically-insecure corporate network if the company has any information or intellectual property assets at all (as opposed to, say, being nothing but a dinosaur existing on rents ensured by legislative carve-outs).

The most interesting (frustrating?) aspect of this is watching what happens when soft (corporate) networks, where cost saving is king, are targeted with military-grade tools and techniques, a function of governments and corporations now sharing a common information platform.

It&#039;s exciting, but doesn&#039;t leave one with much hope for the future.</description>
		<content:encoded><![CDATA[<p>The issue I take with Grossman&#8217;s article is that he ignores the inconvenient branches of his logical tree.  This is not an either-or debate.</p>
<p>Sure, there is increasing State-Sponsored vulnerability research (see <a href="http://www.uscc.gov/researchpapers/2009/NorthropGrumman_PRC_Cyber_Paper_FINAL_Approved%20Report_16Oct2009.pdf" rel="nofollow">http://www.uscc.gov/researchpapers/2009/NorthropGrumman_PRC_Cyber_Paper_FINAL_Approved%20Report_16Oct2009.pdf</a> for China-specific examples of this) as governments become more attuned to the need for both offensive as well as defensive computer security capabilities.  But that&#8217;s not evidence of a Crowding Out effect&#8211;exactly the opposite, actually.</p>
<p>Stereotypical &#8220;Mom&#8217;s Basement&#8221; hackers are not going away just because governments are funding vulnerability research, they&#8217;re just increasing their odds of making a buck from the comfort of their dungeon lairs.</p>
<p>Third parties, often in the Grey Hat world or just flat-out Black Hats are being hired or commissioned to do this work.  Soldiers are being trained in how to utilize these tools.  The technical capabilities and available labor pool is being expanded in, I fear, the worst ways possible.</p>
<p>My personal opinion is that we are seeing growing pools of people for whom this kind of work is a legitimate living, and they will work for whomever is willing to pay them to do it.  This is dramatically increasing the risk of running a a typically-insecure corporate network if the company has any information or intellectual property assets at all (as opposed to, say, being nothing but a dinosaur existing on rents ensured by legislative carve-outs).</p>
<p>The most interesting (frustrating?) aspect of this is watching what happens when soft (corporate) networks, where cost saving is king, are targeted with military-grade tools and techniques, a function of governments and corporations now sharing a common information platform.</p>
<p>It&#8217;s exciting, but doesn&#8217;t leave one with much hope for the future.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

