Document Comparison
aoc_saq_d_service_providers.pdf
→
AOC_SAQ_D_ServiceProvider_v3-1_rev1-1.pdf
41% similar
4 → 10
Pages
906 → 2140
Words
19
Content Changes
Content Changes
19 content changes. 10 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 service provider’s self-assessment with the Payment Card Industry Data Security Standard Requirements and Security Assessment Procedures (PCI DSS). Complete all sections: The service provider is responsible for ensuring that each section is completed by the relevant parties, as applicable. Contact the requesting payment brand for reporting and submission procedures.
Part 1. Service Provider and Qualified Security Assessor Information Part 1a. Service Provider Organization Information Company Name: DBA (doing business as):
ISA Name(s) (if applicable): Title:
Lead QSA Contact Name: Title:
Part 1. Service Provider and Qualified Security Assessor Information Part 1a. Service Provider Organization Information Company Name: DBA (doing business as):
ISA Name(s) (if applicable): Title:
Lead QSA Contact Name: Title:
Added
p. 3
Name of service(s) assessed:
Type of service(s) assessed:
Applications / software Infrastructure / Network Physical space (co-location) Security services 3-D Secure Hosting Provider Shared Hosting Provider Other Hosting (specify):
Managed Services (specify):
Systems security services IT support Physical security Terminal Management System Other services (specify):
POS / card present Internet / e-commerce MOTO / Call Center Other processing (specify):
Account Management Fraud and Chargeback Payment Gateway/Switch Back-Office Services Issuer Processing Prepaid Services Billing Management Loyalty Programs Records Management Clearing and Settlement Merchant Services Tax/Government Payments Network Provider Others (specify):
Note: These categories are provided for assistance only, and are not intended to limit or predetermine an entity’s service description. If you feel these categories don’t apply to your service, complete “Others.” If you’re unsure whether a category could apply to your service, consult with the applicable payment brand.
Managed Services (specify):
Systems security services IT support Physical security Terminal Management System Other services (specify):
Account Management Fraud and Chargeback Payment …
Type of service(s) assessed:
Applications / software Infrastructure / Network Physical space (co-location) Security services 3-D Secure Hosting Provider Shared Hosting Provider Other Hosting (specify):
Managed Services (specify):
Systems security services IT support Physical security Terminal Management System Other services (specify):
POS / card present Internet / e-commerce MOTO / Call Center Other processing (specify):
Account Management Fraud and Chargeback Payment Gateway/Switch Back-Office Services Issuer Processing Prepaid Services Billing Management Loyalty Programs Records Management Clearing and Settlement Merchant Services Tax/Government Payments Network Provider Others (specify):
Note: These categories are provided for assistance only, and are not intended to limit or predetermine an entity’s service description. If you feel these categories don’t apply to your service, complete “Others.” If you’re unsure whether a category could apply to your service, consult with the applicable payment brand.
Managed Services (specify):
Systems security services IT support Physical security Terminal Management System Other services (specify):
Account Management Fraud and Chargeback Payment …
Added
p. 4
Name of service(s) not assessed:
Type of service(s) not assessed:
Applications / software Hardware Infrastructure / Network Physical space (co-location) Storage Web Security services 3-D Secure Hosting Provider Shared Hosting Provider Other Hosting (specify):
POS / card present Internet / e-commerce MOTO / Call Center ATM Other processing (specify):
Provide a brief explanation why any checked services were not included in the assessment:
Part 2b. Description of Payment Card Business Describe how and in what capacity your business stores, processes, and/or transmits cardholder data.
Describe how and in what capacity your business is otherwise involved in or has the ability to impact the security of cardholder data.
Part 2c. Locations List types of facilities (for example, retail outlets, corporate offices, data centers, call centers, etc.) and a summary of locations included in the PCI DSS review.
Type of facility Number of facilities of this type Location(s) of facility (city, country) Example: Retail outlets 3 Boston, MA, USA
Type of service(s) not assessed:
Applications / software Hardware Infrastructure / Network Physical space (co-location) Storage Web Security services 3-D Secure Hosting Provider Shared Hosting Provider Other Hosting (specify):
POS / card present Internet / e-commerce MOTO / Call Center ATM Other processing (specify):
Provide a brief explanation why any checked services were not included in the assessment:
Part 2b. Description of Payment Card Business Describe how and in what capacity your business stores, processes, and/or transmits cardholder data.
Describe how and in what capacity your business is otherwise involved in or has the ability to impact the security of cardholder data.
Part 2c. Locations List types of facilities (for example, retail outlets, corporate offices, data centers, call centers, etc.) and a summary of locations included in the PCI DSS review.
Type of facility Number of facilities of this type Location(s) of facility (city, country) Example: Retail outlets 3 Boston, MA, USA
Added
p. 5
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) Part 2f. Third-Party Service Providers Does your company have a relationship with one or more third-party service providers (for example, gateways, payment processors, payment service providers (PSP), web-hosting companies, airline booking agents, loyalty program agents, etc.) for the purpose of the services being validated? Type of service provider: Description of services provided:
Note: Requirement 12.8 applies to all entities in …
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) Part 2f. Third-Party Service Providers Does your company have a relationship with one or more third-party service providers (for example, gateways, payment processors, payment service providers (PSP), web-hosting companies, airline booking agents, loyalty program agents, etc.) for the purpose of the services being validated? Type of service provider: Description of services provided:
Note: Requirement 12.8 applies to all entities in …
Added
p. 6
Full
• The requirement and all sub-requirements were assessed for that Requirement, and no sub- requirements were marked as “Not Tested” or “Not Applicable” in the SAQ.
Partial
• One or more sub-requirements of that Requirement were marked as “Not Tested” or “Not Applicable” in the SAQ.
None
• All sub-requirements of that Requirement were marked as “Not Tested” and/or “Not Applicable” in the SAQ.
For all requirements identified as either “Partial” or “None,” provide details in the “Justification for Approach” column, including:
Details of specific sub-requirements that were marked as either “Not Tested” and/or “Not Applicable” in the SAQ Reason why sub-requirement(s) were not tested or not applicable
Note: One table to be completed for each service covered by this AOC. Additional copies of this section are available on the PCI SSC website.
Name of Service Assessed:
PCI DSS Requirement Details of Requirements Assessed Full Partial None Justification for Approach (Required for all “Partial” …
• The requirement and all sub-requirements were assessed for that Requirement, and no sub- requirements were marked as “Not Tested” or “Not Applicable” in the SAQ.
Partial
• One or more sub-requirements of that Requirement were marked as “Not Tested” or “Not Applicable” in the SAQ.
None
• All sub-requirements of that Requirement were marked as “Not Tested” and/or “Not Applicable” in the SAQ.
For all requirements identified as either “Partial” or “None,” provide details in the “Justification for Approach” column, including:
Details of specific sub-requirements that were marked as either “Not Tested” and/or “Not Applicable” in the SAQ Reason why sub-requirement(s) were not tested or not applicable
Note: One table to be completed for each service covered by this AOC. Additional copies of this section are available on the PCI SSC website.
Name of Service Assessed:
PCI DSS Requirement Details of Requirements Assessed Full Partial None Justification for Approach (Required for all “Partial” …
Added
p. 10
Check with the applicable 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
• ServiceProvider Version Version 1.2
• Service
Payment Card Industry (PCI) Data Security Standard Attestation of Compliance for Self-Assessment Questionnaire D
• Service Providers For use with PCI DSS Version 3.1 Revision 1.1
• Service Providers For use with PCI DSS Version 3.1 Revision 1.1
Removed
p. 2
Part 1. Qualified Security Assessor Company Information (if applicable) Company Name:
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 (for example, 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:
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 (for example, 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:
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
Part 2. Service Provider Organization Information Company Name:
Part 1b. Qualified Security Assessor Company Information (if applicable) Company Name:
Removed
p. 3
Part 3a. Confirmation of Compliant Status Service Provider confirms:
Part 3b. Service Provider Acknowledgement Signature of Service Provider Executive Officer Date Service Provider Executive Officer Name Title Service Provider 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.
Part 3b. Service Provider Acknowledgement Signature of Service Provider Executive Officer Date Service Provider Executive Officer Name Title Service Provider 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 → 8
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.
Compliant: All sections of the PCI DSS SAQ are complete, all questions answered affirmatively, resulting in an overall COMPLIANT rating; thereby (Service Provider Company Name) has demonstrated full compliance with the PCI DSS.
Modified
p. 3 → 8
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:
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 (Service Provide Company Name) has not demonstrated full compliance with the PCI DSS.
Modified
p. 3 → 8
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 the payment brand(s) before completing Part 4.
Modified
p. 3 → 8
Self-Assessment Questionnaire D, Version (insert version number), was completed according to the instructions therein.
PCI DSS Self-Assessment Questionnaire D, Version (version of SAQ), was completed according to the instructions therein.
Modified
p. 3 → 8
All information within the above-referenced SAQ and in this attestation fairly represents the results of my assessment.
All information within the above-referenced SAQ and in this attestation fairly represents the results of my assessment in all material respects.
Modified
p. 3 → 8
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 → 10
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 …