Source: http://docplayer.net/2743824-Payment-card-industry-pci-data-security-standard-self-assessment-questionnaire-d-and-attestation-of-compliance.html
Timestamp: 2018-12-17 19:11:21
Document Index: 21273938

Matched Legal Cases: ['art 1', 'art 2', 'art 2', 'art 2', 'art 2', 'art 3', 'art 4', 'art 4', 'art 3', 'art 3', 'art 4', 'art 4', 'art 1', 'art 2', 'art 2', 'art 2', 'art 2', 'art 3', 'art 4', 'art 4', 'art 3', 'art 3', 'art 4', 'art 4']

1 Payment Card Industry (PCI) Data Security Standard Self-Assessment Questionnaire D and Attestation of Compliance All other Merchants and all SAQ-Eligible Service Providers Version 1.1 February 2008
2 Table of Contents PCI Data Security Standard: Related Documents... ii Before You Begin... iii Completing the Self-Assessment Questionnaire...iii PCI DSS Compliance - Completion Steps...iii Guidance for Exclusion of Certain, Specific Requirements...iv Attestation of Compliance, SAQ D Merchant Version... 1 Attestation of Compliance, SAQ D Service Provider Version... 5 Self-Assessment Questionnaire D... 9 Build and Maintain a Secure Network...9 Requirement 1: Install and maintain a firewall configuration to protect data...9 Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters...11 Protect Cardholder Data...13 Requirement 3: Protect stored cardholder data...13 Requirement 4: Encrypt transmission of cardholder data across open, public networks..15 Maintain a Vulnerability Management Program...16 Requirement 5: Use and regularly update anti-virus software or programs...16 Requirement 6: Develop and maintain secure systems and applications...16 Implement Strong Access Control Measures...19 Requirement 7: Restrict access to cardholder data by business need-to-know...19 Requirement 8: Assign a unique ID to each person with computer access...19 Requirement 9: Restrict physical access to cardholder data...20 Regularly Monitor and Test Networks...23 Requirement 10: Track and monitor all access to network resources and cardholder data23 Requirement 11: Regularly test security systems and processes...24 Maintain an Information Security Policy...26 Requirement 12: Maintain a policy that addresses information security for employees and contractors...26 PCI DSS Applicability for Hosting Providers Requirement A.1: Hosting providers protect cardholder data environment...29 Compensating Controls Appendix Compensating Controls for Requirement Compensating Controls Worksheet...31 Compensating Controls Worksheet Completed Example...32 PCI DSS SAQ D, v1.1, Table of Contents February 2008 Copyright 2008 PCI Security Standards Council LLC Page i
3 PCI Data Security Standard: Related Documents The following documents were created to assist merchants and service providers in understanding the PCI Data Security Standard and the PCI DSS SAQ. Document PCI Data Security Standard Navigating PCI DSS: Understanding the Intent of the Requirements PCI Data Security Standard: Self-Assessment Guidelines and Instructions PCI Data Security Standard: Self-Assessment Questionnaire A and Attestation PCI Data Security Standard: Self-Assessment Questionnaire B and Attestation PCI Data Security Standard: Self-Assessment Questionnaire C and Attestation PCI Data Security Standard: Self-Assessment Questionnaire D and Attestation PCI DSS Glossary, Abbreviations, and Acronyms Audience All merchants and service providers All merchants and service providers All merchants and service providers Merchants 1 Merchants 1 Merchants 1 Service providers and all other merchants 1 All merchants and service providers 1 To determine the appropriate Self-Assessment Questionnaire, see PCI Data Security Standard: Self- Assessment Guidelines and Instructions, Selecting the SAQ and Attestation That Best Apply To Your Organization. PCI DSS SAQ D, v1.1, PCI Data Security Standard: Related Documents February 2008 Copyright 2008 PCI Security Standards Council LLC Page ii
4 Before You Begin Completing the Self-Assessment Questionnaire SAQ D has been developed for all SAQ-eligible service providers, and for all merchants not meeting the descriptions of SAQs A-C as described briefly in the table below and fully in PCI DSS Self-Assessment Questionnaire Instructions and Guidelines. SAQ Validation Type Description SAQ 1 Card-not-present (e-commerce or mail/telephone-order) merchants, all cardholder data functions outsourced. This would never apply to faceto-face merchants. 2 Imprint-only merchants with no electronic cardholder data storage B 3 Stand-alone terminal merchants, no electronic cardholder data storage B 4 Merchants with POS systems connected to the Internet, no electronic cardholder data storage 5 All other merchants (not included in descriptions for SAQs A-C above) and all service providers defined by a payment brand as eligible to complete an SAQ. These merchants not meeting the criteria for SAQs A-C above and all service providers defined by a payment brand as being SAQ-eligible are defined as SAQ Validation Type 5, here and in the PCI DSS Self-Assessment Questionnaire Instructions and Guidelines. While many of the organizations completing SAQ D will need to validate compliance with every PCI DSS requirement, some organizations with very specific business models may find that some requirements do not apply. For example, a company that does not use wireless technology in any capacity would not be expected to validate compliance with the sections of the PCI DSS that are specific to wireless technology. See the guidance below for information about the exclusion of wireless technology and certain other, specific requirements. Each section of this questionnaire focuses on a specific area of security, based on the requirements in the PCI Data Security Standard. PCI DSS Compliance - Completion Steps 1. Complete the Self-Assessment Questionnaire (SAQ D) according to the instructions in the Self- Assessment Questionnaire Instructions and Guidelines. 2. Complete a clean vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV), and obtain evidence of a passing scan from the ASV. 3. Complete the Attestation of Compliance in its entirety. 4. Submit the SAQ, evidence of a passing scan, and the Attestation of Compliance, along with any other requested documentation, to your acquirer (for merchants) or to the payment brand or other requester (for service providers). A C D PCI DSS SAQ D, v1.1, Before You Begin February 2008 Copyright 2008 PCI Security Standards Council LLC Page iii
5 Guidance for Exclusion of Certain, Specific Requirements If you are required to answer SAQ D to validate your PCI DSS compliance, the following exceptions may be considered: The questions specific to wireless only need to be answered if wireless is present anywhere in your network (Requirements 1.3.8, 2.1.1, and 4.1.1). Note that Requirement 11.1 (use of wireless analyzer) must still be answered even if wireless is not in your network, since the analyzer detects any rogue or unauthorized devices that may have been added without the merchant s knowledge. The questions specific to custom applications and code (Requirements ) only need to be answered if your organization writes its own custom web applications. The questions specific to data centers (Requirements ), only need to be answered if you have a dedicated data center or server room. A data center is defined by PCI SSC as a dedicated, physically secure room or structure where information technology infrastructure (application servers, database servers, web servers, and/or network devices) is centrally housed, whose main purpose is to store, process, or transmit cardholder data. Data center may be synonymous with server room, network operations center (NOC), and co-location facilities at an ISP or hosting provider. PCI DSS SAQ D, v1.1, Before You Begin February 2008 Copyright 2008 PCI Security Standards Council LLC Page iv
6 Attestation of Compliance, SAQ D Merchant Version Instructions for Submission The merchant must complete this Attestation of Compliance as a declaration of the merchant s compliance status with the Payment Card Industry Data Security Standard (PCI DSS). Complete all applicable sections and refer to the submission instructions at PCI DSS Compliance Completion Steps in this document. Part 1. Qualified Security Assessor Company Information (if applicable) Company Name: Lead QSA Contact Name: Telephone: Title: Business Address: State/Province: Country: ZIP: URL: Part 2. Merchant Organization Information Company Name: Contact Name: Telephone: DBA(S): Title: Business Address: State/Province: Country: ZIP: URL: Part 2a. Type of merchant business (check all that apply): Retailer Telecommunication Grocery and Supermarkets Petroleum E-Commerce Mail/Telephone-Order Others (please specify): List facilities and locations included in PCI DSS review: Part 2b. Relationships Does your company have a relationship with one or more third-party service providers (e.g. gateways, web-hosting companies, airline booking agents, loyalty program agents, etc)? Yes No Does your company have a relationship with more than one acquirer? Yes No Part 2c. Transaction Processing Payment Application in use: Payment Application Version: Part 3. PCI DSS Validation PCI DSS SAQ D, v1.1, Attestation of Compliance, Merchant Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 1
7 Based on the results noted in the SAQ D dated (completion date), (Merchant Company Name) asserts the following compliance status (check one): Compliant: All sections of the PCI SAQ are complete, all questions answered affirmatively, resulting in an overall COMPLIANT rating; and a passing scan has been completed by a PCI SSC Approved Scan Vendor, thereby (Merchant Company Name) has demonstrated full compliance with the PCI DSS. Non-Compliant: Not all sections of the PCI DSS SAQ are complete, or not all questions are answered yes, resulting in an overall NON-COMPLIANT rating, or a passing scan has not been completed by a PCI SSC Approved Scan Vendor, thereby (Merchant Company Name) has not demonstrated full compliance with the PCI DSS. Target Date for Compliance: An entity submitting this form with a status of Non-Compliant may be required to complete the Action Plan in Part 4 of this document. Check with your acquirer or the payment brand(s) before completing Part 4, since not all payment brands require this section. Part 3a. Confirmation of Compliant Status Merchant confirms: PCI DSS Self-Assessment Questionnaire D, Version (version of SAQ), was completed according to the instructions therein. All information within the above-referenced SAQ and in this attestation fairly represents the results of my assessment in all material respects. I have confirmed with my POS vendor that my POS system does not store sensitive authentication data after authorization. I have read the PCI DSS and I recognize that I must maintain full PCI DSS compliance at all times. No evidence of magnetic stripe (i.e., track) data 2, CAV2, CVC2, CID, or CVV2 data 3, or PIN data 4 storage subsequent to transaction authorization was found on ANY systems reviewed during this assessment. Part 3b. Merchant Acknowledgement Signature of Merchant Executive Officer Date Merchant Executive Officer Name Title Merchant Company Represented Data encoded in the magnetic stripe used for authorization during a card-present transaction. Entities may not retain full magnetic-stripe data subsequent to transaction authorization. The only elements of track data that may be retained are account number, expiration date, and name. The three- or four-digit value printed on or to the right of the signature panel or on the face of a payment card used to verify cardnot-present transactions. Personal Identification Number entered by cardholder during a card-present transaction, and/or encrypted PIN block present within the transaction message. PCI DSS SAQ D, v1.1, Attestation of Compliance, Merchant Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 2
8 Part 4. Action Plan for Non-Compliant Status Please select the appropriate Compliance Status for each requirement. If you answer NO to any of the requirements, you are required to provide the date Company will be compliant with the requirement and a brief description of the actions being taken to meet the requirement. Check with your acquirer or the payment brand(s) before completing Part 4, since not all payment brands require this section. Compliance Status (Select One) PCI DSS Requirement Description of Requirement YES NO Remediation Date and Actions (if Compliance Status is NO ) 1 Install and maintain a firewall configuration to protect cardholder data 2 3 Do not use vendor-supplied defaults for system passwords and other security parameters Protect stored cardholder data 4 Encrypt transmission of cardholder data across open, public networks 5 Use and regularly update anti-virus software 6 Develop and maintain secure systems and applications 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 10 Track and monitor all access to network resources and cardholder data 11 Regularly test security systems and processes PCI DSS SAQ D, v1.1, Attestation of Compliance, Merchant Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 3
9 Compliance Status (Select One) 12 Maintain a policy that addresses information security PCI DSS SAQ D, v1.1, Attestation of Compliance, Merchant Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 4
10 Attestation of Compliance, SAQ D Service Provider Version Instructions for Submission The service provider must complete this Attestation of Compliance as a declaration of the service provider s compliance status with the Payment Card Industry Data Security Standard (PCI DSS). Complete all applicable sections and refer to the submission instructions at PCI DSS Compliance Completion Steps in this document. Part 1. Qualified Security Assessor Company Information (if applicable) Company Name: Lead QSA Contact Name: Telephone: Title: Business Address: State/Province: Country: ZIP: URL: Part 2. Service Provider Organization Information Company Name: Contact Name: Telephone: Title: Business Address: State/Province: Country: ZIP: URL: Part 2a. Services Services Provided (check all that apply): Authorization Loyalty Programs 3-D Secure Access Control Server Switching IPSP (E-commerce) Process Magnetic-Stripe Transactions Payment Gateway Clearing & Settlement Process MO/TO Transactions Hosting Issuing Processing Others (please specify): List facilities and locations included in PCI DSS review: Part 2b. Relationships Does your company have a relationship with one or more third-party service providers (e.g. gateways, web-hosting companies, airline booking agents, loyalty program agents, etc)? Yes No Part 2c: Transaction Processing How and in what capacity does your business store, process and/or transmit cardholder data? Payment Applications in use or provided as part of your service: Payment Application Version: PCI DSS SAQ D, v1.1, Attestation of Compliance, Service Provider Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 5
11 Part 3. PCI DSS Validation Based on the results noted in the SAQ D dated (completion date of SAQ), (Service Provider Company Name) asserts the following compliance status (check one): Compliant: All sections of the PCI SAQ are complete, and all questions answered yes, resulting in an overall COMPLIANT rating; and a passing scan has been completed by a PCI SSC Approved Scan Vendor, thereby (Service Provider Company Name) has demonstrated full compliance with the PCI DSS. Non-Compliant: Not all sections of the PCI SAQ are complete, or some questions are answered no, resulting in an overall NON-COMPLIANT rating, or a passing scan has not been completed by a PCI SSC Approved Scan Vendor, thereby (Service Provider Company Name) has not demonstrated full compliance with the PCI DSS. Target Date for Compliance: An entity submitting this form with a status of Non-Compliant may be required to complete the Action Plan in Part 4 of this document. Check with your acquirer or the payment brand(s) before completing Part 4, since not all payment brands require this section. Part 3a. Confirmation of Compliant Status Service Provider confirms: Self-Assessment Questionnaire D, Version (insert version number), was completed according to the instructions therein. All information within the above-referenced SAQ and in this attestation fairly represents the results of my assessment. I have read the PCI DSS and I recognize that I must maintain full PCI DSS compliance at all times. No evidence of magnetic stripe (i.e., track) data 5, CAV2, CVC2, CID, or CVV2 data 6, or PIN data 7 storage subsequent to transaction authorization was found on ANY systems reviewed during this assessment. Part 3b. Service Provider Acknowledgement Signature of Service Provider Executive Officer Date Service Provider Executive Officer Name Title Service Provider Company Represented Data encoded in the magnetic stripe used for authorization during a card-present transaction. Entities may not retain full magnetic-stripe data subsequent to transaction authorization. The only elements of track data that may be retained are account number, expiration date, and name. The three- or four-digit value printed on or to the right of the signature panel or on the face of a payment card used to verify cardnot-present transactions. Personal Identification Number entered by cardholder during a card-present transaction, and/or encrypted PIN block present within the transaction message. PCI DSS SAQ D, v1.1, Attestation of Compliance, Service Provider Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 6
12 Part 4. Action Plan for Non-Compliant Status Please select the appropriate Compliance Status for each requirement. If you answer NO to any of the requirements, you are required to provide the date Company will be compliant with the requirement and a brief description of the actions being taken to meet the requirement. Check with your acquirer or the payment brand(s) before completing Part 4, since not all payment brands require this section. Compliance Status (Select One) PCI DSS Requirement Description of Requirement YES NO 1 Install and maintain a firewall configuration to protect cardholder data Remediation Date and Actions (if Compliance Status is NO ) 2 Do not use vendor-supplied defaults for system passwords and other security parameters 3 Protect stored cardholder data Encrypt transmission of cardholder data across open, public networks Use and regularly update anti-virus software Develop and maintain secure systems and applications Restrict access to cardholder data by business need to know Assign a unique ID to each person with computer access Restrict physical access to cardholder data Track and monitor all access to network resources and cardholder data Regularly test security systems and processes PCI DSS SAQ D, v1.1, Attestation of Compliance, Service Provider Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 7
13 12 Maintain a policy that addresses information security PCI DSS SAQ D, v1.1, Attestation of Compliance, Service Provider Version February 2008 Copyright 2008 PCI Security Standards Council LLC Page 8
14 Self-Assessment Questionnaire D Date of Completion: Build and Maintain a Secure Network Requirement 1: Install and maintain a firewall configuration to protect data Question Response: Yes No Special 1.1 Do established firewall configuration standards include the following? A formal process for approving and testing all external network connections and changes to the firewall configuration? A current network diagram with all connections to cardholder data, including any wireless networks? Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone? Description of groups, roles, and responsibilities for logical management of network components? Documented list of services and ports necessary for business? Justification and documentation for any available protocols besides hypertext transfer protocol (HTTP), secure sockets layer (SSL), secure shell (SSH), and virtual private network (VPN)? Justification and documentation for any risky protocols allowed (for example, file transfer protocol [FTP]), which includes reason for use of protocol and security features implemented? Quarterly review of firewall and router rule sets? Configuration standards for routers? 1.2 Does the firewall configuration deny all traffic from untrusted networks and hosts, except for protocols necessary for the cardholder environment? 1.3 (a) Does the firewall configuration restrict connections between publicly accessible servers and any system component storing cardholder data, including any connections from wireless networks? (b) Does the firewall configuration: Not Applicable (permitted only when indicated) or Compensating Control Used. Organizations using compensating controls must complete the Compensating Control Worksheet in the Appendix. Copyright 2008 PCI Security Standards Council LLC Page 9
15 Question Response: Yes No Special Restrict inbound Internet traffic to Internet protocol (IP) addresses within the DMZ (ingress filters)? Prohibit the passing of internal addresses from the Internet into the DMZ? Implement stateful inspection, also known as dynamic packet filtering (that is, only established connections are allowed into the network)? Place the database in an internal network zone, segregated from the DMZ? Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment? Secure and synchronize router configuration files? (For example, running configuration files (for normal functioning of the routers), and start-up configuration files (when machines are re-booted) should have the same secure configuration.) Deny all other inbound and outbound traffic not specifically allowed? Include installation of perimeter firewalls between any wireless networks and the cardholder data environment, and configure these firewalls to deny any traffic from the wireless environment or from controlling any traffic (if such traffic is necessary for business purposes)? Include installation of personal firewall software on any mobile and employee-owned computers with direct connectivity to the Internet (for example, laptops used by employees), which are used to access the organization s network? 1.4 (a) Does the firewall configuration prohibit direct public access between external networks and any system component that stores cardholder data (for example, databases, logs, trace files), (b) At a minimum, do controls ensure the following? Has a DMZ been implemented to filter and screen all traffic and to prohibit direct routes for inbound and outbound Internet traffic? Is outbound traffic restricted from payment card applications to IP addresses within the DMZ? 1.5 Has IP-masquerading been implemented to prevent internal addresses from being translated and revealed on the Internet? Use technologies that implement RFC 1918 address space, such as port address translation (PAT) or network address translation (NAT). Copyright 2008 PCI Security Standards Council LLC Page 10
16 Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Question Response: Yes No Special 2.1 Are vendor-supplied defaults always changed before installing a system on the network? Examples include passwords, simple network management protocol (SNMP) community strings, and elimination of unnecessary accounts Are wireless environment defaults changed before installing a wireless system? Wireless environment defaults include but are not limited to, wired equivalent privacy (WEP) keys, default service set identifier (SSID), passwords, and SNMP community strings. (a) Are SSID broadcasts disabled? (b) Is WiFi protected access (WPA and WPA2) technology enabled for encryption and authentication when WPAcapable? 2.2 (a) Have configuration standards been developed for all system components? (b) Do these standards address all known security vulnerabilities and are they consistent with industry-accepted system hardening standards as defined, for example, by SysAdmin Audit Network Security Network (SANS), National Institute of Standards Technology (NIST), and Center for Internet Security (CIS)? (c) Do controls ensure the following? Is only one primary function implemented per server (for example, web servers, database servers, and DNS should be implemented on separate servers)? Are all unnecessary and insecure services and protocols disabled (services and protocols not directly needed to perform the devices specified function)? Are system security parameters configured to prevent misuse? Has all unnecessary functionality such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers been removed? Not Applicable (permitted only when indicated) or Compensating Control Used. Organizations using compensating controls must complete the Compensating Control Worksheet in the Appendix. Copyright 2008 PCI Security Standards Council LLC Page 11
17 Question Response: Yes No Special 2.3 Is all non-console administrative access encrypted? Use technologies such as SSH, VPN, or SSL/TLS (transport layer security) for web-based management and other non-console administrative access. 2.4 If you are a hosting provider, are your systems configured to protect each entity s hosted environment and data? See Appendix A: PCI DSS Applicability for Hosting Providers for specific requirements that must be met. Not Applicable (permitted only when indicated) or Compensating Control Used. Organizations using compensating controls must complete the Compensating Control Worksheet in the Appendix. Copyright 2008 PCI Security Standards Council LLC Page 12
18 Protect Cardholder Data Requirement 3: Protect stored cardholder data Question Response: Yes No Special 3.1 (a) Is storage of cardholder data kept to a minimum, and is storage amount and retention time limited to that which is required for business, legal, and/or regulatory purposes? (b) Is there a data-retention and disposal policy, and does it include limitations as stated in (a) above? 3.2 Do all systems adhere to the following requirements regarding storage of sensitive authentication data? Do not store the full contents of any track from the magnetic stripe (that is on the back of a card, in a chip or elsewhere). This data is alternatively called full track, track, track 1, track 2, and magnetic stripe data. In the normal course of business, the following data elements from the magnetic stripe may need to be retained: the accountholder s name, primary account number (PAN), expiration date, and service code. To minimize risk, store only those data elements needed for business. NEVER store the card verification code or value or PIN verification value data elements Do not store the card-validation code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions Do not store the personal identification number (PIN) or the encrypted PIN block. 3.3 Is the PAN masked when displayed (the first six and last four digits are the maximum number of digits to be displayed). Note: This requirement does not apply to employees and other parties with a specific need to see the full PAN; nor does the requirement supersede stricter requirements in place for displays of cardholder data (for example, for point-of-sale [POS] receipts). Not Applicable (permitted only when indicated) or Compensating Control Used. Organizations using compensating controls must complete the Compensating Control Worksheet in the Appendix. Copyright 2008 PCI Security Standards Council LLC Page 13
19 Question Response: Yes No Special 3.4 Is PAN, at a minimum, rendered unreadable anywhere it is stored (including data on portable digital media, backup media, in logs, and data received from or stored by wireless networks) by using any of the following approaches? Strong one-way hash functions (hashed indexes) Truncation Index tokens and pads (pads must be securely stored) Strong cryptography with associated key management processes and procedures. The MINIMUM account information that must be rendered unreadable is the PAN. If for some reason, a company is unable to encrypt cardholder data, refer to Appendix B: Compensating Controls for Encryption of Stored Data If disk encryption (rather than file- or column-level database encryption) is used: (a) Is logical access managed independently of native operating system access control mechanisms (for example, by not using local system or Active Directory accounts)? (b) Are decryption keys independent of user accounts? 3.5 Are encryption keys used for encryption of cardholder data protected against both disclosure and misuse? Is access to keys restricted to the fewest number of custodians necessary? Are keys stored securely, and in the fewest possible locations and forms? 3.6 (a) Are all key-management processes and procedures for keys used for encryption of cardholder data, fully documented and implemented? (b) Do they include the following? Generation of strong keys Secure key distribution Secure key storage Periodic changing of keys As deemed necessary and recommended by the associated application (for example, re-keying), preferably automatically At least annually Destruction of old keys Copyright 2008 PCI Security Standards Council LLC Page 14
20 Question Response: Yes No Special Split knowledge and establishment of dual control of keys (so that it requires two or three people, each knowing only their part of the key, to reconstruct the whole key) Prevention of unauthorized substitution of keys Replacement of known or suspected compromised keys Revocation of old or invalid keys Requirement for key custodians to sign a form stating that they understand and accept their key-custodian responsibilities. Requirement 4: Encrypt transmission of cardholder data across open, public networks 4.1 Are strong cryptography and security protocols, such as secure sockets layer (SSL) / transport layer security (TLS) and Internet protocol security (IPSEC), used to safeguard sensitive cardholder data during transmission over open, public networks? Examples of open, public networks that are in scope of the PCI DSS are the Internet, WiFi (IEEE x), global system for mobile communications (GSM), and general packet radio service (GPRS) (a) For wireless networks transmitting cardholder data, are transmissions encrypted by using WiFi protected access (WPA or WPA2) technology, IPSEC VPN, or SSL/TLS? Never rely exclusively on wired equivalent privacy (WEP) to protect confidentiality and access to a wireless LAN. (b) If WEP is used, do controls ensure the following? WEP is used with a minimum 104-bit encryption key and 24 bit-initialization value. WEP is used ONLY in conjunction with WiFi protected access (WPA or WPA2) technology, VPN, or SSL/TLS. Shared WEP keys are rotated quarterly (or automatically if the technology permits). Shared WEP keys are rotated whenever there are changes in personnel with access to keys. Access is restricted based on media access code (MAC) address. 4.2 Are policies, procedures, and practices in place to preclude the sending of unencrypted PANs by ? Copyright 2008 PCI Security Standards Council LLC Page 15