Source: http://docplayer.net/20788816-Payment-card-industry-pci-data-security-standard-self-assessment-questionnaire-c-and-attestation-of-compliance.html
Timestamp: 2019-01-15 23:06:02
Document Index: 218398647

Matched Legal Cases: ['art 1', 'art 2', '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 C and Attestation of Compliance Payment Application Connected to Internet, No Electronic Cardholder Data Storage Version 1.1 February 2008
2 Table of Contents PCI Data Security Standard: Related Documents ii Before you Begin Completing the Self-Assessment Questionnaire...iii iii PCI DSS Compliance - Completion Steps iii Attestation of Compliance, SAQ C 2 Self-Assessment Questionnaire C 6 Build and Maintain a Secure Network...6 Requirement 1: Install and maintain a firewall configuration to protect data...6 Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters...6 Protect Cardholder Data...7 Requirement 3: Protect stored cardholder data...7 Requirement 4: Encrypt transmission of cardholder data across open, public networks...7 Maintain a Vulnerability Management Program...8 Requirement 5: Use and regularly update anti-virus software or programs...8 Requirement 6: Develop and maintain secure systems and applications...8 Implement Strong Access Control Measures...8 Requirement 7: Restrict access to cardholder data by business need-to-know...8 Requirement 8: Assign a unique ID to each person with computer access...8 Requirement 9: Restrict physical access to cardholder data...9 Regularly Monitor and Test Networks...10 Requirement 10: Track and monitor all access to network resources and cardholder data..10 Requirement 11: Regularly test security systems and processes...10 Maintain an Information Security Policy...11 Requirement 12: Maintain a policy that addresses information security for employees and contractors...11 PCI DSS SAQ C, 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 C, 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 C has been developed to address requirements applicable to merchants who process cardholder data via payment applications (for example, POS systems) connected to the Internet (via high-speed connection, DSL, cable modem, etc.), but who do not store cardholder data on any computer system. These payment applications are connected to the Internet either because: 1. The payment application is on a personal computer connected to the Internet, or 2. The payment application is connected to the Internet to transmit cardholder data. These merchants are defined as SAQ Validation Type 4, as defined here and in the PCI DSS Self- Assessment Questionnaire Instructions and Guidelines. Validation Type 4 merchants process cardholder data via POS machines connected to the Internet, do not store cardholder data on any computer system, and may be either brick-and-mortar (card-present) or e-commerce or mail/telephone-order (card-notpresent) merchants. Such merchants must validate compliance by completing SAQ C and the associated Attestation of Compliance, confirming that: Your company has a payment application system and an Internet connection on the same device; The payment application/internet device is not connected to any other systems within your environment; Your company retains only paper reports or paper copies of receipts; Your company does not store cardholder data in electronic format; and Your company s payment application vendor uses secure techniques to provide remote support to your payment system. 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 C) 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. PCI DSS SAQ C, v1.1, Before You Begin February 2008 Copyright 2008 PCI Security Standards Council LLC Page iii
5 Attestation of Compliance, SAQ C 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: PCI DSS SAQ C, v1.1, Attestation of Compliance February 2008 Copyright 2008 PCI Security Standards Council LLC Page 2
6 Part 2d. Eligibility to Complete SAQ C Merchant certifies eligibility to complete this shortened version of the Self-Assessment Questionnaire because: Merchant has a payment application system and an Internet or public network connection on the same device; The payment application system/internet device is not connected to any other system within the merchant environment; Merchant does not store cardholder data in electronic format; If Merchant does store cardholder data, such data is only in paper reports or copies of paper receipts and is not received electronically; and Merchant s payment application software vendor uses secure techniques to provide remote support to merchant s payment application system. Part 3. PCI DSS Validation Based on the results noted in the SAQ C dated (completion date), (Merchant 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 (Merchant 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 (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. Copyright 2008 PCI Security Standards Council LLC Page 3
7 Part 3a. Confirmation of Compliant Status Merchant confirms: PCI DSS Self-Assessment Questionnaire C, Version (SAQ version #), 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 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. Copyright 2008 PCI Security Standards Council LLC Page 4
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 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 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 11 Regularly test security systems and processes 12 Maintain a policy that addresses information security Copyright 2008 PCI Security Standards Council LLC Page 5
9 Self-Assessment Questionnaire C Date of Completion: Build and Maintain a Secure Network Requirement 1: Install and maintain a firewall configuration to protect data Question Response: YES NO 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? 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), Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters Question Response: YES NO 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 WPA-capable? 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. Copyright 2008 PCI Security Standards Council LLC Page 6
10 Protect Cardholder Data Requirement 3: Protect stored cardholder data Question Response: YES NO 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 fourdigit 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). 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). 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 7
11 Maintain a Vulnerability Management Program Requirement 5: Use and regularly update anti-virus software or programs Question Response: YES NO 5.1 Is anti-virus software deployed on all systems commonly affected by viruses (particularly personal computers and servers)? Note: Systems commonly affected by viruses typically do not include UNIXbased operating systems or mainframes Are anti-virus programs capable of detecting, removing, and protecting against other forms of malicious software, including spyware and adware? 5.2 Are all anti-virus mechanisms current, actively running, and capable of generating audit logs? Requirement 6: Develop and maintain secure systems and applications 6.1 (a) Do all system components and software have the latest vendorsupplied security patches installed? (b) Are relevant security patches installed within one month of release? Implement Strong Access Control Measures Requirement 7: Restrict access to cardholder data by business need-to-know Question Response: YES NO 7.1 Is access to computing resources and cardholder information limited to only those individuals whose jobs require such access? Requirement 8: Assign a unique ID to each person with computer access Are accounts used by vendors for remote maintenance enabled only during the time period needed? Copyright 2008 PCI Security Standards Council LLC Page 8
12 Requirement 9: Restrict physical access to cardholder data 9.6 Are all paper and electronic media that contain cardholder data physically secure? (Such media includes computers, electronic media, networking and communications hardware, telecommunication lines, paper receipts, paper reports, and faxes.) 9.7 (a) Is strict control maintained over the internal or external distribution of any kind of media that contains cardholder data? (b) Do controls include the following: Is the media classified so it can be identified as confidential? Is the media sent by secured courier or other delivery method that can be accurately tracked? 9.8 Are processes and procedures in place to ensure management approval is obtained prior to moving any and all media from a secured area (especially when media is distributed to individuals)? 9.9 Is strict control maintained over the storage and accessibility of media that contains cardholder data? 9.10 Is media containing cardholder data destroyed when it is no longer needed for business or legal reasons? Destruction should be as follows: Are hardcopy materials cross-cut shredded, incinerated, or pulped? Copyright 2008 PCI Security Standards Council LLC Page 9
13 Regularly Monitor and Test Networks Requirement 10: Track and monitor all access to network resources and cardholder data Question Response: YES NO No questions applicable to SAQ C. Requirement 11: Regularly test security systems and processes 11.1 (a) Are security controls, limitations, network connections, and restrictions tested annually to assure the ability to adequately identify and to stop any unauthorized access attempts? (b) Is a wireless analyzer used at least quarterly to identify all wireless devices in use? 11.2 Are internal and external network vulnerability scans run at least quarterly and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades)? Note: Quarterly external vulnerability scans must be performed by a scan vendor qualified by the payment card industry. Scans conducted after network changes may be performed by the company s internal staff. Copyright 2008 PCI Security Standards Council LLC Page 10
14 Maintain an Information Security Policy Requirement 12: Maintain a policy that addresses information security for employees and contractors Question Response: YES NO 12.1 Is a security policy established, published, maintained, and disseminated, and does it accomplish the following: Includes a review at least once a year and updates when the environment changes? 12.3 (a) Are usage policies for critical employee-facing technologies (such as modems and wireless) developed to define proper use of these technologies for all employees and contractors? 12.4 Do the security policy and procedures clearly define information security responsibilities for all employees and contractors? 12.5 Are the following information security management responsibilities assigned to an individual or team? Establishing, documenting, and distributing security incident response and escalation procedures to ensure timely and effective handling of all situations? 12.6 Is a formal security awareness program in place to make all employees aware of the importance of cardholder data security? 12.8 Contractually, are the following required if cardholder data is shared with service providers? That service providers must adhere to the PCI DSS requirements? An agreement that includes an acknowledgement that the service provider is responsible for the security of cardholder data the provider possesses? Copyright 2008 PCI Security Standards Council LLC Page 11