Source: http://docplayer.net/11873727-Payment-card-industry-pci-data-security-standard-self-assessment-questionnaire-d-and-attestation-of-compliance.html
Timestamp: 2019-01-19 06:37:14
Document Index: 533226644

Matched Legal Cases: ['art 1', 'art 1', 'art 1', '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 SAQ-Eligible Merchants and Service Providers Version 2.0 October 2010
2 Document Changes Date Version Description October 1, October 28, To align content with new PCI DSS v1.2 and to implement minor changes noted since original v1.1. To align content with new PCI DSS v2.0 requirements and testing procedures. PCI DSS SAQ D, v2.0, Document Changes October 2010 Page i
3 Table of Contents Document Changes... i Related Documents... iii Before You Begin... iv Completing the Self-Assessment Questionnaire...iv PCI DSS Compliance Completion Steps...iv Guidance for Non-Applicability of Certain, Specific Requirements... v Attestation of Compliance, SAQ D Merchant Version... 1 Attestation of Compliance, SAQ D Service Provider Version... 1 Self-Assessment Questionnaire D... 1 Build and Maintain a Secure Network... 1 Requirement 1: Install and maintain a firewall configuration to protect data... 1 Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters... 4 Protect Cardholder Data... 6 Requirement 3: Protect stored cardholder data... 6 Requirement 4: Encrypt transmission of cardholder data across open, public networks...10 Maintain a Vulnerability Management Program...11 Requirement 5: Use and regularly update anti-virus software or programs...11 Requirement 6: Develop and maintain secure systems and applications...11 Implement Strong Access Control Measures...15 Requirement 7: Restrict access to cardholder data by business need to know...15 Requirement 8: Assign a unique ID to each person with computer access...16 Requirement 9: Restrict physical access to cardholder data...19 Regularly Monitor and Test Networks...22 Requirement 10: Track and monitor all access to network resources and cardholder data..22 Requirement 11: Regularly test security systems and processes...24 Maintain an Information Security Policy...27 Requirement 12: Maintain a policy that addresses information security for all personnel...27 Appendix A: Additional PCI DSS Requirements for Shared Hosting Providers Requirement A.1: Shared hosting providers must protect cardholder data environment...31 Appendix B: Compensating Controls Appendix C: Compensating Controls Worksheet Compensating Controls Worksheet Completed Example...35 Appendix D: Explanation of Non-Applicability PCI DSS SAQ D, v2.0, Table of Contents October 2010 Page ii
4 Related Documents The following documents were created to assist merchants and service providers in understanding the PCI Data Security Standard (PCI DSS) and the PCI DSS SAQ. Document Requirements and Security Assessment Procedures Navigating PCI DSS: Understanding the Intent of the Requirements Self-Assessment Guidelines and Instructions Self-Assessment Questionnaire A and Attestation Self-Assessment Questionnaire B and Attestation Self-Assessment Questionnaire C-VT and Attestation Self-Assessment Questionnaire C and Attestation Self-Assessment Questionnaire D and Attestation PCI Data Security Standard and Payment Application Data Security Standard: Glossary of Terms, Abbreviations, and Acronyms Audience All merchants and service providers All merchants and service providers All merchants and service providers Eligible merchants 1 Eligible merchants 1 Eligible merchants 1 Eligible merchants 1 Eligible merchants and service providers 1 All merchants and service providers 1 To determine the appropriate Self-Assessment Questionnaire, see Self- Assessment Guidelines and Instructions, Selecting the SAQ and Attestation That Best Apply to Your Organization. PCI DSS SAQ D, v2.0, Related Documents October 2010 Page iii
5 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 SAQ types A through C as described briefly in the table below and fully in PCI DSS Self- Assessment Questionnaire Instructions and Guidelines. SAQ A B C-VT C D Description Card-not-present (e-commerce or mail/telephone-order) merchants, all cardholder data functions outsourced. This would never apply to face-to-face merchants. Imprint-only merchants with no electronic cardholder data storage, or standalone, dial-out terminal merchants with no electronic cardholder data storage Merchants using only web-based virtual terminals, no electronic cardholder data storage Merchants with payment application systems connected to the Internet, no electronic cardholder data storage All other merchants (not included in descriptions for SAQs A through C above) and all service providers defined by a payment brand as eligible to complete an SAQ. SAQ D applies to SAQ-eligible merchants not meeting the criteria for SAQ types A through C, above and all service providers defined by a payment brand as being SAQ-eligible. SAQ D service providers and merchants validate compliance by completing SAQ D and the associated Attestation of Compliance. 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 managing 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 DSS. PCI DSS Compliance Completion Steps 1. Assess your environment for compliance with the PCI DSS. 2. Complete the Self-Assessment Questionnaire (SAQ D) according to the instructions in the Self- Assessment Questionnaire Instructions and Guidelines. 3. Complete a passing vulnerability scan with a PCI SSC Approved Scanning Vendor (ASV), and obtain evidence of a passing scan from the ASV. 4. Complete the Attestation of Compliance in its entirety. 5. 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). PCI DSS SAQ D, v2.0, Before You Begin October 2010 Page iv
6 Guidance for Non-Applicability of Certain, Specific Requirements Exclusion: If you are required to answer SAQ D to validate your PCI DSS compliance, the following exceptions may be considered. See Non-Applicability below for the appropriate SAQ response. The questions specific to wireless only need to be answered if wireless is present anywhere in your network (for example, Requirements 1.2.3, 2.1.1, and 4.1.1). Note that Requirement 11.1 (use of process to identify unauthorized wireless access points) must still be answered even if wireless is not in your network, since the process detects any rogue or unauthorized devices that may have been added without your knowledge. The questions specific to custom applications and code (Requirements 6.3 and 6.5) only need to be answered if your organization develops its own custom applications. The questions for Requirements 9.1 through 9.4 only need to be answered for facilities with sensitive areas as defined here. Sensitive areas refers to any data center, server room or any area that houses systems that store, process, or transmit cardholder data. This excludes the areas where only point-of-sale terminals are present, such as the cashier areas in a retail store, but does include retail store back-office server rooms that store cardholder data, and storage areas for large quantities of cardholder data. Non-Applicability: These and any other requirements deemed not applicable to your environment must be indicated with N/A in the Special column of the SAQ. Accordingly, complete the Explanation of Non-Applicability worksheet in Appendix D for each N/A entry. PCI DSS SAQ D, v2.0, Before You Begin October 2010 Page v
7 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) Requirements and Security Assessment Procedures. Complete all applicable sections and refer to the submission instructions at PCI DSS Compliance Completion Steps in this document. Part 1. Merchant and Qualified Security Assessor Information Part 1a. Merchant Organization Information Company Name: DBA(s): Contact Name: Title: Telephone: Business Address: City: State/Province: Country: Zip: URL: Part 1b. Qualified Security Assessor Company Information (if applicable) Company Name: Lead QSA Contact Name: Title: Telephone: Business Address: City: State/Province: Country: Zip: URL: Part 2 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 2a. Relationships Does your company have a relationship with one or more third-party agents (for example, 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 2b. Transaction Processing How and in what capacity does your business store, process and/or transmit cardholder data? Please provide the following information regarding the Payment Applications your organization uses: Payment Application in Use Version Number Last Validated according to PABP/PA-DSS PCI DSS SAQ D, v2.0, Attestation of Compliance, Merchant Version October 2010 Page 1
8 Part 3. PCI DSS Validation 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 Scanning Vendor (ASV), 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 Scanning Vendor (ASV), 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 payment application vendor that my payment 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 after 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 or equivalent data on a chip used for authorization during a card-present transaction. Entities may not retain full magnetic-stripe data after 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, v2.0, Attestation of Compliance, Merchant Version October 2010 Page 2
9 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. PCI DSS Requirement Description of Requirement Compliance Status (Select One) YES NO Remediation Date and Actions (if Compliance Status is NO ) 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 3 Protect stored cardholder data 4 Encrypt transmission of cardholder data across open, public networks 5 Use and regularly update anti-virus software or programs 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 12 Maintain a policy that addresses information security for all personnel PCI DSS SAQ D, v2.0, Attestation of Compliance, Merchant Version October 2010 Page 3