pci fs data storage


1 AT A GLANCE PCI DATA STORAGE PCI Data Storage Do’s and Don’ts Requirement 3 of the Payment Card Industry’s Data Security Standard (PCI DSS) is to “protect stored cardholder data.” The public assumes merchants and financial institutions will protect data on payment cards to thwart theft and prevent unauthorized use. But merchants should take note: Requirement 3 applies only if cardholder data is stored . Merchants who do not store any cardholder data provide stronger automatically protection by having eliminated a key target for data thieves. For merchants who have a legitimate business reason to store cardholder data, it is important to understand what data elements PCI DSS allows them to store and what measures they must take to protect those data. To prevent unauthorized storage, only Council certified PIN entry devices and payment applications may be used. PCI DSS compliance is enforced by the major payment card brands who established the PCI DSS and the PCI Security Standards Council: American Express, Discover Financial Services, JCB International, MasterCard Worldwide and Visa Inc. PCI SSC FOunDERS Basic PCI Data Storage Guidelines for Merchants Cardholder data refers to any information contained on a customer’s payment card. The data is printed on either side of the card and is contained in digital format on the magnetic stripe embedded in the backside of the card. Some payment cards store data in chips embedded on the front side. The front side usually has the primary account number (PAN), cardholder name and expiration date. The magnetic stripe or chip holds these plus other sensitive data for authentication and authorization. In general, no payment card data should ever be stored by a merchant unless it’s necessary to meet the needs of the business. Sensitive data on the magnetic stripe or chip must never be stored. Only the PAN, expiration date, service code, or cardholder name may be stored, and merchants must use technical precautions for safe storage (see back of this fact sheet for a summary). The matrix below shows basic “do’s” and “don’ts” for data storage security. Data Do’s Data Don’ts Do not store cardholder data unless it’s absolutely Do understand where payment card data flows for necessary the entire transaction process Do verify that your payment card terminals comply Do not store sensitive authentication data with the PCI personal identification number (PIN) contained in the payment card’s storage chip or full PARTICIPATInG entry device (PED) security requirements magnetic stripe, including the printed 3-4 digit card ORGAnIzATIOnS validation code on the front or back of the payment card after authorization Merchants, Banks, Processors, Hardware and Software Developers Do verify that your payment applications comply Do not have PED terminals print out personally and Point-of-Sale Vendors with the Payment Application Data Security identifiable payment card data; printouts should be Standard (PA-DSS) truncated or masked Do retain (if you have a legitimate business need) Do not store any payment card data in payment cardholder data only if authorized, and ensure it’s card terminals or other unprotected endpoint protected devices, such as PCs, laptops or smart phones Do use strong cryptography to render unreadable Do not locate servers or other payment card cardholder data that you store, and use other system storage devices outside of a locked, fully- layered security technologies to minimize the risk secured and access-controlled room of exploits by criminals Do ensure that third parties who process your Do not permit any unauthorized people to access customers’ payment cards comply with PCI DSS, stored cardholder data PED and/or PA-DSS as applicable. Have clear access and password protection policies

2 PROTECT STORED Technical Guidelines for Stored Payment Card Data CARDhOlDER DATA PCI DSS Requirement 3 details technical guidelines for protecting stored cardholder data. Merchants should develop a data retention and storage policy that strictly limits storage amount and retention use Encryption time to that which is required for business, legal, and/or regulatory purposes. Encrypted data is unreadable and Sensitive authentication data must never be stored after authorization – even if this data is encrypted. unusable to a system intruder • Never store full contents of any track from the card’s magnetic stripe or chip (referred to as full without the property cryptographic track, track, track 1, track 2, or magnetic stripe data). If required for business purposes, the keys. See the PCI DSS Glossary for cardholder’s name, PAN, expiration date, and service code may be stored as long as they are more information: protected in accordance with PCI DSS requirements. www.pcisecuritystandards.org/pdfs/ pci_dss_glossary.pdf • Never store the card-validation code or value (three- or four-digit number printed on the front or back of a payment card used to validate card-not-present transactions). use Other Measures • Never store the personal identification number (PIN) or PIN Block. Be sure to mask PAN whenever Do not store cardholder data unless it is displayed. The first six and last four digits are the maximum number of digits that may be there is a legitimate business need; displayed. This requirement does not apply to those authorized with a specific need to see the full truncate or mask cardholder data if PAN, nor does it supersede stricter requirements in place for displays of cardholder data such as full PAN is not needed and do not on a point-of-sale receipt. send PAN in unencrypted emails, instant messages, chats, etc.. Technical Guidelines for PCI Data Storage use Compensating Controls as PCI DSS Protection Storage Alternatives Data Element Permitted Required Req. 3.4 If stored cardholder data cannot Primary Account Number be encrypted, consult PCI DSS Yes Yes Yes (PAN) Appendix B: Compensating 1 [1] No Yes Yes Cardholder Name Cardholder Data Controls and Appendix C: 1 1 Compensating Controls Worksheet. No Yes Yes Service Code 1 1 Yes No Yes Expiration Date Verify 3rd Party Compliance [3] N/A Full Magnetic Stripe Data N/A No Sensitive Approved PIN Entry Devices Authentication CAV2/CVC2/CVV2/CID No N/A N/A www.pcisecuritystandards.org/pin/ [2] Data pedapprovallist.html N/A PIN/PIN Block No N/A Validated Payment Applications [1] These data elements must be protected if stored in conjunction with the PAN. This protection should be https://www.pcisecuritystandards. per PCI DSS requirements for general protection of the cardholder data environment. Additionally, other org/security_standards/pa_dss. legislation (e.g., related to consumer personal data protection, privacy, identity theft, or data security) shtml may require specific protection of this data, or proper disclosure of a company’s practices if consumer- related personal data is being collected during the course of business. PCI DSS, however, does not apply if PANs are not stored, processed, or transmitted. [2] Sensitive authentication data must not be stored after authorization (even if encrypted). [3] Full track data from the magnetic stripe, magnetic stripe image on the chip, or elsewhere. Technical Guidelines for Protecting Stored Payment Card Data At a minimum, PCI DSS requires PAN to be rendered unreadable anywhere it is stored – including portable digital media, backup media, and in logs. Software solutions for this requirement may include one of the following: • One-way hash functions based on strong cryptography – also called hashed index, which displays only index data that point to records in the database where sensitive data actually reside. – removing a data segment, such as showing only the last four digits. Truncation • Index tokens and securely stored pads • – encryption algorithm that combines sensitive plain text data with a random key or “pad” that works only once. Strong cryptography – with associated key management processes and procedures. Refer to the • PCI DSS and PA-DSS Glossary of Terms, Abbreviations and Acronyms for the definition of “strong cryptography.” Some cryptography solutions encrypt specific fields of information stored in a database; others encrypt a singular file or even the entire disk where data is stored. If full-disk encryption is used, logical access must be managed independently of native operating system access control mechanisms. Decryption keys must not be tied to user accounts. Encryption keys used for encryption of cardholder data must be protected against both disclosure and misuse. All key management processes and procedures for keys used for encryption of cardholder data must be fully documented and implemented. For more details, see PCI DSS Requirement 3. © 2008 PCI Security Standards Council LLC. The intent of this document is to provide supplemental information, 10/08 which does not replace or supersede PCI SSC Security Standards or their supporting documents.

Related documents