Document Comparison
PCI-DSS-v3-2-1-AOC-Merchant-r2.pdf
→
PCI-DSS-v4-0-ROC-AOC-Merchants-r1.pdf
43% similar
9 → 11
Pages
1703 → 2196
Words
32
Content Changes
Content Changes
32 content changes. 13 administrative changes (dates, page numbers) hidden.
Added
p. 2
PCI DSS v4.0 Attestation of Compliance for Report on Compliance - Merchants Entity Name:
Date of Report as noted in the Report on Compliance:
This AOC reflects the results documented in an associated Report on Compliance (ROC). Associated ROC sections are noted in each AOC Part/Section below.
Capitalized terms used but not otherwise defined in this document have the meanings set forth in the PCI DSS Report on Compliance Template.
Part 1. Contact Information Part 1a. Assessed Entity (ROC Section 1.1) Company name:
Company mailing address:
Company mailing address:
Company main website:
Company contact name:
Company contact title:
Contact phone number:
Contact e-mail address:
Part 1b. Assessor (ROC Section 1.1) Provide the following information for all assessors involved in the Assessment. If there was no assessor for a given assessor type, enter Not Applicable.
PCI SSC Internal Security Assessor(s) ISA name(s):
Assessor phone number:
Assessor e-mail address:
Assessor certificate number:
Date of Report as noted in the Report on Compliance:
This AOC reflects the results documented in an associated Report on Compliance (ROC). Associated ROC sections are noted in each AOC Part/Section below.
Capitalized terms used but not otherwise defined in this document have the meanings set forth in the PCI DSS Report on Compliance Template.
Part 1. Contact Information Part 1a. Assessed Entity (ROC Section 1.1) Company name:
Company mailing address:
Company mailing address:
Company main website:
Company contact name:
Company contact title:
Contact phone number:
Contact e-mail address:
Part 1b. Assessor (ROC Section 1.1) Provide the following information for all assessors involved in the Assessment. If there was no assessor for a given assessor type, enter Not Applicable.
PCI SSC Internal Security Assessor(s) ISA name(s):
Assessor phone number:
Assessor e-mail address:
Assessor certificate number:
Added
p. 4
Mail order / telephone order (MOTO) E-Commerce Card-present Are any payment channels not included in this Assessment? If yes, indicate which channel(s) is not included in the Assessment and provide a brief explanation about why the channel was excluded.
Part 2b. Description of Role with Payment Cards (ROC Section 2.1) For each payment channel included in this Assessment as selected in Part 2a above, describe how the business stores, processes, and/or transmits account data.
Channel How Business Stores, Processes, and/or Transmits Account Data Part 2c. Description of Payment Card Environment Provide a high-level description of the environment covered by this Assessment. For example:
• System components that could impact the security of account data.
Part 2b. Description of Role with Payment Cards (ROC Section 2.1) For each payment channel included in this Assessment as selected in Part 2a above, describe how the business stores, processes, and/or transmits account data.
Channel How Business Stores, Processes, and/or Transmits Account Data Part 2c. Description of Payment Card Environment Provide a high-level description of the environment covered by this Assessment. For example:
• System components that could impact the security of account data.
Added
p. 5
Facility Type Total Number of Locations (How many locations of this type are in scope) Location(s) of Facility (city, country) Example: Retail locations 3 Boston, MA, USA Part 2e. PCI SSC Validated Products and Solutions (ROC Section 3.3) Does the entity use any item identified on any PCI SSC Lists of Validated Products and Solutions*? Provide the following information regarding each item the entity uses from PCI SSC's Lists of Validated Products and Solutions:
Name of PCI SSC- Validated Product or Version of Product or
PCI SSC Standard to which Product or Solution Was Validated
PCI SSC Listing Expiry Date of YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD * For purposes of this document, ”Lists of Validated Products and Solutions” means the lists of validated products, solutions, and/or components, appearing on the PCI SSC website (www.pcisecuritystandards.org) (for example, 3DS Software Development Kits, Approved PTS Devices, Validated Payment Software, Payment Applications (PA-DSS), Point to Point …
Name of PCI SSC- Validated Product or Version of Product or
PCI SSC Standard to which Product or Solution Was Validated
PCI SSC Listing Expiry Date of YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD YYYY-MM-DD * For purposes of this document, ”Lists of Validated Products and Solutions” means the lists of validated products, solutions, and/or components, appearing on the PCI SSC website (www.pcisecuritystandards.org) (for example, 3DS Software Development Kits, Approved PTS Devices, Validated Payment Software, Payment Applications (PA-DSS), Point to Point …
Added
p. 6
• Store, process, or transmit account data on the entity’s behalf (for example, payment gateways, payment processors, payment service providers (PSPs), and off-site storage)
• Manage system components included in the scope of the Assessment (for example, via network security control services, anti-malware services, security incident and event management (SIEM), contact and call centers, web-hosting services, and IaaS, PaaS, SaaS, and FaaS cloud providers)
• Could impact the security of the entity’s CDE (for example, vendors providing support via remote access, and/or bespoke software developers).
• Manage system components included in the scope of the Assessment (for example, via network security control services, anti-malware services, security incident and event management (SIEM), contact and call centers, web-hosting services, and IaaS, PaaS, SaaS, and FaaS cloud providers)
• Could impact the security of the entity’s CDE (for example, vendors providing support via remote access, and/or bespoke software developers).
Added
p. 7
PCI DSS Requirement Requirement Finding More than one response may be selected for a given requirement. Indicate all responses that apply.
Select If Below Method(s) In Place Not Applicable Not Tested Not In Customized Compensating
Section 2 Report on Compliance (ROC Sections 1.2 and 1.3.2) Date Assessment began: Note: This is the first date that evidence was gathered, or observations were made.
YYYY-MM-DD Date Assessment ended: Note: This is the last date that evidence was gathered, or observations were made.
YYYY-MM-DD Were any requirements in the ROC unable to be met due to a legal constraint? Yes No Were any testing activities performed remotely? If yes, for each testing activity below, indicate whether remote assessment activities were performed:
• Examine documentation Yes No
• Interview personnel Yes No
• Examine/observe live data Yes No
• Observe process being performed Yes No
• Observe physical environment Yes No
• Interactive testing Yes No
• All requirements have been assessed and therefore no …
Select If Below Method(s) In Place Not Applicable Not Tested Not In Customized Compensating
Section 2 Report on Compliance (ROC Sections 1.2 and 1.3.2) Date Assessment began: Note: This is the first date that evidence was gathered, or observations were made.
YYYY-MM-DD Date Assessment ended: Note: This is the last date that evidence was gathered, or observations were made.
YYYY-MM-DD Were any requirements in the ROC unable to be met due to a legal constraint? Yes No Were any testing activities performed remotely? If yes, for each testing activity below, indicate whether remote assessment activities were performed:
• Examine documentation Yes No
• Interview personnel Yes No
• Examine/observe live data Yes No
• Observe process being performed Yes No
• Observe physical environment Yes No
• Interactive testing Yes No
• All requirements have been assessed and therefore no …
Added
p. 10
PCI DSS controls will be maintained at all times, as applicable to the entity’s environment.
Part 3b. Merchant Attestation Signature of Merchant Executive Officer Date: YYYY-MM-DD Merchant Executive Officer Name: Title:
QSA performed testing procedures.
QSA provided other assistance. If selected, describe all role(s) performed:
Signature of Lead QSA Date: YYYY-MM-DD Lead QSA Name:
ISA(s) performed testing procedures.
ISA(s) provided other assistance.
If selected, describe all role(s) performed:
Part 3b. Merchant Attestation Signature of Merchant Executive Officer Date: YYYY-MM-DD Merchant Executive Officer Name: Title:
QSA performed testing procedures.
QSA provided other assistance. If selected, describe all role(s) performed:
Signature of Lead QSA Date: YYYY-MM-DD Lead QSA Name:
ISA(s) performed testing procedures.
ISA(s) provided other assistance.
If selected, describe all role(s) performed:
Removed
p. 2
September 2022 Revision 2 Updated to reflect the inclusion of UnionPay as a Participating Payment Brand.
Removed
p. 3
Part 1. Merchant and Qualified Security Assessor Information Part 1a. Merchant Organization Information Company Name: DBA (doing business as):
Business Address: City:
Business Address: City:
State/Province: Country: Zip:
State/Province: Country: Zip:
Lead QSA Contact Name: Title:
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):
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 assessment? Mail order/telephone order (MOTO) E-Commerce Card-present (face-to-face)
Business Address: City:
Business Address: City:
State/Province: Country: Zip:
State/Province: Country: Zip:
Lead QSA Contact Name: Title:
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):
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 assessment? Mail order/telephone order (MOTO) E-Commerce Card-present (face-to-face)
Modified
p. 3
Section 1: Assessment Information Instructions for Submission This Attestation of Compliance must be completed as a declaration of the results of the merchant’s 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 your acquirer (merchant bank) or the payment brands for reporting and submission procedures.
Section 1 Assessment Information Instructions for Submission This Attestation of Compliance (AOC) must be completed as a declaration of the results of the merchant’s assessment against the Payment Card Industry Data Security Standard (PCI DSS) Requirements and Testing Procedures (“Assessment”). Complete all sections. The merchant is responsible for ensuring that each section is completed by the relevant parties, as applicable. Contact the entity(ies) to which this AOC will be submitted for reporting and submission procedures.
Modified
p. 3
Qualified Security Assessor Company name:
Modified
p. 3 → 4
Note: If your organization has a payment channel or process that is not covered by this assessment, consult your acquirer or payment brand about validation for the other channels.
Note: If the merchant has a payment channel that is not covered by this Assessment, consult with the entity(ies) to which this AOC will be submitted about validation for the other channels.
Removed
p. 4
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.
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.
Modified
p. 4
• Connections into and out of the cardholder data environment (CDE).
• Critical system components within the CDE, such as
• Critical system components within the CDE, such as POI devices, databases, web servers, etc., and any other necessary payment components, as applicable.
Modified
p. 4
Indicate whether the environment includes segmentation to reduce the scope of the Assessment. Refer to “Segmentation” section of PCI DSS for guidance on segmentation.
Removed
p. 5
Does your company share cardholder data with any third-party service providers (for example, Qualified Integrator & Resellers (QIR), gateways, payment processors, payment service providers (PSP), web-hosting companies, airline booking agents, loyalty program agents, etc.)? Name of service provider: Description of services provided:
Modified
p. 5 → 6
Description of services provided by QIR:
Name of Service Provider: Description of Service(s) Provided:
Removed
p. 6
Section 2: Report on Compliance This Attestation of Compliance reflects the results of an onsite assessment, which is documented in an accompanying Report on Compliance (ROC).
The assessment documented in this attestation and in the ROC was completed on:
Have compensating controls been used to meet any requirement in the ROC? Yes No Were any requirements in the ROC identified as being not applicable (N/A)? Yes No Were any requirements not tested? Yes No Were any requirements in the ROC unable to be met due to a legal constraint? Yes No
(Check all that apply) The ROC was completed according to the PCI DSS Requirements and Security Assessment Procedures, Version (version number), and was completed according to the instructions therein.
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 PCI DSS …
The assessment documented in this attestation and in the ROC was completed on:
Have compensating controls been used to meet any requirement in the ROC? Yes No Were any requirements in the ROC identified as being not applicable (N/A)? Yes No Were any requirements not tested? Yes No Were any requirements in the ROC unable to be met due to a legal constraint? Yes No
(Check all that apply) The ROC was completed according to the PCI DSS Requirements and Security Assessment Procedures, Version (version number), and was completed according to the instructions therein.
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 PCI DSS …
Modified
p. 7 → 9
Section 3: Validation and Attestation Details Part 3. PCI DSS Validation This AOC is based on results noted in the ROC dated (ROC completion date).
Section 3 Validation and Attestation Details Part 3. PCI DSS Validation (ROC Section 1.7) This AOC is based on results noted in the ROC dated (Date of Report as noted in the ROC YYYY-MM-DD). Indicate below whether a full or partial PCI DSS assessment was completed:
Modified
p. 7 → 9
Based on the results documented in the ROC noted above, 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 (check one):
Based on the results documented in the ROC noted above, each signatory identified in any of Parts 3b-3d, as applicable, assert(s) the following compliance status for the entity identified in Part 2 of this document (select one):
Modified
p. 7 → 9
Compliant: All sections of the PCI DSS ROC are complete, all questions answered affirmatively, resulting in an overall COMPLIANT rating; thereby (Merchant Company Name) has demonstrated full compliance with the PCI DSS.
Compliant: All sections of the PCI DSS ROC are complete, and all assessed requirements are marked as being either In Place or Not Applicable, resulting in an overall COMPLIANT rating; thereby (Merchant Company Name) has demonstrated compliance with all PCI DSS requirements except those noted as Not Tested above.
Modified
p. 7 → 9
Non-Compliant: Not all sections of the PCI DSS ROC 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.
Non-Compliant: Not all sections of the PCI DSS ROC are complete, or one or more requirements are marked as Not in Place, resulting in an overall NON-COMPLIANT rating; thereby (Merchant Company Name) has not demonstrated compliance with PCI DSS requirements.
Modified
p. 7 → 9
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.
Target Date for Compliance: YYYY-MM-DD An entity submitting this form with a Non-Compliant status may be required to complete the Action Plan in Part 4 of this document. Confirm with the entity to which this AOC will be submitted before completing Part 4.
Modified
p. 7 → 9
Compliant but with Legal exception: One or more requirements are marked “Not in Place” due to a legal restriction that prevents the requirement from being met. This option requires additional review from acquirer or payment brand.
Compliant but with Legal exception: One or more assessed requirements in the ROC are marked as Not in Place due to a legal restriction that prevents the requirement from being met and all other assessed requirements are marked as being either In Place or Not Applicable, resulting in an overall COMPLIANT BUT WITH LEGAL EXCEPTION rating; thereby (Merchant Company Name) has demonstrated compliance with all PCI DSS requirements except those noted as Not Tested above or as Not in Place …
Modified
p. 7 → 9
If checked, complete the following:
If selected, complete the following:
Modified
p. 7 → 9
Affected Requirement Details of how legal constraint prevents requirement being met Part 3a. Acknowledgement of Status Signatory(s) confirms:
Affected Requirement Details of how legal constraint prevents requirement from being met
Modified
p. 7 → 10
All information within the above-referenced ROC and in this attestation fairly represents the results of my assessment in all material respects.
All information within the above-referenced ROC and in this attestation fairly represents the results of the Assessment in all material respects.
Removed
p. 8
ASV scans are being completed by the PCI SSC Approved Scanning Vendor (ASV Name) Part 3b. Merchant Attestation Signature of Merchant Executive Officer Date:
Modified
p. 8 → 10
Part 3c. Qualified Security Assessor (QSA) Acknowledgement (if applicable) If a QSA was involved or assisted with this assessment, describe the role performed:
Part 3c. Qualified Security Assessor (QSA) Acknowledgement If a QSA was involved or assisted with this Assessment, indicate the role performed:
Modified
p. 8 → 10
Signature of Duly Authorized Officer of QSA Company Date:
Signature of Duly Authorized Officer of QSA Company Date: YYYY-MM-DD Duly Authorized Officer Name: QSA Company:
Modified
p. 8 → 10
Part 3d. Internal Security Assessor (ISA) Involvement (if applicable) If an ISA(s) was involved or assisted with this assessment, identify the ISA personnel and describe the role performed:
Part 3d. PCI SSC Internal Security Assessor (ISA) Involvement If an ISA(s) was involved or assisted with this Assessment, indicate the role performed:
Removed
p. 9
Check with your acquirer or the payment brand(s) before completing Part 4.
Modified
p. 9 → 11
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 1 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 …
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 1 Install and maintain network security controls 2 Apply secure configurations to all system components 3 Protect stored account data Protect cardholder data with strong cryptography during transmission over open, public networks 5 Protect all systems and networks from malicious software 6 Develop and maintain secure systems and software Restrict access to system components and …