<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Zen Dzign &#187; credit card</title>
	<atom:link href="http://www.zendzign.com/tag/credit-card/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zendzign.com</link>
	<description>The official ZZ Servers Blog - Visit http://www.zzservers.com for your business hosting needs.</description>
	<lastBuildDate>Thu, 26 Jan 2012 05:59:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>PCI Data Security Standards Rock Video</title>
		<link>http://www.zendzign.com/2010/05/pci-data-security-standards-rock-video/</link>
		<comments>http://www.zendzign.com/2010/05/pci-data-security-standards-rock-video/#comments</comments>
		<pubDate>Tue, 25 May 2010 19:14:34 +0000</pubDate>
		<dc:creator>Peter Zendzian</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[credit cards stolen]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[education]]></category>
		<category><![CDATA[video]]></category>

		<guid isPermaLink="false">http://www.zendzign.com/?p=160</guid>
		<description><![CDATA[This short animated video provides an overview of the PCI Data Security Standard in a more entertaining way.]]></description>
			<content:encoded><![CDATA[<p>This short animated video provides an overview of the PCI Data  Security Standard in a more entertaining way.</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="640" height="385" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.youtube.com/v/xpfCr4By71U&amp;hl=en_US&amp;fs=1&amp;rel=0" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="640" height="385" src="http://www.youtube.com/v/xpfCr4By71U&amp;hl=en_US&amp;fs=1&amp;rel=0" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.zendzign.com/2010/05/pci-data-security-standards-rock-video/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>PCI Compliant Hosting &#8211; Are you sure your host knows what PCI is and what they are selling?</title>
		<link>http://www.zendzign.com/2009/10/pci-compliant-hosting-are-you-sure-your-host-knows-what-pci-is-and-what-they-are-selling/</link>
		<comments>http://www.zendzign.com/2009/10/pci-compliant-hosting-are-you-sure-your-host-knows-what-pci-is-and-what-they-are-selling/#comments</comments>
		<pubDate>Wed, 28 Oct 2009 15:01:23 +0000</pubDate>
		<dc:creator>David M. Zendzian</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[qsa]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[shared hosting]]></category>
		<category><![CDATA[Small Business]]></category>

		<guid isPermaLink="false">http://www.zendzign.com/?p=70</guid>
		<description><![CDATA[I recently had a discussion with a potential customer on why they should work with ZZ Servers instead of one of the now hundreds of other hosting providers offering PCI &#8220;compliant&#8221; hosting services. After spending the last 5 years doing PCI Level 1 validations I have run into many areas that hosting providers just do [...]]]></description>
			<content:encoded><![CDATA[<p>I recently had a discussion with a potential customer on why they should work with ZZ Servers instead of one of the now hundreds of other hosting providers offering PCI &#8220;compliant&#8221; hosting services. After spending the last 5 years doing PCI Level 1 validations I have run into many areas that hosting providers just do not get PCI and what hosting providers need to know to provide secure &amp; compliant hosting. I have also been able to compile a list of questions that I can use to determine if they are just trying to sell a service or really provide a PCI solution.</p>
<p><span id="more-70"></span></p>
<p>I was able to spend a good 1/2 an hour with the now new customer and help them understand how our approach meets the intent of PCI and is not focused only on trying to &#8220;make the sale.&#8221;  However, for those that we do not know what questions to ask of a hosting provider I have started a new project where I will be &#8220;shopping&#8221; for a new hosting provider and will post the communications I have with them, along with some additional comments on what their answers would mean to me if I was in my QSA role evaluating their solutions.  I will keep the communications anonymous to prevent any liability issues, but feel free to use any of the questions or comments I have when discussing hosting solutions with any providers you may be examining; and feel free to use my questions against us when you call and ask about PCI or Compliant based hosting with ZZ Servers.</p>
<p>With that in mind, here is the first discussion with a decent data-center with multiple data-centers fully owned and operated by their staff in the northern midwest.  I have highlighted items that caused me to be concerned about their understanding of PCI and what it takes for merchants or service providers to be hosted with managed PCI solutions.  Please note, anyone can take a rack of hardware and managed / deploy it in a compliant manor.  But that is not what these hosting providers are selling.  They are selling compliant solutions, leading customers who do not fully undersand the requirements to think they are meeting all of the requirements.</p>
<p>***Chat Information*You are now chatting with &#8216;Paul&#8217;<br />
*Paul: *Greetings, my name is Paul.  Welcome to &lt;HOSTING PROVIDER&gt; Sales.  With<br />
whom am I speaking?   How may I be of assistance?<br />
*you: *Hello, i saw your VPS servers have a $50/mo PCI certification?<br />
what does that provide? Does that mean i&#8217;ll be compliant? do i need<br />
anything else? does that include my scanning, pen test,<br />
internal/external? log monitoring?<br />
*you: *hello?<br />
*Paul: *Hello, sorry about that<br />
<strong>*Paul: *the PCI certification will include all scans for your server to<br />
be entirely compliant</strong><br />
<em>&#8211; This is common, many people belive that if you get your ASV scanning &amp; answer questionairre you are compliant..if it was only that simple</em><br />
*you: *so it is only the scans?<br />
*you: *not the rest of the compliance needs?<br />
*you: *internal &amp; external scans then?<br />
*Paul: *it covers all services needed<br />
*you: *external logging/monitoring, firewalls, IDS, 2 factor remote<br />
access, pen-testing (internal/eternal), asv scanning &amp; internal scanning<br />
(&amp; other stuff i can&#8217;t remember atm)??<br />
<strong>*Paul: *Yes, it is the complete service</strong><br />
<em>&#8211; how can he say it&#8217;s scanning, then a complete service? At this point I really believe the sales guy does not know what he is selling</em><br />
*you: *applicatoin &amp; network penetration testing? how do you have that<br />
for $50/mo? the best quote I have from a professional pen-testing<br />
company is 5000/year<br />
*Paul: *let me double check<br />
<strong>*Paul: *yes, it does, I have confirmed</strong><em><br />
&#8211; confirmed? if you can&#8217;t tell by now that I am asking questions above his knowledge level; why not conference in someone who knows the answer..<br />
&#8211; Many hosting providers want you to email or fill in a form so they can manage their response, if they can&#8217;t answer your quetions at all hours<br />
&#8211; then are you sure they can manage your compliance needs at any hour??  Get them to bring the expert on the phone while you are asking questions!</em><br />
*you: *interesting, do you have a detailed whitepaper or pdf on the<br />
complete services offereed?<br />
*you: *and i assume i&#8217;ll have to get more than 1 server<br />
<strong>*Paul: *No, you can have PCIC with one server</strong><br />
<em>&#8211; big big red flag!! If you are only using paypal/google for payments then yes this is right but if you are not then the requirement for &#8220;single use&#8221; is pretty important</em><br />
*you: *and that includes firewalls too right? do i have a dedicated<br />
rfc1918 address space?<br />
*you: *you can?<br />
*you: *how do you satisfy the &#8220;single purpose&#8221; requirement?<br />
*you: *where a server can not be a web &amp; database server<br />
<strong>*Paul: *we do not require a cluster for pcic<br />
&#8211; </strong><em>I wasn&#8217;t asking about a cluster. This is a typical issue, the sales team is use to selling hosting of servers but does not understand PCI.  I guess they have not had<br />
&#8211; any PCI training (which you merchants &amp; service providers are required to have annually)<br />
</em>*you: *you do not, but PCI requires that<br />
*you: *pci has something somewhere that requires each server have a<br />
single function<br />
*you: *do you have any documentation? or details about what is included<br />
in your PCI services?<br />
<strong>*Paul: *I do not have a detailed outline, but I know these are the<br />
standards we follow</strong><br />
<em>&#8211; Another warning&#8230;PCI is documentation heavy, if they do not have documentation, have they really done all thats required?</em><br />
*Paul:<br />
*<a href="https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml">https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml</a><br />
*you: *yes i am familiar with that<br />
*you: *our QSA has ingrained tht into us<br />
*you: *i was just curious because some of your answers do not jibe with<br />
what the PCI-DSS requires<br />
*you: *ok i think i have enough for now; thank you for your time<br />
*you: *Have a great night..oh one last question; where are your<br />
data-centers located?<br />
*Paul: *My pleasure, they are in &lt;LOCATION&gt;<br />
*you: *any other geographic areas?<br />
*Paul: *they are all located in &lt;ONE LOCATION&gt;<br />
*you: *thank you have a great night<br />
*you: *oh one other questoin<br />
*you: *what technology do you use for your remote 2 factor auth &amp; vpn<br />
technology?<br />
*you: *rsa/certificates/?<br />
*Paul: *The only vendors I have info on at the moment are control scan,<br />
security metrics, trustkeeper, and clone systems<br />
*you: *so it&#8217;s not included w/the pci service?<br />
*you: *it&#8217;s a 3rd party vendor we have to engage?<br />
*Paul: *Send me an email to &lt;SALES-EMAIL&gt; and I will find out for sure<br />
<em>&#8211; Remember earlier they said it included all required services? Again, lack of documentation &amp; training lead me to think they just do not know what the requirements are or what they are selling</em><br />
*you: *ok thank you, have a great night/morning</p>
]]></content:encoded>
			<wfw:commentRss>http://www.zendzign.com/2009/10/pci-compliant-hosting-are-you-sure-your-host-knows-what-pci-is-and-what-they-are-selling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Understanding PCI Levels and Types</title>
		<link>http://www.zendzign.com/2009/06/understanding-pci-levels-and-types/</link>
		<comments>http://www.zendzign.com/2009/06/understanding-pci-levels-and-types/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 13:19:57 +0000</pubDate>
		<dc:creator>Peter Zendzian</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[credit card payment]]></category>
		<category><![CDATA[Hosting]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Small Business]]></category>

		<guid isPermaLink="false">http://www.zendzign.com/?p=26</guid>
		<description><![CDATA[Any merchant who accepts credit cards and has a merchant account must validate compliance. It does not matter if you use a 3rd party processor or if you outsource all of your credit card processing. It&#8217;s the ownership of the merchant account that defines if you must validate compliance. The only to avoid PCI compliance [...]]]></description>
			<content:encoded><![CDATA[<p>Any merchant who accepts credit cards and has a merchant account must validate compliance. It does not matter if you use a 3rd party processor or if you outsource all of your credit card processing. It&#8217;s the ownership of the merchant account that defines if you must validate compliance. <strong><em>The only to avoid PCI compliance is by not having a merchant account. </em></strong>Below are some charts which will help you decide which category and merchant type your business fits into.<span id="more-26"></span></p>
<h4>Merchant levels and Compliance Validation Requirements</h4>
<table style="height: 416px;" border="1" width="547">
<tbody>
<tr>
<td colspan="3" align="center" valign="top"><strong>PCI Merchant Levels</strong></td>
</tr>
<tr>
<td align="center" valign="top"><strong>Level</strong></td>
<td align="center" valign="top"><strong>Description</strong></td>
<td align="center" valign="top"><strong>Validation Requirements</strong></td>
</tr>
<tr>
<td align="center" valign="middle">1</td>
<td align="left" valign="top">
<ul>
<li>Any merchant, &#8220;regardless of acceptance channel, processing over 6,000,000 Visa transactions per year</li>
<li>Any merchant that has suffered a hack or an attack that resulted in an account data compromise.</li>
<li>Any merchant that Visa, at its sole discretion, determines should meet the Level 1 merchant requirements to minimize risk to the Visa system.</li>
<li>Any merchant identified by any other payment card brand as Level 1</li>
</ul>
</td>
<td align="left" valign="top">
<ul>
<li>Annual Report on Compliance (“ROC”) by Qualified Security Assessor (“QSA”)</li>
<li>Quarterly network scan by Approved Scan Vendor (“ASV”)</li>
<li>Attestation of Compliance Form</li>
</ul>
</td>
</tr>
<tr>
<td align="center" valign="middle">2</td>
<td align="left" valign="top">
<ul>
<li>Any merchant-regardless of acceptance channel-processing 1,000,000 to 6,000,000 transactions per year</li>
</ul>
</td>
<td align="left" valign="top">
<ul>
<li>Annual Self-Assessment Questionnaire (“SAQ”)</li>
<li>Quarterly network scan by ASV</li>
<li>Attestation of Compliance Form</li>
</ul>
</td>
</tr>
<tr>
<td align="center" valign="middle">3</td>
<td align="left" valign="top">
<ul>
<li>Any merchant processing 20,000 to 1,000,000 transactions per year.</li>
</ul>
</td>
<td align="left" valign="top">
<ul>
<li>Annual SAQ</li>
<li>Quarterly network scan by ASV</li>
<li>Attestation of Compliance Form</li>
</ul>
</td>
</tr>
<tr>
<td align="center" valign="middle">4</td>
<td align="left" valign="top">
<ul>
<li>Any merchant processing fewer than 20,000 transactions per year.</li>
</ul>
</td>
<td align="left" valign="top">
<ul>
<li>Annual SAQ recommended</li>
<li>Quarterly network scan by ASV if applicable</li>
<li>Compliance validation requirements set by acquirer</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p><strong>Merchant Types</strong></p>
<p>The “SAQ” is a self-validation tool for merchants and service providers who are not required to do on-site assessments for PCI DSS compliance. The SAQ includes a series of yes-or-no questions for compliance. If an answer is no, the organization must state the future remediation date and associated actions. In order to align more closely with merchants and their compliance validation process, the SAQ was revised and now allows for flexibility based on the complexity of a particular merchant’s or service provider’s business situation (see chart below). The SAQ validation type does not correlate to the merchant classification or risk level.</p>
<table border="1" width="100%">
<tbody>
<tr>
<td colspan="3" align="center" valign="top"><strong>Self-Assessment Questionnaires and Validation Types</strong></td>
</tr>
<tr>
<td align="center" valign="top"><strong>SAQ Validation</strong><strong>Type</strong></td>
<td align="center" valign="top"><strong>Description</strong></td>
<td align="center" valign="top"><strong>SAQ</strong></td>
</tr>
<tr>
<td align="center" valign="middle">1</td>
<td align="left" valign="top">Card-Not-Present (e-commerce or MO/TO) merchants, all cardholder data<br />
functions outsourced. This would never apply to face-to-face merchants.</td>
<td align="center" valign="middle">A</td>
</tr>
<tr>
<td align="center" valign="middle">2</td>
<td align="left" valign="top">Imprint-only merchants with no cardholder data storage.</td>
<td align="center" valign="middle">B</td>
</tr>
<tr>
<td align="center" valign="middle">3</td>
<td align="left" valign="top">Standalone dial-up terminal merchants, no cardholder data storage.</td>
<td align="center" valign="middle">B</td>
</tr>
<tr>
<td align="center" valign="middle">4</td>
<td align="left" valign="top">Merchants with payment application systems connected to the Internet, no<br />
cardholder data storage.</td>
<td align="center" valign="middle">C</td>
</tr>
<tr>
<td align="center" valign="middle">5</td>
<td align="left" valign="top">All other merchants (not included in descriptions for SAQs A, B or C above), and<br />
all service providers defined by a card brand as eligible to complete a SAQ.</td>
<td align="center" valign="middle">D</td>
</tr>
</tbody>
</table>
<p><strong>Service Provider Levels</strong></p>
<p>Service providers are organizations that process, store, or transmit cardholder data on behalf of clients, merchants, or other service providers. Service provider levels are defined as:</p>
<table border="1" width="100%">
<tbody>
<tr>
<td colspan="3" align="center" valign="top"><strong>Self-Assessment Questionnaires and Validation Types</strong></td>
</tr>
<tr>
<td align="center" valign="top"><strong>Service Provider Level</strong></td>
<td align="center" valign="top"><strong>Description</strong></td>
<td align="center" valign="top"><strong>Validation Requirements</strong></td>
</tr>
<tr>
<td align="center" valign="middle">1</td>
<td align="left" valign="top">Processors or any service providers that stores, processes and/or transmits over 300,000 transactions per year.</td>
<td align="left" valign="top">
<ul>
<li>Annual On-Site PCI Data Security Assessment validated Qualified Security Assessor (“QSA”)</li>
<li>Quarterly network scan by Approved Scan Vendor (“ASV”)</li>
</ul>
</td>
</tr>
<tr>
<td height="42" align="center" valign="middle">2</td>
<td align="left" valign="top">Any service provider that stores, processes and/or transmits less than 300,000 transactions per year.</td>
<td align="left" valign="top">
<ul>
<li>Validated by Service Provider</li>
</ul>
<ul>
<li>Quarterly network scan by Approved Scan Vendor (“ASV”)</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p>By using the charts above, you should be able to easily determine your level and validation type. Knowing this details will go a long way in guiding you through your compliance but it is important to partner with other qualified businesses for your service. <a href="http://www.zzservers.com">ZZ Servers</a> provides PCI focused hosted infrastructure designed for PCI compliance and includes many of controls and measures required for your business infrastructure to be fully compliant.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.zendzign.com/2009/06/understanding-pci-levels-and-types/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Batteries.com Credit Card Data Stolen</title>
		<link>http://www.zendzign.com/2009/05/batteriescom-credit-card-data-stolen/</link>
		<comments>http://www.zendzign.com/2009/05/batteriescom-credit-card-data-stolen/#comments</comments>
		<pubDate>Thu, 28 May 2009 00:52:12 +0000</pubDate>
		<dc:creator>Peter Zendzian</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[data breach]]></category>

		<guid isPermaLink="false">http://www.zendzign.com/?p=25</guid>
		<description><![CDATA[Yet another data breach involving theft of credit card data has been announced. On March 13th, Batteries.com received notice from a customer about potential unauthorized activity on their credit card. They later discovered the Batteries.com network had been breached from around February 25, 2009 to April 9, 2009. The breach involved theft of names, addresses, [...]]]></description>
			<content:encoded><![CDATA[<p>Yet another data breach involving theft of credit card data has been announced.<span> </span>On March 13th, Batteries.com received notice from a customer about potential unauthorized activity on their credit card.  They later discovered the Batteries.com network had been breached from around February 25, 2009 to April 9, 2009.  The breach involved theft of names, addresses, and credit card information.</p>
<p>This breech at Batteries.com shows that a merchant does not need to be large like Heartland to be targeted by hackers.</p>
<p>For more information regarding this breech, visit the Batteries.com <a href="http://batteries.com/security/fraud-prevention.asp">security and fraud prevention page</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.zendzign.com/2009/05/batteriescom-credit-card-data-stolen/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>PCI Data Security Standard version 1.2 now active.</title>
		<link>http://www.zendzign.com/2008/10/pci-data-security-standard-version-12-now-active/</link>
		<comments>http://www.zendzign.com/2008/10/pci-data-security-standard-version-12-now-active/#comments</comments>
		<pubDate>Fri, 24 Oct 2008 03:02:46 +0000</pubDate>
		<dc:creator>Peter Zendzian</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[assesment]]></category>
		<category><![CDATA[credit card]]></category>
		<category><![CDATA[dss]]></category>
		<category><![CDATA[qsa]]></category>

		<guid isPermaLink="false">http://www.zendzign.com/?p=20</guid>
		<description><![CDATA[As of October 1, 2008 the PCI Data Security Standard version 1.2 became active. There are a number of changes to PCI DSS since version 1.1. Version 1.2 removes much of the ambiguity from earlier versions and provides additional details on items such as the use wireless devices. One of the largest and possibly most [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-bottom: 0in;">As of October 1, 2008 the PCI Data Security Standard version 1.2 became active.  There are a <a title="PCI DSS Changes" href="http://pcianswers.com/2008/10/01/pci-dss-version-12-differences-and-updates/" target="_blank">number of changes</a> to PCI DSS since version 1.1.  Version 1.2 removes much of the ambiguity from earlier versions and provides additional details on items such as the use wireless devices.</p>
<p style="margin-bottom: 0in;"><span id="more-20"></span>One of the largest and possibly most hard hitting change is how the the certification process is placing an <a title="PCI DSS Requirements" href="http://usa.visa.com/merchants/risk_management/cisp_merchants.html#anchor_2" target="_blank">increasing amount of scrutiny on level 3 and 4 merchants</a>.  If you process credit cards and have not received any notification from your merchant bank regarding PCI DSS compliance, you will soon.</p>
<p style="margin-bottom: 0in;">I will not attempt to cover all of the details of the new standard but will say if your company handles any cardholder data, it is important to get your infrastructure into compliance with PCI DSS.</p>
<p>PCI DSS 1.2 specifies 12 requirements for compliance, organized into 6 logically related groups, which are called &#8220;control objectives.&#8221;</p>
<p>The control objectives and their requirements are:</p>
<ul>
<li><strong>Build and Maintain a Secure Network </strong>
<ol>
<li>Requirement 1: Install and maintain a firewall configuration to protect cardholder data</li>
<li>Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters</li>
</ol>
</li>
<li><strong>Protect Cardholder Data </strong>
<ol>
<li>Requirement 3: Protect stored cardholder data</li>
<li>Requirement 4: Encrypt transmission of cardholder data across open, public networks</li>
</ol>
</li>
<li><strong>Maintain a Vulnerability Management Program </strong>
<ol>
<li>Requirement 5: Use and regularly update anti-virus software</li>
<li>Requirement 6: Develop and maintain secure systems and applications</li>
</ol>
</li>
<li><strong>Implement Strong Access Control Measures </strong>
<ol>
<li>Requirement 7: Restrict access to cardholder data by business need-to-know</li>
<li>Requirement 8: Assign a unique ID to each person with computer access</li>
<li>Requirement 9: Restrict physical access to cardholder data</li>
</ol>
</li>
<li><strong>Regularly Monitor and Test Networks </strong>
<ol>
<li>Requirement 10: Track and monitor all access to network resources and cardholder data</li>
<li>Requirement 11: Regularly test security systems and processes</li>
</ol>
</li>
<li><strong>Maintain an Information Security Policy </strong>
<ol>
<li>Requirement 12: Maintain a policy that addresses information security</li>
</ol>
</li>
</ul>
<p style="margin-bottom: 0in;">Each control objective contains additional details on what is required to meet the objective and requires a detailed study to fully understand them and their impact on your existing infrastructure.  Smaller companies have the option to use a self-certification questionnaire but even this can be difficult and time consuming.</p>
<p style="margin-bottom: 0in;">ZZ Servers has fully qualified security assessors and partnerships with PCI ASV/QSA&#8217;s for all levels PCI certification, required security scans and full level 1 PCI audit validation.  Contact us today so we can can assist with your adaption of PCI DSS in your environment and ensure your full compliance with these comprehensive regulations.  Let us help you prepare and prevent the damaging costs of a data breach.</p>
<p style="margin-bottom: 0in;">Peter Zendzian<br />
Managing Partner<br />
ZZ Servers, LLC<br />
<a href="http://www.zzservers.com/">www.zzservers.com</a><br />
800-796-3574</p>
]]></content:encoded>
			<wfw:commentRss>http://www.zendzign.com/2008/10/pci-data-security-standard-version-12-now-active/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

