<?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>PCICompliance</title>
	<atom:link href="http://www.pcicompliance.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pcicompliance.org</link>
	<description>PCI Compliance News and Resources</description>
	<lastBuildDate>Tue, 30 Jun 2009 14:21:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Mastercard Raises the Bar for PCI Compliance</title>
		<link>http://www.pcicompliance.org/pci-compliance-news/mastercard-raises-the-bar-for-pci-compliance/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-news/mastercard-raises-the-bar-for-pci-compliance/#comments</comments>
		<pubDate>Tue, 30 Jun 2009 13:52:05 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=134</guid>
		<description><![CDATA[On June 15th, Mastercard announced that Level 2 merchants, those processing between one and three million transactions annually, will now have to undergo an annual onsite assessment for PCI compliance. Previously these merchants were only required to complete the PCI DSS self-assessment questionnaire (SAQ).
The onsite assessment, which must be completed by a PCI QSA (Qualified [...]]]></description>
			<content:encoded><![CDATA[<p>On June 15th, Mastercard announced that Level 2 merchants, those processing between one and three million transactions annually, will now have to undergo an annual onsite assessment for PCI compliance. Previously these merchants were only required to complete the PCI DSS self-assessment questionnaire (SAQ).</p>
<p>The onsite assessment, which must be completed by a PCI QSA (Qualified Security Assessor), will validate compliance with the twelve requirements set forth in the Payment Card Industry Data Security Standards. The <a href="http://www.pcicompliance.org/pci-compliance-faqs/what-are-the-pci-dss-requirements/">PCI DSS requirements</a> are designed to provide increased controls around data and its exposure to compromise.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-news/mastercard-raises-the-bar-for-pci-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Regis Increases Security and Meets PCI DSS Requirements</title>
		<link>http://www.pcicompliance.org/pci-compliance-case-studies/regis-increases-security-and-meets-pci-dss-requirements/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-case-studies/regis-increases-security-and-meets-pci-dss-requirements/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 22:39:43 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=35</guid>
		<description><![CDATA[The Business Challenge:
With more than 12,000 locations worldwide, remote access security across the Regis network is no small job.  Regis had two immediate challenges they were facing. First, they needed to maintain secure remote access for their employees.  They had previously used RSA tokens and neither the employees nor the IT staff was [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The Business Challenge:</strong><br />
With more than 12,000 locations worldwide, remote access security across the Regis network is no small job.  Regis had two immediate challenges they were facing. First, they needed to maintain secure remote access for their employees.  They had previously used RSA tokens and neither the employees nor the IT staff was happy with that solution.  Additionally, Regis needed to become PCI DSS compliant quickly.</p>
<p><strong>The Solution:</strong><br />
Before choosing PhoneFactor, Regis had struggled with the difficulty of using tokens and other two-factor methods.  Their non-technical users found these solutions challenging and the IT department was spending far too much time supporting them. Regis wanted a turnkey solution for remote access that would be easy for their non-technical users to manage and minimize back-end support needs.</p>
<p>It was also critical that Regis fill the gaps in their PCI DSS compliance.  One of those was section 8.3 requiring two-factor authentication.  PhoneFactor’s quick and easy implementation made checking off this requirement painless for Regis.  </p>
<p>Using PhoneFactor has already affected the way business operates at Regis. “It’s no-hassle security, and has reduced the complaints to the Help Desk about access issues,” said Joel Wiens, Vice President of Information Technology for Regis. “It has worked just as we hoped and was an easy transition.” </p>
<p>In fact, Regis noted numerous benefits by switching to PhoneFactor’s two-factor solution:</p>
<ul>
<li>Decreased Deployment Timeframe: Deploying to a remote audience can be challenging.  Regis rolled out PhoneFactor quickly, first as a pilot and then through their normal ongoing cycle of hardware and software updates.</li>
<li>Increased User Response/Adoption: Regis users found PhoneFactor to be much more convenient than fob-based tokens.  In fact, it was so easy that they trained their staff via memo only.</li>
<li>Ongoing Reduced Costs:  With PhoneFactor, there is virtually no maintenance for the IT staff at Regis, significantly reducing their total cost of ownership.</li>
<li>Increased Security: Regis recognizes the absolute need for two-factor.  In addition, PhoneFactor’s instant fraud alerts provide much needed additional protection. This feature is even recognized in Regis’ official incident response plan.</li>
<li>Easy Expansion: PhoneFactor makes roll-out to additional users simple. And Regis plans to evaluate PhoneFactor for additional uses within their organization.</ul>
</li>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-case-studies/regis-increases-security-and-meets-pci-dss-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hearland Payment Systems Recertified for PCI Compliance</title>
		<link>http://www.pcicompliance.org/pci-compliance-news/hearland-payment-systems-recertified-for-pci-compliance/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-news/hearland-payment-systems-recertified-for-pci-compliance/#comments</comments>
		<pubDate>Thu, 21 May 2009 22:37:11 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=33</guid>
		<description><![CDATA[After reporting one of the largest breaches to date, Heartland Payment Systems was removed from Visa list of PCI DSS Validated Service Providers earlier this year. After being revalidated and submitting a Report on Compliance Visa reinstated Heartland as a PCI DSS compliant service provider in early May.
Heartland recently announced that it expects to take [...]]]></description>
			<content:encoded><![CDATA[<p>After reporting one of the largest breaches to date, Heartland Payment Systems was removed from Visa list of PCI DSS Validated Service Providers earlier this year. After being revalidated and submitting a Report on Compliance Visa reinstated Heartland as a PCI DSS compliant service provider in early May.</p>
<p>Heartland recently announced that it expects to take a significant loss in Q3 resulting from more than $12.6 million dollars in fines from Visa and Mastercard, legal fees, and administrative costs. Given that 65% of the cost of a typical data breach is due to lost business from new and existing customers, none of which is included in the $12.6M figure, this may be just the tip of the iceberg for Heartland.</p>
<p>Pained over the cost of compliance? It&#8217;s nothing compared to the cost of a breach. Ask Heartland.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-news/hearland-payment-systems-recertified-for-pci-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is the role of user authentication in PCI compliance?</title>
		<link>http://www.pcicompliance.org/pci-compliance-faqs/what-is-the-role-of-user-authentication-in-pci-compliance/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-faqs/what-is-the-role-of-user-authentication-in-pci-compliance/#comments</comments>
		<pubDate>Thu, 21 May 2009 22:03:55 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[PCI Compliance FAQs]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=24</guid>
		<description><![CDATA[Passwords Just Aren’t Enough
Password phishing is up dramatically and new, more sophisticated phishing methods have emerged. It’s clear that passwords are highly susceptible to attack and agents can’t be trusted to employ best practices with regard to storing and changing their passwords, let alone protecting their PC from malware that could be used to snoop [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Passwords Just Aren’t Enough</strong><br />
Password phishing is up dramatically and new, more sophisticated phishing methods have emerged. It’s clear that passwords are highly susceptible to attack and agents can’t be trusted to employ best practices with regard to storing and changing their passwords, let alone protecting their PC from malware that could be used to snoop their passwords. </p>
<p>Two-factor authentication (using a password, something you know, plus a second method, such as something you have or something you are to prove a user’s identity) is the new standard. </p>
<p><strong>Regulatory Compliance</strong><br />
Regulatory agencies agree that passwords are a weak link and are requiring companies to implement stronger authentication, particularly for remote workers. Depending on the industries served by the call center, a number of regulations may require them to apply strict standards for authenticating users, including:<br />
•	Payment Card Industry Data Security Standards (PCI DSS)<br />
•	Health Insurance Portability and Accountability Act (HIPAA)<br />
•	Authentication in an Internet Banking Environment Guidance (FFIEC)<br />
•	Sarbanes-Oxley</p>
<p><strong>Traditional Two-Factor Authentication Solutions</strong><br />
There are a number of two-factor solutions available, but most are difficult and costly to deploy and maintain for remote call center agents. Tokens and other security devices must be provisioned and mailed to remote agents then replaced if lost of broken. Certificates can be hard to support on hardware that is not company-owned and maintained. Weaker security methods, like security questions, don’t stand up to the scrutiny of a compliance audit.</p>
<p><strong>Telephones As A Security Device?</strong><br />
Particularly well suited for use with remote call center agents is a method of two-factor authentication that uses a simple phone call as the second form of authentication. The agent logs in just like they normally would with a user name and password, and instantly their phone rings. They answer and press # or enter a PIN to complete their login. If the agent is not logging in when they receive a call, they know that their user name and password have been compromised and can press the fraud alert option to block access and alert the I.T. team back at the corporate office. </p>
<p>Because the second factor of authentication occurs across a second network (the public telephone network), there is a significantly enhanced level of security. Both the agent’s internet connection and the public telephone network must be compromised simultaneously in order for the attacker to gain access using the agent’s account. </p>
<p><strong>Cost Savings</strong><br />
With phone-based authentication, there are no devices, software, or certificates to deploy and maintain – it works with the agent’s existing phone. Users require very little training and almost no ongoing support – making phone-based authentication significantly less expensive to setup and maintain than other two-factor solutions. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-faqs/what-is-the-role-of-user-authentication-in-pci-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What if I am not PCI compliant?</title>
		<link>http://www.pcicompliance.org/pci-compliance-faqs/what-if-i-am-not-pci-compliant/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-faqs/what-if-i-am-not-pci-compliant/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:55:31 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[PCI Compliance FAQs]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=22</guid>
		<description><![CDATA[Enforcement of compliance is done by the bodies holding relationships with the in-scope organisations. Thus, for organisations processing Visa or Mastercard transactions, compliance is enforced by the organisation&#8217;s acquirer, while organisations handling American Express transactions will deal directly with American Express for the purposes of compliance. In the case of third party suppliers such as [...]]]></description>
			<content:encoded><![CDATA[<p>Enforcement of compliance is done by the bodies holding relationships with the in-scope organisations. Thus, for organisations processing Visa or Mastercard transactions, compliance is enforced by the organisation&#8217;s acquirer, while organisations handling American Express transactions will deal directly with American Express for the purposes of compliance. In the case of third party suppliers such as hosting companies who have business relationships with in-scope organisations, enforcement of compliance falls to the in-scope company, as neither the acquirers nor the card brands will have appropriate contractual relationships in place to mandate compliance. Non-compliant companies who maintain a relationship with one or more of the card brands, either directly or through an acquirer risk losing their ability to process credit card payments and being audited and/or fined.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-faqs/what-if-i-am-not-pci-compliant/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What are the PCI DSS Requirements?</title>
		<link>http://www.pcicompliance.org/pci-compliance-faqs/what-are-the-pci-dss-requirements/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-faqs/what-are-the-pci-dss-requirements/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:50:40 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[PCI Compliance FAQs]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=14</guid>
		<description><![CDATA[The current version of the standard (1.2) specifies 12 requirements for compliance, organized into six logically related groups, which are called &#8220;control objectives.&#8221;
Control Objectives PCI DSS Requirements


Build and Maintain a Secure Network
 1. Install and maintain a firewall configuration to protect cardholder data
2. Do not use vendor-supplied defaults for system passwords and other security parameters



Protect [...]]]></description>
			<content:encoded><![CDATA[<p>The current version of the standard (1.2) specifies 12 requirements for compliance, organized into six logically related groups, which are called &#8220;control objectives.&#8221;</p>
<p><strong>Control Objectives PCI DSS Requirements</strong></p>
<table cellpadding="5">
<tr>
<td style="vertical-align: top; text-align: left">Build and Maintain a Secure Network</td>
<td> 1. Install and maintain a firewall configuration to protect cardholder data<br />
2. Do not use vendor-supplied defaults for system passwords and other security parameters
</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left">Protect Cardholder Data</td>
<td>3. Protect stored cardholder data<br />
4. Encrypt transmission of cardholder data across open, public networks</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left">Maintain a Vulnerability Management Program</td>
<td>5. Use and regularly update anti-virus software on all systems commonly affected by malware<br />
6. Develop and maintain secure systems and applications</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left">Implement Strong Access Control Measures</td>
<td>7. Restrict access to cardholder data by business need-to-know<br />
8. Assign a unique ID to each person with computer access<br />
9. Restrict physical access to cardholder data</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left">Regularly Monitor and Test Networks</td>
<td>10. Track and monitor all access to network resources and cardholder data<br />
11. Regularly test security systems and processes</td>
</tr>
<tr>
<td style="vertical-align: top; text-align: left">Maintain an Information Security Policy</td>
<td>12. Maintain a policy that addresses information security</td>
</tr>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-faqs/what-are-the-pci-dss-requirements/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What is the Payment Card Industry (PCI) Data Security Standard?</title>
		<link>http://www.pcicompliance.org/pci-compliance-faqs/what-is-the-payment-card-industry-pci-data-security-standard/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-faqs/what-is-the-payment-card-industry-pci-data-security-standard/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:44:10 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[PCI Compliance FAQs]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=12</guid>
		<description><![CDATA[The Payment Card Industry Data Security Standard is a worldwide information security standard assembled by the Payment Card Industry Security Standards Council (PCI SSC). The standard was created to help organizations that process card payments prevent credit card fraud through increased controls around data and its exposure to compromise. The standard applies to all organizations [...]]]></description>
			<content:encoded><![CDATA[<p>The Payment Card Industry Data Security Standard is a worldwide information security standard assembled by the Payment Card Industry Security Standards Council (PCI SSC). The standard was created to help organizations that process card payments prevent credit card fraud through increased controls around data and its exposure to compromise. The standard applies to all organizations which hold, process, or pass cardholder information from any card branded with the logo of one of the card brands.</p>
<p>The standard is maintained by the Payment Card Industry Security Standards Council, which maintains both the PCI DSS and a number of other standards, such as the Payment Card Industry PIN Entry Device security requirements (PCI PED) and the Payment Application Data Security Standard (PA-DSS).</p>
<p>Validation of compliance can be performed either internally or externally, depending on the volume of card transactions the organisation is handling, but regardless of the size of the organisation, compliance must be assessed annually. Organisations handling large volumes of transactions must have their compliance assessed by an independent assessor known as a Qualified Security Assessor (QSA), while companies handling smaller volumes have the option of self-certification via a Self-Assessment Questionnaire (SAQ). In some regions these SAQs still require signoff by a QSA for submission.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-faqs/what-is-the-payment-card-industry-pci-data-security-standard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>West At Home Implements PhoneFactor for PCI Compliance</title>
		<link>http://www.pcicompliance.org/pci-compliance-case-studies/west-at-home-implements-phonefactor-for-pci-compliance/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-case-studies/west-at-home-implements-phonefactor-for-pci-compliance/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:38:40 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=7</guid>
		<description><![CDATA[West At Home Increases Credit Card Data Security With PhoneFactor
The Business Challenge:
West At Home, a division of West Corporation, is the nation&#8217;s leading provider of outsourced communication solutions.  They are based in the Midwest, but have thousands of agents across the United States that work from home taking calls from consumers &#8211; processing orders [...]]]></description>
			<content:encoded><![CDATA[<p><strong>West At Home Increases Credit Card Data Security With PhoneFactor</strong></p>
<p><strong>The Business Challenge:</strong></p>
<p>West At Home, a division of West Corporation, is the nation&#8217;s leading provider of outsourced communication solutions.  They are based in the Midwest, but have thousands of agents across the United States that work from home taking calls from consumers &#8211; processing orders or providing customer service and support to West clients from a wide range of industries, including retail, healthcare, communications, and travel/hospitality. This means that any information that the agents enter into their computers via their remote network must remain secure to protect the consumer&#8217;s personal and payment information, which required compliance with the PCI Data Security Standards.  West, like many call centers, faced certain challenges in maintaining this security.</p>
<ul>
<li> <strong>Strict Industry Regulations:</strong> Because agents often take credit card information, West had to follow industry regulations like PCI DSS, which requires two-factor authentication to secure access to networks where credit cards are processed or stored. But depending on the particular industry focus the agents had at any time, they might also have to comply with HIPAA or FFIEC regulations, among others.</li>
<li> <strong>Use of Personal Computers:</strong> Because these agents work from home on their own equipment, requiring users to install software or certificates on their personal computers would require a material amount of IT support and ongoing maintenance.<strong> </strong></li>
<li> <strong>Employee Turnover:</strong> The call center industry typically experiences a heavy turnover. Any solution had to be one that was easy for the home agents to implement, and very streamlined for West IT to deploy and maintain.</li>
</ul>
<p><strong>The Solution:</strong></p>
<p>PhoneFactor understood West At Home&#8217;s issues.  Our secure two-factor authentication service provides everything they need while using the agent&#8217;s best tool of the trade &#8211; their phone.</p>
<ul>
<li> Easy setup and deployment &#8211; No tokens to mail or certificates to install</li>
<li> Rapid compliance with PCI, FFIEC, HIPAA and other industry regulations</li>
<li> Instant integration with leading remote access products</li>
<li> Centralized user management leveraging their existing Active Directory</li>
</ul>
<p>PhoneFactor integrates with West&#8217;s existing systems, enabling rapid setup and deployment. And because it synchronizes with their Active Directory, provisioning and managing users is seamless.  PhoneFactor is so easy that training is accomplished through an automated email.  And PhoneFactor is significantly cheaper than other two-factor solutions on the market that meet the compliance guidelines necessary for West.</p>
<p><em>&#8220;The PhoneFactor solution gives us the strong two-factor authentication that we need to meet the industry&#8217;s strict regulatory requirements. PhoneFactor fit all of our requirements and gave us a great alternative to costly security token solutions.&#8221;  &#8211; Rachel Roberts, Information Services Project Manager, West Corporation</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-case-studies/west-at-home-implements-phonefactor-for-pci-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Webcast: PCI DSS Compliance In Action: Regis Corporation</title>
		<link>http://www.pcicompliance.org/pci-compliance-events/webcast-pci-dss-compliance-in-action-regis-corporation/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-events/webcast-pci-dss-compliance-in-action-regis-corporation/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:35:22 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[Events]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=5</guid>
		<description><![CDATA[Are you charged with the daunting task of managing your company&#8217;s PCI DSS (Payment Card Industry Data Security Standard) compliance? If so, don&#8217;t miss this TechRepublic Webcast with real-world stories from industry leaders.
Hosted by James Hilliard for TechRepublic and featuring guest speakers Steve Dispensa, Data Security Expert, CTO and co-founder of PhoneFactor and Bernie Rominski, [...]]]></description>
			<content:encoded><![CDATA[<p>Are you charged with the daunting task of managing your company&#8217;s PCI DSS (Payment Card Industry Data Security Standard) compliance? If so, don&#8217;t miss this TechRepublic Webcast with real-world stories from industry leaders.</p>
<p>Hosted by James Hilliard for TechRepublic and featuring guest speakers <strong>Steve Dispensa, Data Security Expert, CTO and co-founder of PhoneFactor</strong> and <strong>Bernie Rominski, IT Security Officer at Regis Corporation</strong>, the world&#8217;s largest operator of hair salons, this Webcast will explore the challenges of meeting compliance requirements, particularly those related to user authentication. Join the Webcast to learn:</p>
<ul>
<li>The basic history of and requirements for PCI DSS compliance</li>
<li>The unique challenges companies face in implementing stronger user authentication</li>
<li>How PhoneFactor, a simple phone-based two-factor authentication system, helped Regis enable rapid, cost effective compliance with two-factor requirements</li>
</ul>
<h4>Register Now for this Free PCI Compliance Webcast</h4>
<div class="wpcf7" id="wpcf7-f1-p5-o1">
<form action="/feed/#wpcf7-f1-p5-o1" method="post" class="wpcf7-form">
<div style="display: none;"><input type="hidden" name="_wpcf7" value="1" /><input type="hidden" name="_wpcf7_version" value="1.10.0.1" /><input type="hidden" name="_wpcf7_unit_tag" value="wpcf7-f1-p5-o1" /></div>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td>First Name:</td>
<td><span class="wpcf7-form-control-wrap first-name"><input type="text" name="first-name" value="" class="wpcf7-validates-as-required" size="20" /></span> </td>
<td>Last Name:</td>
<td><span class="wpcf7-form-control-wrap last-name"><input type="text" name="last-name" value="" class="wpcf7-validates-as-required" size="20" /></span> </td>
</tr>
<tr>
<td>Phone Number:</td>
<td><span class="wpcf7-form-control-wrap phone"><input type="text" name="phone" value="" class="wpcf7-validates-as-required" size="20" /></span> </td>
<td>Email:</td>
<td>
<span class="wpcf7-form-control-wrap email"><input type="text" name="email" value="" class="wpcf7-validates-as-email wpcf7-validates-as-required" size="20" /></span> </td>
</tr>
<tr>
<td>Job Title:</td>
<td><span class="wpcf7-form-control-wrap job-title"><input type="text" name="job-title" value="" class="wpcf7-validates-as-required" size="20" /></span> </td>
<td>Company:</td>
<td><span class="wpcf7-form-control-wrap company"><input type="text" name="company" value="" class="wpcf7-validates-as-required" size="20" /></span> </td>
</tr>
<tr>
<td>Number of Employees:</td>
<td><span class="wpcf7-form-control-wrap employees"><select name="employees" class="wpcf7-validates-as-required"><option value="---">---</option><option value="1-50">1-50</option><option value="51-100">51-100</option><option value="101-250">101-250</option><option value="251-1000">251-1000</option><option value="1001-5000">1001-5000</option><option value="5000+">5000+</option></select></span></td>
<td>State</td>
<td><span class="wpcf7-form-control-wrap state"><input type="text" name="state" value="" class="wpcf7-validates-as-required" size="20" /></span> </td>
</tr>
<tr>
<td colspan="4"><strong><em>All fields are required.</em></strong</td>
</tr>
<tr>
<td>&nbsp;</td>
<td colspan="3"><input type="submit" value="Send" /> <img class="ajax-loader" style="visibility: hidden;" alt="ajax loader" src="http://www.pcicompliance.org/wp-content/plugins/contact-form-7/images/ajax-loader.gif" /></td>
</tr>
</table>
<div class="wpcf7-response-output wpcf7-display-none"></div>
</form>
</div>

]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-events/webcast-pci-dss-compliance-in-action-regis-corporation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update to PCI Compliance Standards Published</title>
		<link>http://www.pcicompliance.org/pci-compliance-news/update-to-pci-compliance-standards-published/</link>
		<comments>http://www.pcicompliance.org/pci-compliance-news/update-to-pci-compliance-standards-published/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:31:02 +0000</pubDate>
		<dc:creator>sfender@phonefactor.com</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[pci compliance 1.2]]></category>
		<category><![CDATA[pci dss]]></category>
		<category><![CDATA[pci dss 1.2]]></category>
		<category><![CDATA[pci standards 1.2]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://www.pcicompliance.org/?p=3</guid>
		<description><![CDATA[Revisions to standard include clarifications and other subtle changes to ease
implementation

The PCI Security Standards Council (PCI SSC), a global, open industry standards body providing management of the Payment Card Industry Data Security Standard (PCI DSS), PIN Entry Device (PED) Security Requirements and the Payment Application Data Security Standard (PA-DSS), today announces general availability of version [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Revisions to standard include clarifications and other subtle changes to ease<br />
implementation<br />
</strong><br />
The PCI Security Standards Council (PCI SSC), a global, open industry standards body providing management of the Payment Card Industry Data Security Standard (PCI DSS), PIN Entry Device (PED) Security Requirements and the Payment Application Data Security Standard (PA-DSS), today announces general availability of version 1.2 of the PCI DSS. This latest version is the culmination of two years of feedback and suggestions from its industry stakeholders and is designed to clarify and ease implementation of the foremost standard for cardholder account security. Version 1.2 is effective immediately and version 1.1 of the standard will sunset on Dec. 31, 2008. The updated standard and supporting documentation is available on the Council’s Web site at <a href="https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml">https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml</a>.</p>
<p>The Council previously announced the summary of changes between version 1.1 and version 1.2 to ensure awareness of the coming latest changes to the standard. Version 1.2 includes clarifications and explanations of the requirements that improve flexibility to meet today’s security challenges and ensure organization’s can adequately comply with the standard. While version 1.2 does not introduce any new major requirements to the existing 12 in place since the Council’s inception, the updates do change some practices, such as the sun-setting of implementations of Wired Equivalent Privacy (WEP) wireless security by June, 2010.</p>
<p>“This latest revision to the PCI DSS is welcome news for merchants and service providers as they grapple with the latest security threats to their payment transactions systems,” said Diana Kelley, partner and analyst with SecurityCurve, a data security consultancy. “The clarifications and language revisions should go a long way in easing implementation questions and help to reduce compliance costs.”</p>
<p>Since the Council’s inception in Sept. 2006 and the release of version 1.1 of the PCI SSC, its Participating Organizations and Board of Advisors have been providing feedback on the standard, with global industry input into the revisions. This follows the established lifecycle process that will ensure that the PCI DSS standard is revised and updated on a two year cycle. Participating Organizations are given the opportunity to receive early drafts of all pending revisions to the Council’s standards and provide a bulk of the feedback during this process. PCI DSS version 1.2 was the primary discussion topic at the Council’s recently concluded and successful community meeting in Orlando, Fla., in which more than 500 attendees came together to begin the process of strengthening the standards even further.</p>
<p>“It is especially gratifying to know that version 1.2 of the PCI DSS is inclusive of global industry feedback,” said Bob Russo, general manager, PCI Security Standards Council. “This ensures that we continue to offer merchants and service providers a pathway to protect cardholder account data that is sensible and achievable.”</p>
<p>For More Information:<br />
More information on the PCI Security Standards Council and becoming a Participating Organization please visit pcisecuritystandards.org, or contact the PCI Security Standards Council at <a href="mailto:participation@pcisecuritystandards.org">participation@pcisecuritystandards.org</a>.</p>
<p>About the PCI Security Standards Council<br />
The mission of the PCI Security Standards Council is to enhance payment account security by driving education and awareness of the PCI Data Security Standard and other standards that increase payment data security.</p>
<p>The PCI Security Standards Council was formed by the major payment card brands American Express, Discover Financial Services, JCB International, MasterCard Worldwide and Visa Inc. to provide a transparent forum in which all stakeholders can provide input into the ongoing development, enhancement and dissemination of the PCI Data Security Standard (DSS), PIN Entry Device (PED) Security Requirements and the Payment Application Data Security Standard (PA-DSS). Merchants, banks, processors and other vendors are encouraged to join as Participating Organizations.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.pcicompliance.org/pci-compliance-news/update-to-pci-compliance-standards-published/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
