PAYMENT CARD INDUSTRY (PCI)DATA SECURITY STANDARD

Document Includes:

PCI DSS (PCI Data Security Standard Requirements and Security Assessment Procedures) Guidance on Scoping Guidance on the intent of all PCI DSS Requirements Details of testing procedures Guidance on Compensating Controls SAQ Instructions and Guidelines documents Information about all SAQs and their eligibility criteria.

How to determine which SAQ is suitable for your organization PCI DSS and PA-DSS Glossary of Terms, Abbreviations, and Acronyms Descriptions and definitions of terms used in the PCI DSS and self-assessment questionnaires These and other resources can be found on the PCI SSC website (www.pcisecuritystandards.org). Organizations are encouraged to review the PCI DSS and other supporting documents before beginning an assessment.

Expected Testing

PCI DSS, and provide a high-level description of the types of testing activities that should be performed in order to verify that a requirement has been met. Full details of testing procedures for each requirement can be found in the PCI DSS.
PCI DSS v3.2 SAQ A, Rev. 1.1 January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved.

Page v Completing the Self-Assessment Questionnaire For each question, status regarding that requirement. Only one response should be selected for each question. A description of the meaning of each response is provided in the table below:

Response When to use this response:

Yes, The expected testing has been performed, and all elements of the requirements have been met as stated. Yes with CCW (Compensating
Control Worksheet) The expected testing has been performed, and the requirement has been met with the assistance of a compensating control. All responses in this column require the completion of a Compensating Control Worksheet (CCW) in Appendix B of the SAQ. Information on the use of compensating controls and guidance on how to complete the worksheet provided in the PCI DSS. No Some or all elements of the requirement have not been met, are in the process of being implemented, or require further testing before it will be known if they are in place.

N/A(Not Applicable)

The requirement does not apply to the environment. (See Guidance for Non-Applicability of Certain, Specific Requirements below for example.) All responses in this column require a supporting explanation in Appendix C of the SAQ. Guidance for Non-Applicability of Certain, Specific Requirements If any requirements are deemed not applicable to your environment, select the specific requirement, and –entry.

Legal Exception

If your organization is subject to a legal restriction that prevents the organization from meeting a PCI DSS
PCI DSS v3.2 SAQ A, Rev. 1.1 Section 1: Assessment Information January 2017© 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved.

Page 2 Part 2b. Description of Payment Card Business

How and in what capacity does your business store, process, and/or transmit 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 the 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
Name
Version
Number
Application
Vendor
Is application
PA-DSS Listed?
PA-DSS Listing Expiry date (if applicable) Yes No

Part 2e. Description of Environment

Provides 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 the Network Segmentation section of PCI DSS for guidance on network segmentation) Yes No

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 1: Assessment Information January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 3

Part 2f. Third-Party Service Providers

Does your company use a Qualified Integrator & Reseller (QIR)? If Yes:
Name of QIR Company:
QIR Individual Name:
Description of services provided by QIR: Yes No

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.)? Yes No
If Yes:
Name of service provider: Description of services provided:
Note: Requirement 12.8 applies to all entities in this list.

Part 2g. Eligibility to Complete SAQ A

Merchant certifies eligibility to complete this shortened version of the Self-Assessment Questionnaire because of this payment channel: Merchant accepts only card-not-present (e-commerce or mail/telephone-order) transactions); All processing of cardholder data is entirely outsourced to PCI DSS validated third-party service providers; Merchant does not electronically store, process, or transmit any cardholder data on merchant systems or premises, but relies entirely on a third party(s) to handle all these functions; Merchant has confirmed that all third party(s) handling storage, processing, and/or transmission of cardholder data are PCI DSS compliant; and Any cardholder data the merchant retains is on paper (for example, printed reports or receipts), and these documents are not received electronically.

Additionally, for e-commerce channels:

All elements of the payment page(s) only and directly from a PCI DSS validated third-party service provider(s). 2018-07-22 PCI DSS v3.2 SAQ A, Rev. 1.1 Section 2: Self-Assessment Questionnaire January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 10

Appendix A: Additional PCI DSS Requirements

Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers
This appendix is not used for merchant assessments.

Appendix A2: Additional PCI DSS Requirements for Entities using SSL/early TLS
This appendix is not used for SAQ A merchant assessments

Appendix A3: Designated Entities Supplemental Validation (DESV)
This Appendix applies only to entities designated by a payment brand(s) or acquirer as requiring additional validation of existing PCI DSS requirements. Entities required to validate this Appendix should use the DESV Supplemental Reporting Template and Supplemental Attestation of Compliance for reporting, and consulting with the applicable payment brand and/or acquirer for submission procedures.

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 2: Self-Assessment Questionnaire January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 11

Appendix B: Compensating Controls Worksheet YES with CCW checked.

Note: Only companies that have undertaken a risk analysis and have legitimate technological or documented business constraints can consider the use of compensating controls to achieve compliance. Refer to Appendices B, C, and D of PCI DSS for information about compensating controls and guidance on how to complete this worksheet.

Requirement Number and Definition:

Information Required Explanation

1. Constraints List constraints precluding compliance with the original requirement.
2. Objective Define the objective of the original control; identify the objective met by the compensating control.
3. Identified Risk Identify any additional risk posed by the lack of the original control.
4. Definition of Compensating Controls Define the compensating controls and explain how they address the objectives of the original control and the increased risk if any.
5. Validation of Compensating Controls Defines how the compensating controls were validated and tested.
6. Maintenance Define process and controls in place to maintain compensating controls.

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 2: Self-Assessment Questionnaire January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 12

Appendix C: Explanation of Non-Applicability

If the (Not Applicable) column was checked in the questionnaire, use this worksheet to explain why the related requirement is not applicable to your organization. Requirement Reason Requirement is Not Applicable Example: 3.4 Cardholder data is never stored electronically Stripe

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 3: Validation and Attestation Details January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 13

Section 3: Validation and Attestation Details

Part 3. PCI DSS Validation

This AOC is based on results noted in SAQ A (Section 2), dated (SAQ completion date). Based on the results documented in the SAQ A 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):

Compliant: All sections of the PCI DSS SAQ are complete, and all questions are answered affirmatively, resulting in an overall COMPLIANT rating; 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 affirmatively, resulting in an overall NON-COMPLIANT rating, 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.

Compliant but with Legal exception: The restriction that prevents the requirement from being met. This option requires additional review from the acquirer or payment brand. If checked, complete the following: Affected Requirement Details of how legal constraint prevents requirement from being met Part 3a.

Acknowledgment of Status Signatory(s) confirms: (Check all that apply) PCI DSS Self-Assessment Questionnaire A, 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 PCI DSS compliance, as applicable to my environment, at all times. If my environment changes, I recognize I must reassess my environment and implement any additional PCI DSS requirements that apply.

PCI DSS v3.2 SAQ A, Rev. 1.1 Section 3: Validation and Attestation Details January 2017 © 2006-2017 PCI Security Standards Council, LLC. All Rights Reserved. Page 15

Part 4. Action Plan for Non-Compliant Requirements

Select the appropriate t for each requirement. If you o may be required to provide the date your Company expects to 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.
PCI DSS
Requirement* Description of Requirement
Compliant to PCI
DSS Requirements (Select One)
Remediation Date and Actions (If selected for any Requirement) YES NO
2 Do not use vendor-supplied defaults for system passwords and other security parameters
8 Identify and authenticate access to system components
9 Restrict physical access to cardholder data
12 Maintain a policy that addresses information security for all personnel

PCI DSS Requirements indicated here refer to the questions in Section 2 of the SAQ.
DOWNLOAD MAXPANDA’S PCI / DATA COMPLIANCE DOCS any time at Maxpanda.com

Click Here

The post PAYMENT CARD INDUSTRY (PCI)<br>DATA SECURITY STANDARD appeared first on Best News Anchor.