<?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: How do companies address security testing?</title>
	<atom:link href="http://www.cigital.com/justice-league-blog/2008/03/31/how-do-companies-address-security-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cigital.com/justice-league-blog/2008/03/31/how-do-companies-address-security-testing/</link>
	<description></description>
	<lastBuildDate>Wed, 30 Nov 2011 15:50:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Justice League &#187; Blog Archive &#187; Is Penetration Testing Security Testing? [Cigital]</title>
		<link>http://www.cigital.com/justice-league-blog/2008/03/31/how-do-companies-address-security-testing/#comment-92</link>
		<dc:creator>Justice League &#187; Blog Archive &#187; Is Penetration Testing Security Testing? [Cigital]</dc:creator>
		<pubDate>Wed, 09 Apr 2008 14:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.cigital.com/justiceleague/2008/03/31/how-do-companies-address-security-testing/#comment-92</guid>
		<description>[...] Because black box tools to a large extent run canned tests they will not satisfy my security testing goal (see previous entry) of having run tests that one traces back to requirements. &#8216;Requirements that one created as a result of doing risk analysis that determines exactly what behaviors (and their impacts) should be avoided were the software attacked. [...] </description>
		<content:encoded><![CDATA[<p>[...] Because black box tools to a large extent run canned tests they will not satisfy my security testing goal (see previous entry) of having run tests that one traces back to requirements. &#8216;Requirements that one created as a result of doing risk analysis that determines exactly what behaviors (and their impacts) should be avoided were the software attacked. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

