<?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: WAF Better Than Code Review?  Not Really.</title>
	<atom:link href="http://www.veracode.com/blog/2008/04/waf-better-than-code-review-think-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.veracode.com/blog/2008/04/waf-better-than-code-review-think-again/</link>
	<description>Application security testing, analysis, and metrics</description>
	<lastBuildDate>Tue, 15 May 2012 22:16:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The State of Web Security &#124; Mike Andrews</title>
		<link>http://www.veracode.com/blog/2008/04/waf-better-than-code-review-think-again/comment-page-1/#comment-1031</link>
		<dc:creator>The State of Web Security &#124; Mike Andrews</dc:creator>
		<pubDate>Tue, 20 May 2008 23:52:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=85#comment-1031</guid>
		<description>[...] been lots of comments about this (too numerous to link to all of them, but there&#8217;s refs from these main two), [...]</description>
		<content:encoded><![CDATA[<p>[...] been lots of comments about this (too numerous to link to all of them, but there&#8217;s refs from these main two), [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.veracode.com/blog/2008/04/waf-better-than-code-review-think-again/comment-page-1/#comment-951</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Thu, 17 Apr 2008 06:53:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=85#comment-951</guid>
		<description>If you care about PCI compliance issues, you may want to check out http://pcianswers.com/  It&#039;s a great source for analysis, information, and review of the payment services space.</description>
		<content:encoded><![CDATA[<p>If you care about PCI compliance issues, you may want to check out <a href="http://pcianswers.com/" rel="nofollow">http://pcianswers.com/</a>  It&#8217;s a great source for analysis, information, and review of the payment services space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Coates</title>
		<link>http://www.veracode.com/blog/2008/04/waf-better-than-code-review-think-again/comment-page-1/#comment-948</link>
		<dc:creator>Michael Coates</dc:creator>
		<pubDate>Wed, 16 Apr 2008 15:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=85#comment-948</guid>
		<description>&quot;Sure, the WAF can protect against some known attacks, and if you set it up the right way, it can attempt to detect and block other, unknown attacks — that is, if it’s configured aggressively enough.&quot;

Yea, you nailed it there. The WAF will just go the same route as the network based firewall. Open a connection here, open up a port there, eventually the firewall is letting in much more than it is actually blocking.  

Unfortunately, I see the WAF going the same way. A very cautious approach will be taken to any blocking actions and once something breaks legitimate functionality it will be throttled back. This approach will not provide sufficient application security and pales in quality to a quality source code review.

-Michael</description>
		<content:encoded><![CDATA[<p>&#8220;Sure, the WAF can protect against some known attacks, and if you set it up the right way, it can attempt to detect and block other, unknown attacks — that is, if it’s configured aggressively enough.&#8221;</p>
<p>Yea, you nailed it there. The WAF will just go the same route as the network based firewall. Open a connection here, open up a port there, eventually the firewall is letting in much more than it is actually blocking.  </p>
<p>Unfortunately, I see the WAF going the same way. A very cautious approach will be taken to any blocking actions and once something breaks legitimate functionality it will be throttled back. This approach will not provide sufficient application security and pales in quality to a quality source code review.</p>
<p>-Michael</p>
]]></content:encoded>
	</item>
</channel>
</rss>

