Document Comparison

aoc_saq_d_merchants.pdf AOC_SAQ_D_Merchant_v3-1_rev1-1.pdf
53% similar
4 → 8 Pages
891 → 1602 Words
17 Content Changes

Content Changes

17 content changes. 8 administrative changes (dates, page numbers) hidden.

Added p. 2
Section 1: Assessment Information Instructions for Submission This document must be completed as a declaration of the results of the merchant’s self-assessment with the Payment Card Industry Data Security Standard Requirements and Security Assessment Procedures (PCI DSS). Complete all sections: The merchant is responsible for ensuring that each section is completed by the relevant parties, as applicable. Contact acquirer (merchant bank) or the payment brands to determine reporting and submission procedures.

ISA Name(s) (if applicable): Title:

Part 1b. Qualified Security Assessor Company Information (if applicable) Company Name:

Lead QSA Contact Name: Title:

What types of payment channels does your business serve?

Mail order/telephone order (MOTO) E-Commerce Card-present (face-to-face) Which payment channels are covered by this SAQ? Mail order/telephone order (MOTO) E-Commerce Card-present (face-to-face)

Note: If your organization has a payment channel or process that is not covered by this SAQ, consult your acquirer or payment brand about validation for the other channels.
Added p. 3
Type of facility Number of facilities of this type Location(s) of facility (city, country) Example: Retail outlets 3 Boston, MA, USA Part 2d. Payment Application Does the organization use one or more Payment Applications? Yes No Provide the following information regarding the Payment Applications your organization uses:

Payment Application Version Number Application Is application PA-DSS Listed? PA-DSS Listing Expiry date (if applicable) Part 2e. Description of Environment Provide a high-level description of the environment covered by this assessment.

For example:

• Connections into and out of the cardholder data environment (CDE).

• Critical system components within the CDE, such as POS devices, databases, web servers, etc., and any other necessary payment components, as applicable.

Does your business use network segmentation to affect the scope of your PCI DSS environment? (Refer to “Network Segmentation” section of PCI DSS for guidance on network segmentation)
Added p. 4
Note: Requirement 12.8 applies to all entities in this list.

Section 2: Self-Assessment Questionnaire D

• Merchants This Attestation of Compliance reflects the results of a self-assessment, which is documented in an accompanying SAQ.

The assessment documented in this attestation and in the SAQ was completed on:

Have compensating controls been used to meet any requirement in the SAQ? Yes No Were any requirements in the SAQ identified as being not applicable (N/A)? Yes No Were any requirements in the SAQ identified as being not tested? Yes No Were any requirements in the SAQ unable to be met due to a legal constraint? Yes No

Section 3: Validation and Attestation Details Part 3. PCI DSS Validation Based on the results noted in the SAQ D dated (completion date), the signatories identified in Parts 3b-3d, as applicable, assert(s) the following compliance status for the entity identified in Part 2 of this document as of (date): (check …
Added p. 8
Check with your acquirer or the payment brand(s) before completing Part 4.
Modified p. 1
Payment Card Industry (PCI) Data Security Standard Attestation of Compliance for Self-Assessment Questionnaire D

Merchant Version Version 1.2
Payment Card Industry (PCI) Data Security Standard Attestation of Compliance for Self-Assessment Questionnaire D

Merchants For use with PCI DSS Version 3.1 Revision 1.1
Removed p. 2
Part 2. Merchant Organization Information Company Name: DBA(S):

Part 2a. Type of merchant business (check all that apply):

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 (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 2c. Transaction Processing Payment Application in use: Payment Application Version:
Modified p. 2
Part 1. Qualified Security Assessor Company Information (if applicable) Company Name:
Part 1. Merchant and Qualified Security Assessor Information Part 1a. Merchant Organization Information Company Name: DBA (doing business as):
Modified p. 2
State/Province: Country: ZIP:
State/Province: Country: Zip:
Modified p. 2
State/Province: Country: ZIP:
State/Province: Country: Zip:
Modified p. 2
Retailer Telecommunication Grocery and Supermarkets Petroleum E-Commerce Mail/Telephone-Order Others (please specify):
Part 2. Executive Summary Part 2a. Type of Merchant Business (check all that apply) Retailer Telecommunication Grocery and Supermarkets Petroleum E-Commerce Mail order/telephone order (MOTO) Others (please specify):
Removed p. 3
Part 3a. Confirmation of Compliant Status Merchant confirms:

Part 3b. Merchant Acknowledgement Signature of Merchant Executive Officer  Date  Merchant Executive Officer Name  Title  Merchant Company Represented  1 Data encoded in the magnetic stripe 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.
Modified p. 3 → 6
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.
Compliant: All sections of the PCI DSS SAQ are complete, all questions answered affirmatively, resulting in an overall COMPLIANT rating; thereby (Merchant Company Name) has demonstrated full compliance with the PCI DSS.
Modified p. 3 → 6
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.
Non-Compliant: Not all sections of the PCI DSS SAQ are complete, or not all questions are answered affirmatively, resulting in an overall NON-COMPLIANT rating, thereby (Merchant Company Name) has not demonstrated full compliance with the PCI DSS.
Modified p. 3 → 6
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.
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.
Modified p. 3 → 6
I have confirmed with my POS vendor that my POS system does not store sensitive authentication data after authorization.
I have confirmed with my payment application vendor that my payment system does not store sensitive authentication data after authorization.
Modified p. 3 → 6
I have read the PCI DSS and I recognize that I must maintain full PCI DSS compliance at all times.
I have read the PCI DSS and I recognize that I must maintain PCI DSS compliance, as applicable to my environment, at all times.
Modified p. 4 → 8
PCI DSS Requirement Description of Requirement Compliance Status (Select One) Remediation Date and Actions (if Compliance Status is “NO”) YES NO Install and maintain a firewall configuration to protect cardholder data 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 …
PCI DSS Requirement Description of Requirement Compliant to PCI DSS Requirements (Select One) Remediation Date and Actions (If “NO” selected for any Requirement) YES NO Install and maintain a firewall configuration to protect cardholder data 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 Protect all systems against malware and regularly update anti- virus software or programs 6 Develop and maintain secure …