<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: QSA Vendor Selection – Points of Consideration</title>
	<atom:link href="http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/feed/" rel="self" type="application/rss+xml" />
	<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/</link>
	<description>Assessing, Articulating &#38; Quantifying Information Security Risk</description>
	<lastBuildDate>Mon, 31 Oct 2011 20:19:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-322</link>
		<dc:creator><![CDATA[Chris Hayes]]></dc:creator>
		<pubDate>Sat, 08 Aug 2009 17:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-322</guid>
		<description><![CDATA[@Volodymyr - Please accept my apologies for taking so long to respond. You are more then welcome to publish the &quot;QSA Vendor Selection&quot; article on your company website. Thanks for asking!]]></description>
		<content:encoded><![CDATA[<p>@Volodymyr &#8211; Please accept my apologies for taking so long to respond. You are more then welcome to publish the &#8220;QSA Vendor Selection&#8221; article on your company website. Thanks for asking!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Volodymyr Tkachenko</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-315</link>
		<dc:creator><![CDATA[Volodymyr Tkachenko]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 06:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-315</guid>
		<description><![CDATA[Dear Chris!

I kindly ask your permission to publish this article on under column Knowledge base on my company Web site, also we &#039;re going to translate this article to ukrainian and russian languages and put it to respective chapters of the site.

Our company is focused on IT audit and IRM functions, operating in the Ukraine.]]></description>
		<content:encoded><![CDATA[<p>Dear Chris!</p>
<p>I kindly ask your permission to publish this article on under column Knowledge base on my company Web site, also we &#8216;re going to translate this article to ukrainian and russian languages and put it to respective chapters of the site.</p>
<p>Our company is focused on IT audit and IRM functions, operating in the Ukraine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-314</link>
		<dc:creator><![CDATA[Chris Hayes]]></dc:creator>
		<pubDate>Fri, 24 Jul 2009 15:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-314</guid>
		<description><![CDATA[@Trebuchet - Thanks for the comment and sharing some insight. And no, I am not being paid by any one for my comments on the SPSP.

But hey - thanks for the chuckle on my second day of vacation. Off to the beach...]]></description>
		<content:encoded><![CDATA[<p>@Trebuchet &#8211; Thanks for the comment and sharing some insight. And no, I am not being paid by any one for my comments on the SPSP.</p>
<p>But hey &#8211; thanks for the chuckle on my second day of vacation. Off to the beach&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trebuchet</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-313</link>
		<dc:creator><![CDATA[Trebuchet]]></dc:creator>
		<pubDate>Fri, 24 Jul 2009 15:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-313</guid>
		<description><![CDATA[Chris ... how much are you being paid to market their Society of Payment Security Professionals certification?

I probably have more experience than a vast majority of the QSAs currently in the market.  Over the past 7 years I have not only conducted countless audits, but have leaded the two largest remediation efforts currently on record for the PCI Industry.  I also, have an extensive background in IT Security, Forensics and Intrusion Analysis, and carry the commensurate certifications as well.  

In my opinion, The Society of Payment Security Professionals is just another new certification from a small group of well meaning individuals who are trying to make a name for themselves as the &quot;defacto&quot; standard-gurus in the PCI Industry.  I also believe it is against the guidance of the PCI SSC and could place needless legal exposure to a well intended effort.

Also, as a corporate official, you should be coached as to what certifications you “recognize” and make sure your corporate legal staff is also in alignment with such attestations.

More importantly, from my experience, I have found that an IT Security and Audit background is a good start … but a QSAs metal is forged in remediation efforts not in the “wham-bam-thank-you-ma’am” of audit.

Good luck in your search.]]></description>
		<content:encoded><![CDATA[<p>Chris &#8230; how much are you being paid to market their Society of Payment Security Professionals certification?</p>
<p>I probably have more experience than a vast majority of the QSAs currently in the market.  Over the past 7 years I have not only conducted countless audits, but have leaded the two largest remediation efforts currently on record for the PCI Industry.  I also, have an extensive background in IT Security, Forensics and Intrusion Analysis, and carry the commensurate certifications as well.  </p>
<p>In my opinion, The Society of Payment Security Professionals is just another new certification from a small group of well meaning individuals who are trying to make a name for themselves as the &#8220;defacto&#8221; standard-gurus in the PCI Industry.  I also believe it is against the guidance of the PCI SSC and could place needless legal exposure to a well intended effort.</p>
<p>Also, as a corporate official, you should be coached as to what certifications you “recognize” and make sure your corporate legal staff is also in alignment with such attestations.</p>
<p>More importantly, from my experience, I have found that an IT Security and Audit background is a good start … but a QSAs metal is forged in remediation efforts not in the “wham-bam-thank-you-ma’am” of audit.</p>
<p>Good luck in your search.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cmlh</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-269</link>
		<dc:creator><![CDATA[cmlh]]></dc:creator>
		<pubDate>Fri, 29 May 2009 02:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-269</guid>
		<description><![CDATA[@Chris Hayes

I have known @sfoak for sometime and he and @chipmonkey allowed me to stay with them when I arrived in the USA in September 2008 to present at the OWASP USA Conference and ToorCon prior to departing to Toronto, Canada for SecTor 2008.

I suspect internationally there would be not much difference as @sfoak also conducted the QSA training  internationally (and I believe he also taught the SPSP Training but I could be incorrect about this).]]></description>
		<content:encoded><![CDATA[<p>@Chris Hayes</p>
<p>I have known @sfoak for sometime and he and @chipmonkey allowed me to stay with them when I arrived in the USA in September 2008 to present at the OWASP USA Conference and ToorCon prior to departing to Toronto, Canada for SecTor 2008.</p>
<p>I suspect internationally there would be not much difference as @sfoak also conducted the QSA training  internationally (and I believe he also taught the SPSP Training but I could be incorrect about this).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-268</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Fri, 29 May 2009 01:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-268</guid>
		<description><![CDATA[@Andre

&quot;Spend money and time on compliance readiness with an external trusted adviser, such as a strategy consulting company specializing in risk management, with strong experience and exposure to both network and app penetration-testing. Risk management is so much more important than any single compliance standard (or even all of them combined).&quot;

With all due respect, I humbly submit that there are very, very few information security focused &quot;risk management&quot; consultancies that could teach Chris (and his organization) much of anything.]]></description>
		<content:encoded><![CDATA[<p>@Andre</p>
<p>&#8220;Spend money and time on compliance readiness with an external trusted adviser, such as a strategy consulting company specializing in risk management, with strong experience and exposure to both network and app penetration-testing. Risk management is so much more important than any single compliance standard (or even all of them combined).&#8221;</p>
<p>With all due respect, I humbly submit that there are very, very few information security focused &#8220;risk management&#8221; consultancies that could teach Chris (and his organization) much of anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-267</link>
		<dc:creator><![CDATA[Chris Hayes]]></dc:creator>
		<pubDate>Fri, 29 May 2009 01:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-267</guid>
		<description><![CDATA[@cmlh - My reference to the Society of Payment Professionals was primarily in the context of the CPISA certification. From what I understand, the CPISA exam by far more comprehensive in terms of what it covers. QSA + CPISA + a good interview hopefully results in a half decent QSA assessor. Regarding QSAs outside the United States - no idea - sorry. I would hook up with @sfoak on Twitter - he can probably point you in the right direction. Thanks for the comment!

@Andre - Thanks for the follow-up comment. The reason I stated that the QSAC is the most appropriate is based off my experience of payment processors deferring to the QSAC as to whether or not a compensating control is adequate or for interpreting various PCI-DSS language. Personally, I think it is a cop out on the payment processor side but I have witnessed these conversations. So, you wind up in a situation where you have a sub par QSAC stating one thing, a merchant stating something not in alignment with the QSAC, and the payment processor siding with the QSAC because they are the independent PCI qualified assessor. This is a liability shift-play on the side of the processors.

Without going into details, the reason my employer recently reached out to a QSAC was to get an objective third party review of a solution we are building. Once you become a level one merchant, you have to use a QSAC. Thus in scenarios where you are a level 2 merchant, almost a level 1 merchant, and spending a lot of money on a solution - you want to make sure that when you do become level 1 your solution is tight - otherwise it is a waste of money.

We are more in agreement then we are in disagreement. Some of my past PCI / QSA posts underscore my skeptcism towards QSAs- but reiterate merchants taking more responsibility for PCI-DSS. At the end of the day, I have to be the more knowledgable about PCI-DSS then any QSAC we hire; unforutnately - they carry a lot more weight in their opinion.

Thanks again for the comments Andre. Glad to see that a fellow OWASP leader cares about PCI and risk topics.]]></description>
		<content:encoded><![CDATA[<p>@cmlh &#8211; My reference to the Society of Payment Professionals was primarily in the context of the CPISA certification. From what I understand, the CPISA exam by far more comprehensive in terms of what it covers. QSA + CPISA + a good interview hopefully results in a half decent QSA assessor. Regarding QSAs outside the United States &#8211; no idea &#8211; sorry. I would hook up with @sfoak on Twitter &#8211; he can probably point you in the right direction. Thanks for the comment!</p>
<p>@Andre &#8211; Thanks for the follow-up comment. The reason I stated that the QSAC is the most appropriate is based off my experience of payment processors deferring to the QSAC as to whether or not a compensating control is adequate or for interpreting various PCI-DSS language. Personally, I think it is a cop out on the payment processor side but I have witnessed these conversations. So, you wind up in a situation where you have a sub par QSAC stating one thing, a merchant stating something not in alignment with the QSAC, and the payment processor siding with the QSAC because they are the independent PCI qualified assessor. This is a liability shift-play on the side of the processors.</p>
<p>Without going into details, the reason my employer recently reached out to a QSAC was to get an objective third party review of a solution we are building. Once you become a level one merchant, you have to use a QSAC. Thus in scenarios where you are a level 2 merchant, almost a level 1 merchant, and spending a lot of money on a solution &#8211; you want to make sure that when you do become level 1 your solution is tight &#8211; otherwise it is a waste of money.</p>
<p>We are more in agreement then we are in disagreement. Some of my past PCI / QSA posts underscore my skeptcism towards QSAs- but reiterate merchants taking more responsibility for PCI-DSS. At the end of the day, I have to be the more knowledgable about PCI-DSS then any QSAC we hire; unforutnately &#8211; they carry a lot more weight in their opinion.</p>
<p>Thanks again for the comments Andre. Glad to see that a fellow OWASP leader cares about PCI and risk topics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre Gironda</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-266</link>
		<dc:creator><![CDATA[Andre Gironda]]></dc:creator>
		<pubDate>Thu, 28 May 2009 21:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-266</guid>
		<description><![CDATA[@Chris Hayes:
You are right that I am reading too much into the post. That&#039;s what I do.

This is a really good post, mind you, otherwise I wouldn&#039;t have commented!

However, I just think that your #6 should be #1 and the others should be like... footnotes or something ;&gt;

To continue the good conversation, I wanted to comment further on one point you made, &quot;QSA vendors are the most appropriate choice in the eyes of most payment processors&quot;.

This is an interesting insight because what if QSACs are not the most appropriate choice to help with SAQs, compensating/alternate controls, or planned/future Merchant Level changes? My strawman argument here is that QSACs are notoriously low quality and lack proper risk management experience, as well as deep technical experience.

Also -- I have some questions based on this comment. Assume you are right and that QSACs are the most appropriate choice to go to for compliance readiness projects for companies handling cardholder data.

Who is the next most appropriate choice? What kinds of non-QSAC security consulting/services shops or security vendors should prospecting organizations avoid?

I mean, it doesn&#039;t make any sense to hire out a QSA to do work that isn&#039;t required by a QSA, right? Or are you suggesting that prospecting organizations instead use non-QSA people from a QSAC for all compliance readiness work? Again, this brings me back to my point that QSAC != quality.]]></description>
		<content:encoded><![CDATA[<p>@Chris Hayes:<br />
You are right that I am reading too much into the post. That&#8217;s what I do.</p>
<p>This is a really good post, mind you, otherwise I wouldn&#8217;t have commented!</p>
<p>However, I just think that your #6 should be #1 and the others should be like&#8230; footnotes or something ;&gt;</p>
<p>To continue the good conversation, I wanted to comment further on one point you made, &#8220;QSA vendors are the most appropriate choice in the eyes of most payment processors&#8221;.</p>
<p>This is an interesting insight because what if QSACs are not the most appropriate choice to help with SAQs, compensating/alternate controls, or planned/future Merchant Level changes? My strawman argument here is that QSACs are notoriously low quality and lack proper risk management experience, as well as deep technical experience.</p>
<p>Also &#8212; I have some questions based on this comment. Assume you are right and that QSACs are the most appropriate choice to go to for compliance readiness projects for companies handling cardholder data.</p>
<p>Who is the next most appropriate choice? What kinds of non-QSAC security consulting/services shops or security vendors should prospecting organizations avoid?</p>
<p>I mean, it doesn&#8217;t make any sense to hire out a QSA to do work that isn&#8217;t required by a QSA, right? Or are you suggesting that prospecting organizations instead use non-QSA people from a QSAC for all compliance readiness work? Again, this brings me back to my point that QSAC != quality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cmlh</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-265</link>
		<dc:creator><![CDATA[cmlh]]></dc:creator>
		<pubDate>Thu, 28 May 2009 18:48:53 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-265</guid>
		<description><![CDATA[@Chris Hayes

In relation to 2.

Are you referring to the CPISA?

Have you encountered anyone with both the CPISA and CPISM?

Also, what has been you experience with QSA outside of the USA?]]></description>
		<content:encoded><![CDATA[<p>@Chris Hayes</p>
<p>In relation to 2.</p>
<p>Are you referring to the CPISA?</p>
<p>Have you encountered anyone with both the CPISA and CPISM?</p>
<p>Also, what has been you experience with QSA outside of the USA?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting Information Security Bits for 05/28/2009 &#124; Infosec Ramblings</title>
		<link>http://risktical.com/2009/05/28/qsa-vendor-selection-%e2%80%93-points-of-consideration/#comment-264</link>
		<dc:creator><![CDATA[Interesting Information Security Bits for 05/28/2009 &#124; Infosec Ramblings]]></dc:creator>
		<pubDate>Thu, 28 May 2009 18:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=209#comment-264</guid>
		<description><![CDATA[[...] replace QSA with penetration test, consulting gig, etc. These are great tips for all RFP processes. QSA Vendor Selection - Points of Consideration &lt;&lt; Risktical Ramblings Tags: ( rfp [...]]]></description>
		<content:encoded><![CDATA[<p>[...] replace QSA with penetration test, consulting gig, etc. These are great tips for all RFP processes. QSA Vendor Selection &#8211; Points of Consideration &lt;&lt; Risktical Ramblings Tags: ( rfp [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

