<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ClearNet Security: PCI:  Not our problem...</title>
    <link>http://blog.clearnetsec.com/articles/2007/05/16/pci-not-our-problem</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>PCI:  Not our problem...</title>
      <description>&lt;p&gt;
What happens when the test environment operated by MasterCard (they &#8220;own&#8221; the testing lab) is misbehaving?  I know.  They yank the wheel, swerve away from responsibility, and point to the PCI council.  And PCI?  They point back.  Beautiful, no? 
&lt;/p&gt;
&lt;img src="http://blog.clearnetsec.com/files/GiveMeTheCash.jpg" align="right"&gt; 
&lt;p&gt;
You see because they refuse to disclose missed results to you they duck responsibility for anything that may have been their fault.  They also &lt;b&gt;&lt;i&gt;clearly imply&lt;/i&gt;&lt;/b&gt; if anything is missed in your attempts to identify vulnerabilities then it is surely &lt;b&gt;&lt;i&gt;your fault or a problem with the tools you used&lt;/i&gt;&lt;/b&gt;. 
&lt;/p&gt;
&lt;p&gt;
I love it:  No clear pass criteria, no way to challenge a decision, and no transparency of what or how &lt;b&gt;&lt;i&gt;they are doing&lt;/i&gt;&lt;/b&gt;.  For all this great service you get to spend thousands every year! 
&lt;/p&gt;
&lt;p&gt;
So what happens when you call bullshit and raise hell? They pass you. :)  Let me not forget to mention we had a few extra bullets in our clip they may have unexpected us to have &#8211; bullets provided to us by friends with information.
&lt;/p&gt;
&lt;p&gt;
Be forewarned; this process has serious issues. 
&lt;/p&gt;

</description>
      <pubDate>Wed, 16 May 2007 20:51:00 -0600</pubDate>
      <guid isPermaLink="false">urn:uuid:4600bd3d-a833-44f1-8677-0ca85d8ea44a</guid>
      <author>tate@ClearNetSec.com (Tate Hansen)</author>
      <link>http://blog.clearnetsec.com/articles/2007/05/16/pci-not-our-problem</link>
      <category>Tate Hansen</category>
      <category>ClearNet</category>
      <category>ClearNet Security</category>
      <category>visa</category>
      <category>PCI</category>
      <category>cisp</category>
      <category>mastercard</category>
      <category>security</category>
      <category>testing</category>
      <category>ASV</category>
      <category>scanning</category>
      <category>vulnerability</category>
    </item>
    <item>
      <title>"PCI:  Not our problem..." by Martin McKeay</title>
      <description>&lt;p&gt;Tate,&lt;/p&gt;

&lt;p&gt;Welcome to the world of PCI DSS.  Every possible step has been taken to divorce Master Card and Visa from anything approaching responsibility.  They don&amp;#8217;t manage the standard, the PCI Council does.  They don&amp;#8217;t do any of the testing to make sure sites are secure, a consultant you hire does that.  And if there&amp;#8217;s a dispute with the results, your only choice is to go through the consultant to argue your point.  They don&amp;#8217;t even levy the fines if there is a compromise, they fine the acquiring bank and the acquiring bank fines the vendor.  No direct linkage to responsibility any where.  &lt;/p&gt;

&lt;p&gt;Isn&amp;#8217;t a great system?  &lt;/p&gt;

&lt;p&gt;Martin&lt;/p&gt;</description>
      <pubDate>Mon, 04 Jun 2007 16:36:07 -0600</pubDate>
      <guid isPermaLink="false">urn:uuid:b8121a02-a15e-4005-b6ac-8d630d7726c7</guid>
      <link>http://blog.clearnetsec.com/articles/2007/05/16/pci-not-our-problem#comment-37</link>
    </item>
  </channel>
</rss>
