Payment Card Industry Data Security Standard
||The examples and perspective in this article deal primarily with the United States and do not represent a worldwide view of the subject. (August 2012)|
The Payment Card Industry Data Security Standard (PCI DSS) is a proprietary information security standard for organizations that handle cardholder information for the major debit, credit, prepaid, e-purse, ATM, and POS cards.
Defined by the Payment Card Industry Security Standards Council, the standard was created to increase controls around cardholder data to reduce credit card fraud via its exposure. Validation of compliance is done annually — by an external Qualified Security Assessor (QSA) that creates a Report on Compliance (ROC) for organizations handling large volumes of transactions, or by Self-Assessment Questionnaire (SAQ) for companies handling smaller volumes.
- 1 Requirements
- 2 History
- 3 Updates and supplemental information
- 4 Compliance versus validation of compliance
- 5 Mandated compliance
- 6 How to get started
- 7 Compliance and wireless LANs
- 8 PCI compliance in call centers
- 9 Controversies and criticisms
- 10 See also
- 11 References
- 12 Articles on PCI compliance using Linux
- 13 Books on PCI DSS
- 14 Updates on PCI DSS v1.2
- 15 Updates on PCI DSS v2.0
- 16 External links
The current version of the standard is version 3.0, released on 7 November 2013. PCI DSS version 2.0 must be adopted by all organizations with payment card data by 1 January 2011, and from 1 January 2012 all assessments must be against version 2.0 of the standard. PCI DSS version 2.0 has two new or evolving requirements out of 132 changes. The remaining changes and enhancements fall under the categories of clarification or additional guidance. The table below summarizes the differing points from version 1.2 of 1 October 2008 and specifies the 12 requirements for compliance, organized into six logically related groups, which are called “control objectives”.
|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 Cardholder Data||3. Protect stored cardholder data|
|4. Encrypt transmission of cardholder data across open, public networks|
|Maintain a Vulnerability Management Program||5. Use and regularly update anti-virus software on all systems commonly affected by malware|
|6. Develop and maintain secure systems and applications|
|Implement Strong Access Control Measures||7. Restrict access to cardholder data by business need-to-know|
|8. Assign a unique ID to each person with computer access|
|9. Restrict physical access to cardholder data|
|Regularly Monitor and Test Networks||10. Track and monitor all access to network resources and cardholder data|
|11. Regularly test security systems and processes|
|Maintain an Information Security Policy||12. Maintain a policy that addresses information security|
PCI DSS originally began as five different programs: Visa Card Information Security Program, MasterCard Site Data Protection, American Express Data Security Operating Policy, Discover Information and Compliance, and the JCB Data Security Program. Each company’s intentions were roughly similar: to create an additional level of protection for card issuers by ensuring that merchants meet minimum levels of security when they store, process and transmit cardholder data. The Payment Card Industry Security Standards Council (PCI SSC) was formed, and on 15 December 2004, these companies aligned their individual policies and released the Payment Card Industry Data Security Standard (PCI DSS).
In September 2006, the PCI standard was updated to version 1.1 to provide clarification and minor revisions to version 1.0.
Version 1.2 was released on October 1, 2008. Version 1.1 "sunsetted" on December 31, 2008. v1.2 did not change requirements, only enhanced clarity, improved flexibility, and addressed evolving risks/threats. In August 2009 the PCI SSC announced the move from version 1.2 to version 1.2.1 for the purpose of making minor corrections designed to create more clarity and consistency among the standards and supporting documents.
Updates and supplemental information
The PCI SSC has released several supplemental pieces of information to clarify various requirements. These documents include the following
- Information Supplement: Requirement 11.3 Penetration Testing
- Information Supplement: Requirement 6.6 Code Reviews and Application Firewalls Clarified
- Navigating the PCI DSS - Understanding the Intent of the Requirements
- Information Supplement: PCI DSS Wireless Guidelines
Compliance versus validation of compliance
Although the PCI DSS must be implemented by all entities that process, store or transmit cardholder data, formal validation of PCI DSS compliance is not mandatory for all entities. Currently both Visa and MasterCard require Merchants and Service Providers to be validated according to the PCI DSS. Smaller merchants and service providers are not required to explicitly validate compliance with each of the controls prescribed by the PCI DSS although these organizations must still implement all controls in order to maintain safe harbour and avoid potential liability in the event of fraud associated with theft of cardholder data. Issuing banks are not required to go through PCI DSS validation although they still have to secure the sensitive data in a PCI DSS compliant manner. Acquiring banks are required to comply with PCI DSS as well as to have their compliance validated by means of an audit. (In the event of a security breach, any compromised entity which was not PCI DSS compliant at the time of breach will be subject to additional card scheme penalties, such as fines.)
In 2009 the U.S. state of Nevada incorporated the standard into state law, requiring compliance of merchants doing business in that state with the current PCI DSS, and shields compliant entities from liability.
How to get started
Document cardholder data flow - One of the first steps in PCI compliance is to document flow of the cardholder data. Cardholder data flows between and through applications, systems, and network infrastructure devices. It is very important to document all cardholder data flows prior to beginning any assessment activities. An inventory of some kind should be developed to identify all systems that store, process or transmit cardholder data.
Develop a system inventory - An inventory of all systems that store, process, and/or transmit cardholder data must be maintained. The following information at a minimum should be maintained in the inventory:
- System name
- Cardholder data stored (list fields)
- Reason for storage
- Retention period
- Protection mechanism (e.g., hashing, encryption, or truncation)
It is to be noted that when you are developing your system inventory you should divide the applications and system components in categories for scoping purposes.
Category 1 Applications and System Components: Applications and systems that directly store, process, or transmit cardholder data are located on the same network as said applications and systems
Category 2 System Components: System components that support the Tier 1 environment (i.e., Active Directory, NTP, DNS, Anti-virus, patching servers, etc.)
Category 3 System Components: All other non-Tier 1 and Tier 2 system components
Compliance and wireless LANs
In July 2009, the Payment Card Industry Security Standards Council published wireless guidelines for PCI DSS recommending the use of wireless intrusion prevention system (WIPS) to automate wireless scanning for large organizations. Wireless guidelines clearly define how wireless security applies to PCI DSS 1.2 compliance.
These guidelines apply to the deployment of wireless LAN (WLAN) in Cardholder Data Environments, also known as CDEs. A CDE is defined as a network environment that possesses or transmits credit card data.
Wireless LAN and CDE classification
PCI DSS wireless guidelines classify CDEs into three scenarios depending on how wireless LANs are deployed.
- No Known WLAN AP inside or outside the CDE: The organization has not deployed any WLAN AP. In this scenario, 3 minimum scanning requirements (Sections 11.1, 11.4 and 12.9) of the PCI DSS apply.
- Known WLAN AP outside the CDE: The organization has deployed WLAN APs outside the CDE. These WLAN APs are segmented from the CDE by a firewall. There are no known WLAN APs inside the CDE. In this scenario, 3 minimum scanning requirements (Sections 11.1, 11.4 and 12.9) of the PCI DSS apply.
- Known WLAN AP inside the CDE: The organization has deployed WLAN APs inside the CDE. In this scenario, three minimum scanning requirements (Sections 11.1, 11.4 and 12.9), as well as six secure deployment requirements (Sections 2.1.1, 4.1.1, 9.1.3, 10.5.4, 10.6 and 12.3) of the PCI DSS apply.
Key sections of PCI DSS 1.2 that are relevant for wireless security are classified and defined below.
Secure deployment requirements for wireless LANs
These secure deployment requirements apply to only those organizations that have a known WLAN AP inside the CDE. The purpose of these requirements is to deploy WLAN APs with proper safeguards.
- Section 2.1.1 Change Defaults: Change default passwords, SSIDs on wireless devices. Enable WPA or WPA2 security.
- Section 4.1.1 802.11i Security: Set up APs in WPA or WPA2 mode with 802.1X authentication and AES encryption. Use of WEP in CDE is not allowed after June 30, 2010.
- Section 9.1.3 Physical Security: Restrict physical access to known wireless devices.
- Section 10.5.4 Wireless Logs: Archive wireless access centrally using a WIPS for 1 year.
- Section 10.6 Log Review: Review wireless access logs daily.
- Section 12.3 Usage Policies: Develop usage policies to list all wireless devices regularly. Develop usage possible for the use of wireless devices.
Minimum scanning requirements for wireless LANs
These minimum scanning requirements apply to all organizations regardless of the type of wireless LAN deployment in the CDE. The purpose of these requirements is to eliminate any rogue or unauthorized WLAN activity inside the CDE.
- Section 11.1 Quarterly Wireless Scan: Scan all sites with CDEs whether or not they have known WLAN APs in the CDE. Sampling of sites is not allowed. A WIPS is recommended for large organizations since it is not possible to manually scan or conduct a walk-around wireless security audit of all sites on a quarterly basis
- Section 11.4 Monitor Alerts: Enable automatic WIPS alerts to instantly notify personnel of rogue devices and unauthorized wireless connections into the CDE.
- Section 12.9 Eliminate Threats: Prepare an incident response plan to monitor and respond to alerts from the WIPS. Enable automatic containment mechanism on WIPS to block rogues and unauthorized wireless connections.
Wireless intrusion prevention system (WIPS) implementations
Wireless intrusion prevention systems are a possible option for compliance with some PCI DSS requirements, and can be implemented in either an internally hosted or externally hosted software as a service(SaaS) model.
The hosted implementation is offered in an on-demand, subscription-based SaaS model. Hosted implementations are said to be particularly cost-effective for organizations looking to fulfill only the minimum scanning requirements for PCI DSS compliance.
The network implementation is an on-site deployment of WIPS within a private network. Such a deployment is viable, but the significant costs have been thought to lead some companies to avoid WIPS deployments.
PCI compliance in call centers
While the PCI DSS standards are very explicit about the requirements for the back end storage and access of PII (personally identifiable information), the Payment Card Industry Security Standards Council has said very little about the collection of that information on the front end, whether through websites, interactive voice response systems or call center agents. This is surprising, given the high threat potential for credit card fraud and data compromise that call centers pose.
In a call center, customers read their credit card information, CVV codes, and expiration dates to call center agents. There are few controls which prevent the agent from skimming (credit card fraud) this information with a recording device or a computer or physical note pad. Moreover, almost all call centers deploy some kind of call recording software, which is capturing and storing all of this sensitive consumer data. These recordings are accessible by a host of call center personnel, are often unencrypted, and generally do not fall under the PCI DSS standards outlined here. Home-based telephone agents pose an additional level of challenges, requiring the company to secure the channel from the home-based agent through the call center hub to the retailer applications.
To address some of these concerns, on January 22, 2010 the Payment Card Industry Security Standards Council issued a revised FAQ about call center recordings. The bottom line is that companies can no longer store digital recordings that include CVV information if those recordings can be queried.
Though the council has not yet issued any requirements, technology solutions can completely prevent skimming (credit card fraud) by agents. At the point in the transaction where the agent needs to collect the credit card information, the call can be transferred to an Interactive Voice Response system. This protects the sensitive information, but can create an awkward customer interaction. Solutions such as Agent-assisted Automation allow the agent to "collect" the credit card information without ever seeing or hearing it. The agent remains on the phone and customers enter their credit card information directly into the customer relationship management software using their phones. The DTMF tones are converted to monotones so the agent cannot recognize them and so that they cannot be recorded. This also ensures a greater level of customer satisfaction as callers understand the security benefits, thereby improving the business-consumer relationship. PCI compliant solutions can be deployed easily within company premises, or through the telephony provider network cloud. If going through the network cloud, no hardware or software needs to be installed in the organization itself. This ensures seamless integration with the call center environment, with minimal disruption to agents, or current IT systems, whilst also reducing risk by enabling rapid implementation. The benefits of increasing the security around the collection of personally identifiable information goes beyond credit card fraud to include helping merchants win chargebacks due to friendly fraud.
Controversies and criticisms
It has been suggested by some IT security professionals that the PCI DSS does little more than provide a minimal baseline for security.
"The fact is you can be PCI-compliant and still be insecure. Look at online application vulnerabilities. They're arguably the fastest growing area of security, and for good reason — exposures in customer-facing applications pose a real danger of a security breach." - Greg Reber
PCI-DSS has been called a “near scam” by a spokesman for the National Retail Federation and others who say it’s designed less to secure card data than to profit credit card companies while giving them executive powers of punishment through a mandated compliance system that has no oversight.
According to Stephen and Theodora “Cissy” McComb, owners of Cisero’s Ristorante and Nightclub in Park City, Utah (which was fined for a breach that two forensics firms could not find evidence even occurred), "the PCI system is less a system for securing customer card data than a system for raking in profits for the card companies via fines and penalties. Visa and MasterCard impose fines on merchants even when there is no fraud loss at all, simply because the fines “are profitable to them,”".
Additionally, Michael Jones, CIO of Michaels' Stores, testifying before a U.S. Congress subcommittee regarding the PCI DSS, says "(...the PCI DSS requirements...) are very expensive to implement, confusing to comply with, and ultimately subjective, both in their interpretation and in their enforcement. It is often stated that there are only twelve “Requirements” for PCI compliance. In fact there are over 220 sub-requirements; some of which can place an incredible burden on a retailer and many of which are subject to interpretation."
In contrast, others have suggested that PCI DSS is a step toward making all businesses pay more attention to IT security, even if minimum standards are not enough to completely eradicate security problems.
"Regulation--SOX, HIPAA, GLBA, the credit-card industry's PCI, the various disclosure laws, the European Data Protection Act, whatever--has been the best stick the industry has found to beat companies over the head with. And it works. Regulation forces companies to take security more seriously, and sells more products and services." - Bruce Schneier
Further, per PCI Council General Manager Bob Russo's response to the National Retail Federation: PCI is a structured "blend...[of] specificity and high-level concepts" that allows "stakeholders the opportunity and flexibility to work with Qualified Security Assessors (QSAs) to determine appropriate security controls within their environment that meet the intent of the PCI standards."
Compliance and compromises
According to Visa Chief Enterprise Risk Officer, Ellen Richey, "...no compromised entity has yet been found to be in compliance with PCI DSS at the time of a breach." However, it has nevertheless become a common misconception that companies have had security breaches while also being PCI DSS compliant. Much of this confusion is a result of the 2008 Heartland Payment Systems breach, wherein more than one hundred million card numbers were compromised. Around this same time Hannaford Brothers and TJX Companies were similarly breached as a result of the alleged very same source of coordinated efforts of Albert "Segvec" Gonzalez and two unnamed Russian hackers.
Assessments examine the compliance of merchants and services providers with the PCI DSS at a specific point in time and frequently utilize a sampling methodology to allow compliance to be demonstrated through representative systems and processes. It is the responsibility of the merchant and service provider to achieve, demonstrate, and maintain their compliance at all times both throughout the annual validation/assessment cycle and across all systems and processes in their entirety. Therefore, these frequently cited breaches and their pointed use as a tool for criticism even to the point of noting that Hannaford Brothers had, in fact, received its PCI DSS compliance validation one day after it had been made aware of a two-month long compromise of its internal systems; fail to appropriately assign blame in their blasting of the standard itself as flawed as opposed to the more truthful breakdown in merchant and service provider compliance with the written standard, albeit in this case having not been identified by the assessor.
Other, more substantial, criticism lies in that compliance validation is required only for Level 1-3 merchants and may be optional for Level 4 depending on the card brand and acquirer. Visa's compliance validation details for merchants state that level 4 merchants compliance validation requirements are set by the acquirer, Visa level 4 merchants are "Merchants processing less than 20,000 Visa e-commerce transactions annually and all other merchants processing up to 1 million Visa transactions annually". At the same time 80% of payment card compromises since 2005 affected Level 4 merchants.
Compliance as a snapshot
The state of being PCI DSS compliant might appear to have some temporal persistence, at least from a merchant point of view. In contrast, the PCI Standards Council General Manager Bob Russo has indicated that liabilities could change depending on the state of a given organization at the point in time when an actual breach occurs.
- "PCI Compliance Frequently Asked Questions". Dell SecureWorks.
- Sidel, Robin (2007-09-22). "In Data Leaks, Culprits Often Are Mom, Pop". The Wall Street Journal.
- Johnson, Katie W. (18 November 2013). "PCI Security Standards Council Releases New Versions of Two Security Standards". The Bureau of National Affairs, Bloomberg. Retrieved 2013-11-25.
- Silverstone, Ariel. "PCI DSS, 2.0, | The Security Blog". The Security Blog. Ariel Silvertone. Retrieved 11 December 2011.
- PCI DSS - PCI Security Standards Council
- PCI SECURITY STANDARDS COUNCIL RELEASES VERSION 1.2 OF PCI DATA SECURITY STANDARD
- Supporting Documents PCI DSS
- Information Supplement: Requirement 11.3 Penetration Testing
- Information Supplement: Requirement 6.6 Code Reviews and Application Firewalls Clarified
- Navigating the PCI DSS - Understanding the Intent of the Requirements
- "PCI DSS Wireless Guidelines". Retrieved 2009-07-16.
- Nevada Revised Statutes, Chap. 603A §215.
- "Don’t Let Wireless Detour your PCI Compliance". Retrieved 2009-07-22.
- Payment Card Industry (PCI) Data Security Standard Glossary, Abbreviations and Acronyms
- "Walk Around Wireless Security Audits – The End Is Near". Retrieved 2009-07-22.
- "Webinar on Wireless Security as SaaS by Gartner Analyst John Pescatore". gartner.com. Retrieved 2009-04-24.
- "Saas offerings for wireless pci compliance". Retrieved 2010-05-25.
- "Security SaaS hits WLAN community". networkworld.com. Retrieved 2008-04-07.
- "Big-Time Wireless Security - As a Service". networkworld.com. Retrieved 2008-04-08.
- Little, Allan (March 19, 2009). "Overseas credit card scam exposed". bbc.co.uk.com.
- Loviglio, Joann (March, 2012). "If Microsoft co-founder's ID isn't safe, is yours?". msnbc.com.
- "PCI Compliance in the Call Center a Headache for Many". searchcrm.com. Retrieved 2011-01-28.
- "PCI Compliance: What it Means to the Call Center Industry". tmcnet.com. Retrieved 2008-02-13.
- "Call Center FAQ Significantly Changes". pciguru. Retrieved 2010-01-25.
- "Restructuring the Contact Center for PCI Compliance". tmcnet.com. Retrieved 2008-11-10.
- Adsit, Dennis (February 21, 2011). "Error-proofing strategies for managing call center fraud". isixsigma.com (iSixSigma (Ideal Media, LLC)).
- Reber, Greg (2008-10-27). "PCI compliance falls short of assuring website security". Tech Target. Retrieved 2009-02-15.
- Zetter, Kim (January 11, 2012). "Rare Legal Fight Takes On Credit Card Company Security Standards and Fines". Wired Magazine. Retrieved January 16, 2012.
- Jones, Michael (2009-03-31). "TESTIMONY OF MICHAEL JONES BEFORE THE EMERGING THREATS, CYBERSECURITY, AND SCIENCE AND TECHNOLOGY SUBCOMMITTEE". Congress of the United States. Retrieved 2010-07-19.[dead link]
- "Bruce Schneier reflects on a decade of security trends". Retrieved 2009-02-15.
- Russo, Bob (2009-06-15). "Letter to NRF". PCI Council. Retrieved 2010-10-19.
- Vijayan, Jaikumar (2009). "Visa: Post-breach criticism of PCI standard misplaced".
- "Heartland data breach sparks security concerns in payment industry".
- McGlasson, Linda (2008-04-04). "Hannaford Data Breach May Be Top of Iceberg". BankInfo Security. Retrieved 2009-01-28.
- Goodin, Dan (2009). "TJX suspect indicted in Heartland, Hannaford breaches".
- Spier, Peter (2010-03-22). "The QSA's Perspective: PCI Compliance Risk Abounds". BankInfo Security. Retrieved 2010-10-19.
- Vijayan, Jaikumar (2009-01-04). "PCI security standard gets ripped at House hearing". Computerworld Security. Retrieved 2009-05-04.
- Visa Merchant levels http://usa.visa.com/merchants/risk_management/cisp_merchants.html
- Pastor, Adrian (2009). "A Pentester’s Guide to Credit Card Theft Techniques".
- "Q and A: Head of PCI council sees security standard as solid, despite breaches". Retrieved 2009-02-15.
Articles on PCI compliance using Linux
- Red Card: Specificity of PCI DSS in respect to Red Hat Enterprise Linux (Part 1)
- Red Card: Specificity of PCI DSS in respect to Red Hat Enterprise Linux (Part 2)
- PCI DSS and Red Hat Enterprise Linux (Part #3)
- PCI DSS and Red Hat Enterprise Linux (Part #4)
- PCI DSS and Red Hat Enterprise Linux (Part #5)
- PCI DSS and Red Hat Enterprise Linux (Part #6)
- PCI DSS and Red Hat Enterprise Linux (Part #7)
- PCI DSS and Red Hat Enterprise Linux (Part #8)
- PCI DSS and Red Hat Enterprise Linux (Final part #9)
Books on PCI DSS
- "PCI DSS Handbook"(ISBN 9780470260463)
- "PCI DSS: A Practical Guide to Implementation" (ISBN 9781849280235)
- "PCI Compliance: Understand and Implement Effective PCI Data Security Standard Compliance" (ISBN 9781597494991)
Updates on PCI DSS v1.2
Updates on PCI DSS v2.0
- Summary of Changes
- PCI DSS 2.0 Announcement, Aug. 12, 2010
- PCI DSS Virtualisation Guidelines, June 2011