<?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"
	>
<channel>
	<title>Comments on: PCI 6.6 &#38; 11.3 clarification</title>
	<atom:link href="http://www.mckeay.net/2008/04/23/pci-66-113-clarification/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mckeay.net/2008/04/23/pci-66-113-clarification/</link>
	<description>The views of one man on security, privacy and anything else that catches his attention</description>
	<pubDate>Fri, 21 Nov 2008 23:08:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Martin</title>
		<link>http://www.mckeay.net/2008/04/23/pci-66-113-clarification/#comment-1708</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Fri, 25 Apr 2008 02:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/04/23/pci-66-113-clarification/#comment-1708</guid>
		<description>Matt,

If I was just talking about the network scanning tools, I'd agree with you.  Anyone holding a QSA had better have the skill set to read a Nessus scan.  But I was referring to the application scanning tools, which are a whole different beast all together.  There aren't a lot of people who have the experience necessary to properly configure and read the reports of a web app scanning tool.  

I should have been a little clearer in my verbiage.

Martin</description>
		<content:encoded><![CDATA[<p>Matt,</p>
<p>If I was just talking about the network scanning tools, I&#8217;d agree with you.  Anyone holding a QSA had better have the skill set to read a Nessus scan.  But I was referring to the application scanning tools, which are a whole different beast all together.  There aren&#8217;t a lot of people who have the experience necessary to properly configure and read the reports of a web app scanning tool.  </p>
<p>I should have been a little clearer in my verbiage.</p>
<p>Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Harrigan</title>
		<link>http://www.mckeay.net/2008/04/23/pci-66-113-clarification/#comment-1705</link>
		<dc:creator>Matt Harrigan</dc:creator>
		<pubDate>Thu, 24 Apr 2008 22:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mckeay.net/2008/04/23/pci-66-113-clarification/#comment-1705</guid>
		<description>"One thing I’d like to see clarified even further is the term “proper use of” when it refers to application and source code tools; does this mean that the person using the tools needs to be certified in some way, have proof of training or just need to say they’re experienced with the tools? It’s minutia like this that gives QSAs gray hair." 

Holding a QSA is indicative of the concept that you should certainly know how to do something as simple as run an automated scanning tool. If the limited set of knowledge that one has managed to garner from any certification process does not include the very limited education required to run automated tools, then the individual in question should likely find an alternative career. Let's face it, infosec is boiling to the rim with posers.</description>
		<content:encoded><![CDATA[<p>&#8220;One thing I’d like to see clarified even further is the term “proper use of” when it refers to application and source code tools; does this mean that the person using the tools needs to be certified in some way, have proof of training or just need to say they’re experienced with the tools? It’s minutia like this that gives QSAs gray hair.&#8221; </p>
<p>Holding a QSA is indicative of the concept that you should certainly know how to do something as simple as run an automated scanning tool. If the limited set of knowledge that one has managed to garner from any certification process does not include the very limited education required to run automated tools, then the individual in question should likely find an alternative career. Let&#8217;s face it, infosec is boiling to the rim with posers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
