Payment Card Industry (PCI)

Data Security Standard

Self-Assessment Questionnaire D
and Attestation of Compliance for
Merchants

All other SAQ-Eligible Merchants

For use with PCI DSS Version 3.2.1
June 2018
Document Changes

PCI DSS SAQ

Date Description
Version Revision

October 1.2 To align content with new PCI DSS v1.2 and to implement
2008 minor changes noted since original v1.1.

October 2.0 To align content with new PCI DSS v2.0 requirements and
2010 testing procedures.

February 3.0 To align content with PCI DSS v3.0 requirements and testing
2014 procedures and incorporate additional response options.

April 2015 3.1 Updated to align with PCI DSS v3.1. For details of PCI DSS
changes, see PCI DSS – Summary of Changes from PCI DSS
Version 3.0 to 3.1.

July 2015 3.1 1.1 Updated to remove references to “best practices” prior to June
30, 2015, and remove the PCI DSS v2 reporting option for
Requirement 11.3.

April 2016 3.2 1.0 Updated to align with PCI DSS v3.2. For details of PCI DSS
changes, see PCI DSS – Summary of Changes from PCI DSS
Version 3.1 to 3.2.

January 3.2 1.1 Updated version numbering to align with other SAQs
2017

June 2018 3.2.1 1.0 Updated to align with PCI DSS v3.2.1. For details of PCI DSS
changes, see PCI DSS – Summary of Changes from PCI DSS
Version 3.2 to 3.2.1.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page
Table of Contents
Document Changes................................................................................................................................... ii
Before You Begin...................................................................................................................................... iv
PCI DSS Self-Assessment Completion Steps......................................................................................iv
Understanding the Self-Assessment Questionnaire............................................................................v
Expected Testing ................................................................................................................................... v
Completing the Self-Assessment Questionnaire.................................................................................v
Guidance for Non-Applicability of Certain, Specific Requirements..................................................vi
Understanding the difference between Not Applicable and Not Tested................................................vii
Legal Exception ................................................................................................................................. vii
Section 1: Assessment Information.................................................................................................... 1
Section 2: Self-Assessment Questionnaire D for Service Providers................................................4
Build and Maintain a Secure Network and Systems............................................................................4
Requirement 1: Install and maintain a firewall configuration to protect data.......................................4
Requirement 2: Do not use vendor-supplied defaults for system passwords and other security
parameters................................................................................................................ 9
Protect Cardholder Data....................................................................................................................... 14
Requirement 3: Protect stored cardholder data................................................................................14
Requirement 4: Encrypt transmission of cardholder data across open, public networks...................22
Maintain a Vulnerability Management Program..................................................................................24
Requirement 5: Protect all systems against malware and regularly update anti-virus software or
programs................................................................................................................. 24
Requirement 6: Develop and maintain secure systems and applications.........................................26
Implement Strong Access Control Measures.....................................................................................35
Requirement 7: Restrict access to cardholder data by business need to know................................35
Requirement 8: Identify and authenticate access to system components.........................................37
Requirement 9: Restrict physical access to cardholder data.............................................................43
Regularly Monitor and Test Networks................................................................................................. 51
Requirement 10: Track and monitor all access to network resources and cardholder data................51
Requirement 11: Regularly test security systems and processes.......................................................57
Maintain an Information Security Policy............................................................................................. 65
Requirement 12: Maintain a policy that addresses information security for all personnel...................65
Appendix A: Additional PCI DSS Requirements.......................................................................73
Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers...........................73
Appendix A2: Additional PCI DSS Requirements for Entities using SSL/early TLS for Card-
Present POS POI Terminal Connections.................................................................73
Appendix A3: Designated Entities Supplemental Validation (DESV).............................................73
Appendix B: Compensating Controls Worksheet.....................................................................74
Appendix C: Explanation of Non-Applicability..........................................................................75
Appendix D: Explanation of Requirements Not Tested............................................................76
Section 3: Validation and Attestation Details...................................................................................77

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page
PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page
Before You Begin

SAQ D for Merchants applies to SAQ-eligible merchants not meeting the criteria for any other SAQ type.
Examples of merchant environments that would use SAQ D may include but are not limited to:
 E-commerce merchants who accept cardholder data on their website
 Merchants with electronic storage of cardholder data
 Merchants that don’t store cardholder data electronically but that do not meet the criteria of
another SAQ type
 Merchants with environments that might meet the criteria of another SAQ type, but that have
additional PCI DSS requirements applicable to their environment
While many organizations completing SAQ D will need to validate compliance with every PCI DSS
requirement, some organizations with very specific business models may find that some requirements do
not apply. See the guidance below for information about the exclusion of certain, specific requirements.

PCI DSS Self-Assessment Completion Steps

(a) Identify the applicable SAQ for your environmentrefer to the Self-Assessment Questionnaire
Instructions and Guidelines document on PCI SSC website for information.
(b) Confirm that your environment is properly scoped and meets the eligibility criteria for the SAQ you are
using.
(c) Assess your environment for compliance with PCI DSS requirements.
(d) Complete all sections of this document:
 Section 1 (Parts 1 & 2 of the AOC) – Assessment Information and Executive Summary
 Section 2 – PCI DSS Self-Assessment Questionnaire (SAQ D)
 Section 3 (Parts 3 & 4 of the AOC) – Validation and Attestation Details and Action Plan for Non-
Compliant Requirements (if applicable)
(e) Submit the SAQ and Attestation of Compliance (AOC), along with any other requested documentation
—such as ASV scan reports—to your acquirer, payment brand, or other requester.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page v
Understanding the Self-Assessment Questionnaire
The questions contained in the “PCI DSS Question” column in this self-assessment questionnaire are
based on the requirements in the PCI DSS.
Additional resources that provide guidance on PCI DSS requirements and how to complete the self-
assessment questionnaire have been provided to assist with the assessment process. An overview of
some of these resources is provided below:

Document Includes:
PCI DSS  Guidance on Scoping
(PCI Data Security Standard  Guidance on the intent of all PCI DSS Requirements
Requirements and Security Assessment  Details of testing procedures
Procedures)  Guidance on Compensating Controls
SAQ Instructions and Guidelines  Information about all SAQs and their eligibility criteria
documents  How to determine which SAQ is right for your
organization
PCI DSS and PA-DSS Glossary of  Descriptions and definitions of terms used in the PCI
Terms, Abbreviations, and Acronyms 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
The instructions provided in the “Expected Testing” column are based on the testing procedures in the
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.

Completing the Self-Assessment Questionnaire

For each question, there is a choice of responses to indicate your company’s status regarding that
requirement. Only one response should be selected for each question.
A description of the meaning for 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 requirement
have been met as stated.

Yes with CCW The expected testing has been performed, and the requirement has been met
with the assistance of a compensating control.
(Compensating
Control Worksheet) All responses in this column require 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 is provided in the PCI DSS.

No Some or all elements of the requirement have not been met, or are in the

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page vi
 Response When to use this response:

process of being implemented, or require further testing before it will be known

if they are in place.

N/A The requirement does not apply to the organization’s environment. (See
Guidance for Non-Applicability of Certain, Specific Requirements below for
(Not Applicable)
examples.)
All responses in this column require a supporting explanation in Appendix C of
the SAQ.

Not Tested The requirement was not included for consideration in the assessment, and
was not tested in any way. (See Understanding the difference between Not
Applicable and Not Tested below for examples of when this option should be
used.)
All responses in this column require a supporting explanation in Appendix D of
the SAQ.

Guidance for Non-Applicability of Certain, Specific Requirements

While many organizations completing SAQ D will need to validate compliance with every PCI DSS
requirement, some organizations with very specific business models may find that some requirements do
not apply. For example, a company that does not use wireless technology in any capacity would not be
expected to validate compliance with the sections of the PCI DSS that are specific to managing wireless
technology. Similarly, an organization that does not store any cardholder data electronically at any time
would not need to validate requirements related to secure storage of cardholder data (for example,
Requirement 3.4).
Examples of requirements with specific applicability include:
 The questions specific to securing wireless technologies (for example, Requirements 1.2.3, 2.1.1,
and 4.1.1) only need to be answered if wireless is present anywhere in your network. Note that
Requirement 11.1 (use of processes to identify unauthorized wireless access points) must still be
answered even if you don’t use wireless technologies in your network, since the process detects
any rogue or unauthorized devices that may have been added without your knowledge.
 The questions specific to application development and secure coding (Requirements 6.3 and 6.5)
only need to be answered if your organization develops its own custom applications.
 The questions for Requirements 9.1.1 and 9.3 only need to be answered for facilities with
“sensitive areas” as defined here: “Sensitive areas” refers to any data center, server room, or any
area that houses systems that store, process, or transmit cardholder data. This excludes the
areas where only point-of-sale terminals are present, such as the cashier areas in a retail store,
but does include retail store back-office server rooms that store cardholder data, and storage
areas for large quantities of cardholder data.
If any requirements are deemed not applicable to your environment, select the “N/A” option for that
specific requirement, and complete the “Explanation of Non-Applicability” worksheet in Appendix C for
each “N/A” entry.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page vii
Understanding the difference between Not Applicable and Not Tested
Requirements that are deemed to be not applicable to an environment must be verified as such. Using
the wireless example above, for an organization to select “N/A” for Requirements 1.2.3, 2.1.1, and 4.1.1,
the organization would first need to confirm that there are no wireless technologies used in their
cardholder data environment (CDE) or that connect to their CDE. Once this has been confirmed, the
organization may select “N/A” for those specific requirements,
If a requirement is completely excluded from review without any consideration as to whether it could
apply, the “Not Tested” option should be selected. Examples of situations where this could occur may
include:
 An organization may be asked by their acquirer to validate a subset of requirements—for
example: using the prioritized approach to validate certain milestones.
 An organization may wish to validate a new security control that impacts only a subset of
requirements—for example, implementation of a new encryption methodology that requires
assessment of PCI DSS Requirements 2, 3, and 4.
 A service provider organization might offer a service which covers only a limited number of PCI
DSS requirements—for example, a physical storage provider may only wish to validate the
physical security controls per PCI DSS Requirement 9 for their storage facility.
In these scenarios, the organization only wishes to validate certain PCI DSS requirements even though
other requirements might also apply to their environment.

Legal Exception
If your organization is subject to a legal restriction that prevents the organization from meeting a PCI DSS
requirement, check the “No” column for that requirement and complete the relevant attestation in Part 3.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page viii
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 your acquirer (merchant bank) or the payment brands to determine
reporting and submission procedures.

Part 1. Merchant and Qualified Security Assessor Information

Part 1a. Merchant Organization Information
Company Name: DBA (doing
business as):
Contact Name: Title:
Telephone: E-mail:
Business Address: City:
State/Province: Country: Zip:
URL:

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

Company Name:
Lead QSA Contact Name: Title:
Telephone: E-mail:
Business Address: City:
State/Province: Country: Zip:
URL:

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 Which payment channels are covered by this
serve? SAQ?
Mail order/telephone order (MOTO) Mail order/telephone order (MOTO)
E-Commerce E-Commerce
Card-present (face-to-face) 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.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 1: Assessment Information June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 1
 Part 2. Executive Summary (continued)
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.
Number of facilities
Type of facility Location(s) of facility (city, country)
of this type
Example: Retail outlets 3 Boston, MA, USA

Part 2d. Payment Applications

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 Application Is application PA-DSS Listing Expiry
Name Number Vendor PA-DSS Listed? date (if applicable)

Yes No
Yes No
Yes No
Yes No
Yes No

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 Yes No
environment?
(Refer to “Network Segmentation” section of PCI DSS for guidance on network
segmentation.)

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 1: Assessment Information June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 2
 Part 2f. Third-Party Service Providers
Does your company use a Qualified Integrator & Reseller (QIR)? Yes No

If Yes:

Name of QIR Company:

QIR Individual Name:

Description of services provided by QIR:

Does your company share cardholder data with any third-party service providers (for Yes No
example, Qualified Integrator & Resellers (QIR), gateways, payment processors, payment
service providers (PSP), web-hosting companies, airline booking agents, loyalty program
agents, etc.)?

If Yes:

Name of service provider: Description of services provided:

Note: Requirement 12.8 applies to all entities in this list.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 1: Assessment Information June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 3
Section 2: Self-Assessment Questionnaire D for Merchants

Note: The following questions are numbered according to PCI DSS requirements and testing procedures, as defined in the PCI DSS
Requirements and Security Assessment Procedures document.

Self-assessment completion date:

Build and Maintain a Secure Network and Systems
Requirement 1: Install and maintain a firewall configuration to protect data
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
1.1 Are firewall and router configuration standards
established and implemented to include the following:

1.1.1 Is there a formal process for approving and testing all  Review documented process.
network connections and changes to the firewall and  Interview personnel.
router configurations?
 Examine network configurations.

1.1.2 (a) Is there a current network diagram that documents all  Review current network diagram.
connections between the cardholder data  Examine network configurations.
environment and other networks, including any
wireless networks?
(b) Is there a process to ensure the diagram is kept  Interview responsible personnel.
current?
1.1.3 (a) Is there a current diagram that shows all cardholder  Review current dataflow diagram.
data flows across systems and networks?  Examine network configurations.
(b) Is there a process to ensure the diagram is kept  Interview personnel.
current?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 4
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
1.1.4 (a) Is a firewall required and implemented at each  Review firewall configuration
Internet connection and between any demilitarized standards.
zone (DMZ) and the internal network zone?  Observe network configurations to
verify that a firewall(s) is in place.
(b) Is the current network diagram consistent with the  Compare firewall configuration
firewall configuration standards? standards to current network
diagram.

1.1.5 Are groups, roles, and responsibilities for logical  Review firewall and router
management of network components assigned and configuration standards.
documented in the firewall and router configuration  Interview personnel.
standards?

1.1.6 (a) Do firewall and router configuration standards  Review firewall and router
include a documented list of services, protocols, and configuration standards.
ports, including business justification and approval
for each?
(b) Are all insecure services, protocols, and ports  Review firewall and router
identified, and are security features documented and configuration standards.
implemented for each identified service?  Examine firewall and router
configurations.

1.1.7 (a) Do firewall and router configuration standards  Review firewall and router
require review of firewall and router rule sets at least configuration standards.
every six months?
(b) Are firewall and router rule sets reviewed at least  Examine documentation from
every six months? firewall reviews.

1.2 Do firewall and router configurations restrict connections

between untrusted networks and any system in the
cardholder data environment as follows:
Note: An “untrusted network” is any network that is
external to the networks belonging to the entity under
review, and/or which is out of the entity’s ability to control
or manage.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 5
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
1.2.1 (a) Is inbound and outbound traffic restricted to that  Review firewall and router
which is necessary for the cardholder data configuration standards.
environment?  Examine firewall and router
configurations.
(b) Is all other inbound and outbound traffic specifically  Review firewall and router
denied (for example by using an explicit “deny all” or configuration standards.
an implicit deny after allow statement)?  Examine firewall and router
configurations.

1.2.2 Are router configuration files secured from unauthorized  Review firewall and router
access and synchronized—for example, the running (or configuration standards.
active) configuration matches the start-up configuration  Examine router configuration files
(used when machines are booted)? and router configurations.

1.2.3 Are perimeter firewalls installed between all wireless  Review firewall and router
networks and the cardholder data environment, and are configuration standards.
these firewalls configured to deny or, if traffic is  Examine firewall and router
necessary for business purposes, permit only authorized configurations.
traffic between the wireless environment and the
cardholder data environment?

1.3 Is direct public access prohibited between the Internet

and any system component in the cardholder data
environment, as follows:

1.3.1 Is a DMZ implemented to limit inbound traffic to only  Examine firewall and router
system components that provide authorized publicly configurations.
accessible services, protocols, and ports?

1.3.2 Is inbound Internet traffic limited to IP addresses within  Examine firewall and router
the DMZ? configurations.

1.3.3 Are anti-spoofing measures implemented to detect and  Examine firewall and router
block forged sourced IP addresses from entering the configurations.
network?
(For example, block traffic originating from the internet
with an internal address.)

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 6
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
1.3.4 Is outbound traffic from the cardholder data environment  Examine firewall and router
to the Internet explicitly authorized? configurations.

1.3.5 Are only established connections permitted into the  Examine firewall and router
network? configurations.

1.3.6 Are system components that store cardholder data (such  Examine firewall and router
as a database) placed in an internal network zone, configurations.
segregated from the DMZ and other untrusted networks?

1.3.7 (a) Are methods in place to prevent the disclosure of  Examine firewall and router
private IP addresses and routing information to the configurations.
Internet?
Note: Methods to obscure IP addressing may include,
but are not limited to:
• Network Address Translation (NAT)
• Placing servers containing cardholder data behind
proxy servers/firewalls,
• Removal or filtering of route advertisements for
private networks that employ registered addressing,
• Internal use of RFC1918 address space instead of
registered addresses.
(b) Is any disclosure of private IP addresses and routing  Examine firewall and router
information to external entities authorized? configurations.
 Interview personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 7
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
1.4 (a) Is personal firewall software (or equivalent  Review policies and configuration
functionality) installed and active on any portable standards.
computing devices (including company and/or  Examine mobile and/or employee-
employee-owned) that connect to the Internet when owned devices.
outside the network (for example, laptops used by
employees), and which are also used to access the
CDE?
(b) Is the personal firewall software (or equivalent  Review policies and configuration
functionality) configured to specific configuration standards.
settings, actively running, and not alterable by users  Examine mobile and/or employee-
of mobile and/or employee-owned devices? owned devices.

1.5 Are security policies and operational procedures for  Review security policies and
managing firewalls: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 8
Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
2.1 (a) Are vendor-supplied defaults always changed before  Review policies and procedures.
installing a system on the network?  Examine vendor documentation.
This applies to ALL default passwords, including but not  Observe system configurations
limited to those used by operating systems, software that and account settings.
provides security services, application and system
accounts, point-of-sale (POS) terminals, payment  Interview personnel.
applications, Simple Network Management Protocol
(SNMP) community strings, etc.).

(b) Are unnecessary default accounts removed or  Review policies and procedures.
disabled before installing a system on the network?  Review vendor documentation.
 Examine system configurations
and account settings.
 Interview personnel.
2.1.1 For wireless environments connected to the cardholder
data environment or transmitting cardholder data, are
ALL wireless vendor defaults changed at installations, as
follows:
(a) Are encryption keys changed from default at  Review policies and procedures.
installation, and changed anytime anyone with  Review vendor documentation.
knowledge of the keys leaves the company or
changes positions?  Interview personnel.

(b) Are default SNMP community strings on wireless  Review policies and procedures.
devices changed at installation?  Review vendor documentation.
 Interview personnel.
 Examine system configurations.
(c) Are default passwords/passphrases on access points  Review policies and procedures.
changed at installation?  Interview personnel.
 Examine system configurations.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 9
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
2.1.1 (d) Is firmware on wireless devices updated to support  Review policies and procedures.
(cont.) strong encryption for authentication and transmission  Review vendor documentation.
over wireless networks?
 Examine system configurations.
(e) Are other security-related wireless vendor defaults  Review policies and procedures.
changed, if applicable?  Review vendor documentation.
 Examine system configurations.
2.2 (a) Are configuration standards developed for all system  Review system configuration
components and are they consistent with industry- standards.
accepted system hardening standards?  Review industry-accepted
Sources of industry-accepted system hardening hardening standards.
standards may include, but are not limited to, SysAdmin  Review policies and procedures.
Audit Network Security (SANS) Institute, National
Institute of Standards Technology (NIST), International  Interview personnel.
Organization for Standardization (ISO), and Center for
Internet Security (CIS).

(b) Are system configuration standards updated as new  Review policies and procedures.
vulnerability issues are identified, as defined in  Interview personnel.
Requirement 6.1?
(c) Are system configuration standards applied when  Review policies and procedures.
new systems are configured?  Interview personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 10
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
2.2 (d) Do system configuration standards include all of the  Review system configuration
(cont.) following: standards.
- Changing of all vendor-supplied defaults and
elimination of unnecessary default accounts?
- Implementing only one primary function per server
to prevent functions that require different security
levels from co-existing on the same server?
- Enabling only necessary services, protocols,
daemons, etc., as required for the function of the
system?
- Implementing additional security features for any
required services, protocols or daemons that are
considered to be insecure?
- Configuring system security parameters to
prevent misuse?
- Removing all unnecessary functionality, such as
scripts, drivers, features, subsystems, file
systems, and unnecessary web servers?
2.2.1 (a) Is only one primary function implemented per server,  Examine system configurations.
to prevent functions that require different security
levels from co-existing on the same server?
For example, web servers, database servers, and DNS
should be implemented on separate servers.

(b) If virtualization technologies are used, is only one  Examine system configurations.
primary function implemented per virtual system
component or device?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 11
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
2.2.2 (a) Are only necessary services, protocols, daemons,  Review configuration standards.
etc. enabled as required for the function of the  Examine system configurations.
system (services and protocols not directly needed
to perform the device’s specified function are
disabled)?
(b) Are all enabled insecure services, daemons, or  Review configuration standards
protocols justified per documented configuration  Interview personnel.
standards?  Examine configuration settings.
 Compare enabled services, etc. to
documented justifications.
2.2.3 Are additional security features documented and  Review configuration standards.
implemented for any required services, protocols or  Examine configuration settings.
daemons that are considered to be insecure?
2.2.4 (a) Are system administrators and/or personnel that  Interview personnel.
configure system components knowledgeable about
common security parameter settings for those
system components?
(b) Are common system security parameters settings  Review system configuration
included in the system configuration standards? standards.
(c) Are security parameter settings set appropriately on  Examine system components.
system components?  Examine security parameter
settings.
 Compare settings to system
configuration standards.
2.2.5 (a) Has all unnecessary functionality—such as scripts,  Examine security parameters on
drivers, features, subsystems, file systems, and system components.
unnecessary web servers—been removed?
(b) Are enabled functions documented and do they  Review documentation.
support secure configuration?  Examine security parameters on
system components.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 12
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
2.2.5 (c) Is only documented functionality present on system  Review documentation.
(cont.) components?  Examine security parameters on
system components.
2.3 Is non-console administrative access encrypted as
follows:
(a) Is all non-console administrative access encrypted  Examine system components.
with strong cryptography, and is a strong encryption  Examine system configurations.
method invoked before the administrator’s password
is requested?  Observe an administrator log on.

(b) Are system services and parameter files configured  Examine system components.
to prevent the use of Telnet and other insecure  Examine services and file.s
remote login commands?
(c) Is administrator access to web-based management  Examine system components.
interfaces encrypted with strong cryptography?  Observe an administrator log on.
(d) For the technology in use, is strong cryptography  Examine system components.
implemented according to industry best practice  Review vendor documentation.
and/or vendor recommendations?
 Interview personnel.
2.4 (a) Is an inventory maintained for systems components  Examine system inventory.
that are in scope for PCI DSS, including a list of
hardware and software components and a
description of function/use for each?
(b) Is the documented inventory kept current?  Interview personnel.

2.5 Are security policies and operational procedures for  Review security policies and
managing vendor defaults and other security parameters: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?
2.6 This requirement applies only to service providers.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 13
Protect Cardholder Data
Requirement 3: Protect stored cardholder data
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.1 Are data-retention and disposal policies, procedures, and
processes implemented as follows:
(a) Is data storage amount and retention time limited to  Review data retention and
that required for legal, regulatory, and/or business disposal policies and
requirements? procedures.
 Interview personnel.
(b) Are there defined processes in place for securely  Review policies and procedures.
deleting cardholder data when no longer needed for  Interview personnel.
legal, regulatory, and/or business reasons?
 Examine deletion mechanism.
(c) Are there specific retention requirements for  Review policies and procedures.
cardholder data?  Interview personnel.
For example, cardholder data needs to be held for X  Examine retention requirements.
period for Y business reasons.

(d) Is there a quarterly process for identifying and  Review policies and procedures.
securely deleting stored cardholder data that  Interview personnel.
exceeds defined retention requirements?
 Observe deletion processes.
(e) Does all stored cardholder data meet the  Examine files and system
requirements defined in the data-retention policy? records.

3.2 (a) This testing procedure applies only to Issuers.

(b) This testing procedure applies only to Issuers.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 14
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.2 (c) Is sensitive authentication data deleted or rendered  Review policies and procedures.
(cont.) unrecoverable upon completion of the authorization  Examine system configurations.
process?
 Examine deletion processes.
(d) Do all systems adhere to the following requirements
regarding non-storage of sensitive authentication
data after authorization (even if encrypted):

3.2.1 The full contents of any track (from the magnetic stripe  Examine data sources including:
located on the back of a card, equivalent data contained - Incoming transaction data
on a chip, or elsewhere) are not stored after
authorization? - All logs

This data is alternatively called full track, track, track 1, - History files
track 2, and magnetic-stripe data. - Trace files
Note: In the normal course of business, the following - Database schema
data elements from the magnetic stripe may need to be
- Database contents
retained:
• The cardholder’s name,
• Primary account number (PAN),
• Expiration date, and
• Service code
To minimize risk, store only these data elements as
needed for business.

3.2.2 The card verification code or value (three-digit or four-  Examine data sources including:
digit number printed on the front or back of a payment - Incoming transaction data
card) is not stored after authorization?
- All logs
- History files
- Trace files
- Database schema
- Database contents

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 15
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.2.3 The personal identification number (PIN) or the encrypted  Examine data sources including:
PIN block is not stored after authorization? - Incoming transaction data
- All logs
- History files
- Trace files
- Database schema
- Database contents

3.3 Is the PAN masked when displayed (the first six and last  Review policies and procedures.
four digits are the maximum number of digits to be  Review roles that need access to
displayed) such that only personnel with a legitimate displays of full PAN.
business need can see more than the first six/last four
 Examine system configurations.
digits of the PAN?
 Observe displays of PAN.
Note: This requirement does not supersede stricter
requirements in place for displays of cardholder data—for
example, legal or payment card brand requirements for
point-of-sale (POS) receipts.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 16
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.4 Is PAN rendered unreadable anywhere it is stored  Examine vendor documentation.
(including data repositories, portable digital media,  Examine data repositories.
backup media, and in audit logs), by using any of the
 Examine removable media.
following approaches?
 Examine audit logs, including
 One-way hashes based on strong cryptography
payment application logs.
(hash must be of the entire PAN)
 Truncation (hashing cannot be used to replace the
truncated segment of PAN)
 Index tokens and pads (pads must be securely
stored)
 Strong cryptography with associated key
management processes and procedures.
Note: It is a relatively trivial effort for a malicious
individual to reconstruct original PAN data if they have
access to both the truncated and hashed version of a
PAN. Where hashed and truncated versions of the same
PAN are present in an entity’s environment, additional
controls must be in place to ensure that the hashed and
truncated versions cannot be correlated to reconstruct
the original PAN.

3.4.1 If disk encryption (rather than file- or column-level

database encryption) is used, is access managed as
follows:
Note: This requirement applies in addition to all other PCI
DSS encryption and key management requirements.

(a) Is logical access to encrypted file systems managed  Examine system configurations.
separately and independently of native operating  Observe the authentication
system authentication and access control process.
mechanisms (for example, by not using local user
account databases or general network login
credentials)?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 17
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.4.1 (b) Are cryptographic keys stored securely (for example,  Observe processes.
(cont.) stored on removable media that is adequately  Interview personnel.
protected with strong access controls)?
(c) Is cardholder data on removable media encrypted  Examine system configurations.
wherever stored?  Observe processes.
Note: If disk encryption is not used to encrypt removable
media, the data stored on this media will need to be
rendered unreadable through some other method.

3.5 Are keys used to secure stored cardholder data protected

against disclosure and misuse as follows:
Note: This requirement applies to keys used to encrypt
stored cardholder data, and also applies to key-
encrypting keys used to protect data-encrypting keys.
Such key-encrypting keys must be at least as strong as
the data-encrypting key.

3.5.1 This requirement applies only to service providers.

3.5.2 Is access to cryptographic keys restricted to the fewest  Examine user access lists.
number of custodians necessary?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 18
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.5.3 Are secret and private cryptographic keys used to  Review documented procedures.
encrypt/decrypt cardholder data stored in one (or more) of  Examine system configurations
the following forms at all times? and key storage locations,
 Encrypted with a key-encrypting key that is at least including for key-encrypting
as strong as the data-encrypting key, and that is keys.
stored separately from the data-encrypting key
 Within a secure cryptographic device (such as a
hardware (host) security module (HSM) or PTS-
approved point-of-interaction device)
 As at least two full-length key components or key
shares, in accordance with an industry-accepted
method.
Note: It is not required that public keys be stored in one
of these forms.

3.5.4 Are cryptographic keys stored in the fewest possible  Examine key-storage locations.
locations?  Observe processes.

3.6 (a) Are all key-management processes and procedures  Review key-management
fully documented and implemented for cryptographic procedures.
keys used for encryption of cardholder data?
(b) This testing procedure applies only to service
providers.
(c) Are key-management processes and procedures
implemented to require the following:

3.6.1 Do cryptographic key procedures include the generation  Review key-management

of strong cryptographic keys? procedures.
 Observe key-generation
procedures.

3.6.2 Do cryptographic key procedures include secure  Review key management

cryptographic key distribution? procedures.
 Observe the key-distribution
method.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 19
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.6.3 Do cryptographic key procedures include secure  Review key-management
cryptographic key storage? procedures.
 Observe the method for secure
storage of keys.

3.6.4 Do cryptographic key procedures include cryptographic  Review key-management

key changes for keys that have reached the end of their procedures.
defined cryptoperiod (for example, after a defined period  Interview personnel.
of time has passed and/or after a certain amount of
cipher-text has been produced by a given key), as
defined by the associated application vendor or key
owner, and based on industry best practices and
guidelines (for example, NIST Special Publication 800-
57)?

3.6.5 (a) Do cryptographic key procedures include retirement  Review key-management

or replacement (for example, archiving, destruction, procedures.
and/or revocation) of cryptographic keys when the  Interview personnel.
integrity of the key has been weakened (for example,
departure of an employee with knowledge of a clear-
text key)?
(b) Do cryptographic key procedures include  Review key-management
replacement of known or suspected compromised procedures.
keys?  Interview personnel.
(c) If retired or replaced cryptographic keys are  Review key-management
retained, are these keys only used for procedures.
decryption/verification purposes, and not used for  Interview personnel.
encryption operations?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 20
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
3.6.6 If manual clear-text key-management operations are  Review key-management
used, do cryptographic key procedures include split procedures.
knowledge and dual control of cryptographic keys as  Interview personnel and/or.
follows:
 Observe processes.
 Do split knowledge procedures require that key
components are under the control of at least two
people who only have knowledge of their own key
components?
AND
 Do dual control procedures require that at least two
people are required to perform any key management
operations and no one person has access to the
authentication materials (for example, passwords or
keys) of another?
Note: Examples of manual key management operations
include, but are not limited to: key generation,
transmission, loading, storage and destruction.

3.6.7 Do cryptographic key procedures include the prevention  Review procedures.

of unauthorized substitution of cryptographic keys?  Interview personnel and/or
 Observe processes.

3.6.8 Are cryptographic key custodians required to formally  Review procedures.

acknowledge (in writing or electronically) that they  Review documentation or other
understand and accept their key-custodian evidence.
responsibilities?
3.7 Are security policies and operational procedures for  Review security policies and
protecting stored cardholder data: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 21
Requirement 4: Encrypt transmission of cardholder data across open, public networks
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
4.1 (a) Are strong cryptography and security protocols used to  Review documented
safeguard sensitive cardholder data during transmission standards.
over open, public networks?  Review policies and
Note: Examples of open, public networks include but are not procedures.
limited to the Internet; wireless technologies, including  Review all locations where
802.11 and Bluetooth; cellular technologies, for example, CHD is transmitted or
Global System for Mobile communications (GSM), Code received.
division multiple access (CDMA); and General Packet Radio
Service (GPRS).  Examine system
configurations.
(b) Are only trusted keys and/or certificates accepted?  Observe inbound and
outbound transmissions.
 Examine keys and certificates.
(c) Are security protocols implemented to use only secure  Examine system
configurations, and to not support insecure versions or configurations.
configurations?
(d) Is the proper encryption strength implemented for the  Review vendor documentation.
encryption methodology in use (check vendor  Examine system
recommendations/best practices)? configurations.
(e) For TLS implementations, is TLS enabled whenever  Examine system
cardholder data is transmitted or received? configurations.
For example, for browser-based implementations:
• “HTTPS” appears as the browser Universal Record
Locator (URL) protocol, and
• Cardholder data is only requested if “HTTPS” appears as
part of the URL.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 22
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
4.1.1 Are industry best practices used to implement strong  Review documented
encryption for authentication and transmission for wireless standards.
networks transmitting cardholder data or connected to the  Review wireless networks.
cardholder data environment?
 Examine system configuration
settings.

4.2 (a) Are PANs rendered unreadable or secured with strong  Observe processes.
cryptography whenever they are sent via end-user  Review outbound
messaging technologies (for example, e-mail, instant transmissions.
messaging, SMS, chat, etc.)?
(b) Are policies in place that state that unprotected PANs  Review policies and
are not to be sent via end-user messaging procedures.
technologies?
4.3 Are security policies and operational procedures for  Review security policies and
encrypting transmissions of cardholder data: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 23
Maintain a Vulnerability Management Program
Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
5.1 Is anti-virus software deployed on all systems commonly  Examine system configurations.
affected by malicious software?

5.1.1 Are anti-virus programs capable of detecting, removing,  Review vendor documentation.
and protecting against all known types of malicious  Examine system configurations.
software (for example, viruses, Trojans, worms, spyware,
adware, and rootkits)?

5.1.2 Are periodic evaluations performed to identify and  Interview personnel.

evaluate evolving malware threats in order to confirm
whether those systems considered to not be commonly
affected by malicious software continue as such?

5.2 Are all anti-virus mechanisms maintained as follows:

(a) Are all anti-virus software and definitions kept  Examine policies and
current? procedures.
 Examine anti-virus
configurations, including the
master installation.
 Examine system components.
(b) Are automatic updates and periodic scans enabled  Examine anti-virus
and being performed? configurations, including the
master installation.
 Examine system components.
(c) Are all anti-virus mechanisms generating audit logs,  Examine anti-virus
and are logs retained in accordance with PCI DSS configurations.
Requirement 10.7?  Review log retention processes.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 24
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
5.3 Are all anti-virus mechanisms:  Examine anti-virus
 Actively running? configurations.
 Unable to be disabled or altered by users?  Examine system components.
Note: Anti-virus solutions may be temporarily disabled  Observe processes.
only if there is legitimate technical need, as authorized by  Interview personnel.
management on a case-by-case basis. If anti-virus
protection needs to be disabled for a specific purpose, it
must be formally authorized. Additional security measures
may also need to be implemented for the period of time
during which anti-virus protection is not active.

5.4 Are security policies and operational procedures for  Review security policies and
protecting systems against malware: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 25
Requirement 6: Develop and maintain secure systems and applications
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.1 Is there a process to identify security vulnerabilities,  Review policies and procedures.
including the following:  Interview personnel.
 Using reputable outside sources for vulnerability  Observe processes.
information?
 Assigning a risk ranking to vulnerabilities that includes
identification of all “high” risk and “critical”
vulnerabilities?
Note: Risk rankings should be based on industry best
practices as well as consideration of potential impact. For
example, criteria for ranking vulnerabilities may include
consideration of the CVSS base score and/or the
classification by the vendor, and/or type of systems
affected.
Methods for evaluating vulnerabilities and assigning risk
ratings will vary based on an organization’s environment
and risk assessment strategy. Risk rankings should, at a
minimum, identify all vulnerabilities considered to be a
“high risk” to the environment. In addition to the risk
ranking, vulnerabilities may be considered “critical” if they
pose an imminent threat to the environment, impact critical
systems, and/or would result in a potential compromise if
not addressed. Examples of critical systems may include
security systems, public-facing devices and systems,
databases, and other systems that store, process or
transmit cardholder data.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 26
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.2 (a) Are all system components and software protected  Review policies and procedures.
from known vulnerabilities by installing applicable
vendor-supplied security patches?
(b) Are critical security patches installed within one month  Review policies and procedures.
of release?  Examine system components.
Note: Critical security patches should be identified  Compare list of security patches
according to the risk ranking process defined in installed to recent vendor patch
Requirement 6.1. lists.

6.3 (a) Are software- development processes based on  Review software development
industry standards and/or best practices? processes.
 Observe processes.
 Interview personnel.
(b) Is information security included throughout the  Review software development
software-development life cycle? processes.
 Observe processes.
 Interview personnel.
(c) Are software applications developed in accordance  Review software development
with PCI DSS (for example, secure authentication and processes.
logging)?  Observe processes.
 Interview personnel.
(d) Do software development processes ensure the
following at 6.3.1 - 6.3.2:

6.3.1 Are development, test, and/or custom application  Review software development
accounts, user IDs, and passwords removed before processes.
applications become active or are released to customers?  Interview personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 27
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.3.2 Is all custom code reviewed prior to release to production  Review policies and procedures.
or customers to identify any potential coding vulnerability  Interview personnel.
(using either manual or automated processes as follows:
 Examine recent changes and
 Are code changes reviewed by individuals other than change records.
the originating code author, and by individuals who
are knowledgeable about code review techniques and
secure coding practices?
 Do code reviews ensure code is developed according
to secure coding guidelines?
 Are appropriate corrections are implemented prior to
release?
 Are code review results are reviewed and approved
by management prior to release?
Note: This requirement for code reviews applies to all
custom code (both internal and public-facing), as part of
the system development life cycle. Code reviews can be
conducted by knowledgeable internal personnel or third
parties. Public-facing web applications are also subject to
additional controls, to address ongoing threats and
vulnerabilities after implementation, as defined at PCI
DSS Requirement 6.6.

6.4 Are change control processes and procedures followed for

all changes to system components to include the
following:

6.4.1 (a) Are development/test environments separate from the  Review change control
production environment? processes and procedures.
 Examine network documentation
and network device
configurations.
(b) Is access control in place to enforce the separation  Review change control
between the development/test environments and the processes and procedures.
production environment?  Examine access control settings.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 28
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.4.2 Is there separation of duties between personnel assigned  Review change control
to the development/test environments and those assigned processes and procedures.
to the production environment?  Observe processes.
 Interview personnel.

6.4.3 Are production data (live PANs) not used for testing or  Review change control
development? processes and procedures.
 Observe processes.
 Interview personnel.
 Examine test data.

6.4.4 Are test data and accounts removed from system  Review change control
components before the system becomes active / goes into processes and procedures.
production?  Observe processes.
 Interview personnel.
 Examine production systems.

6.4.5 (a) Are change-control procedures documented and  Review change control
require the following? processes and procedures.
- Documentation of impact
- Documented change control approval by
authorized parties
- Functionality testing to verify that the change
does not adversely impact the security of the
system
- Back-out procedures
(b) Are the following performed and documented for all
changes:

6.4.5.1 Documentation of impact?  Trace changes to change control

documentation.
 Examine change control
documentation.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 29
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.4.5.2 Documented approval by authorized parties?  Trace changes to change control
documentation.
 Examine change control
documentation.

6.4.5.3 (a) Functionality testing to verify that the change does not  Trace changes to change control
adversely impact the security of the system? documentation.
 Examine change control
documentation.
(b) For custom code changes, testing of updates for  Trace changes to change control
compliance with PCI DSS Requirement 6.5 before documentation.
being deployed into production?  Examine change control
documentation.

6.4.5.4 Back-out procedures?  Trace changes to change control

documentation.
 Examine change control
documentation.

6.4.6 Upon completion of a significant change, are all relevant  Trace changes to change control
PCI DSS requirements implemented on all new or documentation.
changed systems and networks, and documentation  Examine change control
updated as applicable? documentation.
 Interview personnel.
 Observe affected systems or
networks.

6.5 (a) Do software-development processes address  Review software-development

common coding vulnerabilities? policies and procedures.
(b) Are developers trained at least annually in up-to-date  Examine software-development
secure coding techniques, including how to avoid policies and procedures.
common coding vulnerabilities?  Examine training records.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 30
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
(c) Are applications developed based on secure coding
guidelines to protect applications from, at a minimum,
the following vulnerabilities:
Note: The vulnerabilities listed at 6.5.1 through 6.5.10
were current with industry best practices when this version
of PCI DSS was published. However, as industry best
practices for vulnerability management are update d (for
example, the Open Web Application Security Project
(OWASP) Guide, SANS CWE Top 25, CERT Secure
Coding, etc.), the current best practices must be used for
these requirements.

6.5.1 Do coding techniques address injection flaws, particularly  Examine software-development

SQL injection? policies and procedures.
Note: Also consider OS Command Injection, LDAP and  Interview responsible personnel.
XPath injection flaws as well as other injection flaws.

6.5.2 Do coding techniques address buffer overflow  Examine software-development

vulnerabilities? policies and procedures.
 Interview responsible personnel.

6.5.3 Do coding techniques address insecure cryptographic  Examine software-development

storage? policies and procedures.
 Interview responsible personnel.

6.5.4 Do coding techniques address insecure communications?  Examine software-development

policies and procedures.
 Interview responsible personnel.

6.5.5 Do coding techniques address improper error handling?  Examine software-development

policies and procedures.
 Interview responsible personnel.

6.5.6 Do coding techniques address all “high risk” vulnerabilities  Examine software-development
identified in the vulnerability identification process (as policies and procedures.
defined in PCI DSS Requirement 6.1)?  Interview responsible personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 31
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested

For web applications and application interfaces (internal or external), are applications developed based on secure coding guidelines to
protect applications from the following additional vulnerabilities:
6.5.7 Do coding techniques address cross-site scripting (XSS)  Examine software-development
vulnerabilities? policies and procedures.
 Interview responsible personnel.

6.5.8 Do coding techniques address improper access control  Examine software-development

such as insecure direct object references, failure to restrict policies and procedures.
URL access, directory traversal, and failure to restrict user  Interview responsible personnel.
access to functions?

6.5.9 Do coding techniques address cross-site request forgery  Examine software-development

(CSRF)? policies and procedures.
 Interview responsible personnel.

6.5.10 Do coding techniques address broken authentication and  Examine software-development

session management? policies and procedures.
 Interview responsible personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 32
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.6 For public-facing web applications, are new threats and  Review documented processes.
vulnerabilities addressed on an ongoing basis, and are  Interview personnel.
these applications protected against known attacks by
 Examine records of application
applying either of the following methods?
security assessments.
 Reviewing public-facing web applications via manual
 Examine system configuration
or automated application vulnerability security
settings.
assessment tools or methods, as follows:
- At least annually
- After any changes
- By an organization that specializes in application
security
- That, at a minimum, all vulnerabilities in
Requirement 6.5 are included in the assessment
- That all vulnerabilities are corrected
- That the application is re-evaluated after the
corrections
Note: This assessment is not the same as the vulnerability
scans performed for Requirement 11.2.
– OR –
 Installing an automated technical solution that detects
and prevents web-based attacks (for example, a web-
application firewall) as follows:
- Is situated in front of public-facing web
applications to detect and prevent web-based
attacks.
- Is actively running and up to date as applicable.
- Is generating audit logs.
- Is configured to either block web-based attacks,
or generate an alert that is immediately
investigated.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 33
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
6.7 Are security policies and operational procedures for  Review security policies and
developing and maintaining secure systems and operational procedures.
applications:  Interview personnel.
 Documented
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 34
Implement Strong Access Control Measures
Requirement 7: Restrict access to cardholder data by business need to know
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
7.1 Is access to system components and cardholder data
limited to only those individuals whose jobs require such
access, as follows:
 Is there a written policy for access control that  Examine written access
incorporates the following? control policy.
- Defining access needs and privilege assignments
for each role
- Restriction of access to privileged user IDs to
least privileges necessary to perform job
responsibilities,
- Assignment of access based on individual
personnel’s job classification and function
- Documented approval (electronically or in writing)
by authorized parties for all access, including
listing of specific privileges approved
7.1.1 Are access needs for each role defined, including:  Examine roles and access
 System components and data resources that each need.
role needs to access for their job function?
 Level of privilege required (for example, user,
administrator, etc.) for accessing resources?

7.1.2 Is access to privileged user IDs restricted as follows:  Interview personnel.

 To least privileges necessary to perform job  Interview management.
responsibilities?  Review privileged user IDs.
 Assigned only to roles that specifically require that
privileged access?

7.1.3 Is access assigned based on individual personnel’s job  Interview management.

classification and function?  Review user IDs.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 35
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
7.1.4 Is documented approval by authorized parties required,  Review user IDs.
specifying required privileges?  Compare with documented
approvals.
 Compare assigned privileges
with documented approvals.

7.2 Is an access control system(s) in place for system

components to restrict access based on a user’s need to
know, and is it set to “deny all” unless specifically allowed,
as follows:

7.2.1 Is the access control system(s) in place on all system  Review vendor
components? documentation.
 Examine configuration
settings.

7.2.2 Is the access control system(s) configured to enforce  Review vendor

privileges assigned to individuals based on job documentation.
classification and function?  Examine configuration
settings.

7.2.3 Does the access control system(s) have a default “deny-  Review vendor
all” setting? documentation.
 Examine configuration
settings.

7.3 Are security policies and operational procedures for  Examine security policies and
restricting access to cardholder data: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 36
Requirement 8: Identify and authenticate access to system components
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
8.1 Are policies and procedures for user identification
management controls defined and in place for non-
consumer users and administrators on all system
components, as follows:

8.1.1 Are all users assigned a unique ID before allowing them to  Review password
access system components or cardholder data? procedures.
 Interview personnel.

8.1.2 Are additions, deletions, and modifications of user IDs,  Review password
credentials, and other identifier objects controlled such that procedures.
user IDs are implemented only as authorized (including  Examine privileged and
with specified privileges)? general user IDs and
associated authorizations.
 Observe system settings.

8.1.3 Is access for any terminated users immediately  Review password

deactivated or removed? procedures.
 Examine terminated users
accounts.
 Review current access lists.
 Observe returned physical
authentication devices.

8.1.4 Are inactive user accounts either removed or disabled  Review password
within 90 days? procedures.
 Observe user accounts.

8.1.5 (a) Are accounts used by third parties to access, support,  Review password
or maintain system components via remote access procedures.
enabled only during the time period needed and  Interview personnel.
disabled when not in use?
 Observe processes.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 37
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
(b) Are third-party remote access accounts monitored  Interview personnel.
when in use?  Observe processes.

8.1.6 (a) Are repeated access attempts limited by locking out  Review password
the user ID after no more than six attempts? procedures.
 Examine system configuration
settings.
(b) This testing procedure applies only to service
providers.

8.1.7 Once a user account is locked out, is the lockout duration  Review password
set to a minimum of 30 minutes or until an administrator procedures.
enables the user ID?  Examine system configuration
settings.

8.1.8 If a session has been idle for more than 15 minutes, are  Review password
users required to re-authenticate (for example, re-enter the procedures.
password) to re-activate the terminal or session?  Examine system configuration
settings.

8.2 In addition to assigning a unique ID, is one or more of the  Review password
following methods employed to authenticate all users? procedures.
 Something you know, such as a password or  Observe authentication
passphrase processes.
 Something you have, such as a token device or smart
card
 Something you are, such as a biometric

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 38
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
8.2.1 (a) Is strong cryptography used to render all  Review password
authentication credentials (such as procedures.
passwords/passphrases) unreadable during  Review vendor
transmission and storage on all system components? documentation.
 Examine system configuration
settings.
 Observe password files.
 Observe data transmissions.
(b) This testing procedure applies only to service
providers.

8.2.2 Is user identity verified before modifying any authentication  Review authentication
credential (for example, performing password resets, procedures.
provisioning new tokens, or generating new keys)?  Observe personnel.

8.2.3 (a) Are user password parameters configured to require  Examine system configuration
passwords/passphrases meet the following? settings to verify password
- A minimum password length of at least seven parameters.
characters
- Contain both numeric and alphabetic characters
Alternatively, the passwords/passphrases must have
complexity and strength at least equivalent to the
parameters specified above.
(b) This testing procedure applies only to service
providers.
8.2.4 (a) Are user passwords/passphrases changed at least  Review password
once every 90 days? procedures.
 Examine system configuration
settings.
(b) This testing procedure applies only to service
providers.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 39
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
8.2.5 (a) Must an individual submit a new  Review password
password/passphrase that is different from any of the procedures.
last four passwords/passphrases he or she has used?  Sample system components.
 Examine system configuration
settings.
(b) This testing procedure applies only to service
providers.

8.2.6 Are passwords/passphrases set to a unique value for each  Review password
user for first-time use and upon reset, and must each user procedures.
change their password immediately after the first use?  Examine system configuration
settings.
 Observe security personnel.

8.3 Is all individual non-console administrative access and all

remote access to the CDE secured using multi-factor
authentication, as follows:
Note: Multi-factor authentication requires that a minimum
of two of the three authentication methods (see PCI DSS
Requirement 8.2 for descriptions of authentication
methods) be used for authentication. Using one factor
twice (for example, using two separate passwords) is not
considered multi-factor authentication.

8.3.1 Is multi-factor authentication incorporated for all non-  Examine system

console access into the CDE for personnel with configurations.
administrative access?  Observe administrator logging
into CDE.

8.3.2 Is multi-factor authentication incorporated for all remote  Examine system

network access (both user and administrator, and including configurations.
third-party access for support or maintenance) originating  Observe personnel
from outside the entity’s network? connecting remotely.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 40
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
8.4 (a) Are authentication policies and procedures  Review policies and
documented and communicated to all users? procedures.
 Review distribution method.
 Interview personnel.
 Interview users.

8.4 (b) Do authentication policies and procedures include the  Review policies and
(cont.) following? procedures.
- Guidance on selecting strong authentication  Review documentation
credentials provided to users.
- Guidance for how users should protect their
authentication credentials
- Instructions not to reuse previously used
passwords
- Instructions that users should change passwords
if there is any suspicion the password could be
compromised

8.5 Are group, shared, or generic accounts, passwords, or  Review policies and
other authentication methods prohibited as follows: procedures.
 Generic user IDs and accounts are disabled or  Examine user ID lists.
removed;  Interview personnel.
 Shared user IDs for system administration activities
and other critical functions do not exist; and
 Shared and generic user IDs are not used to
administer any system components?

8.5.1 This requirement applies only to service providers.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 41
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
8.6 Where other authentication mechanisms are used (for  Review policies and
example, physical or logical security tokens, smart cards, procedures.
and certificates, etc.), is the use of these mechanisms  Interview personnel.
assigned as follows?
 Examine system configuration
 Authentication mechanisms must be assigned to an settings and/or physical
individual account and not shared among multiple controls.
accounts
 Physical and/or logical controls must be in place to
ensure only the intended account can use that
mechanism to gain access

8.7 Is all access to any database containing cardholder data

(including access by applications, administrators, and all
other users) restricted as follows:
(a) Is all user access to, user queries of, and user actions  Review database
on (for example, move, copy, delete), the database authentication policies and
through programmatic methods only (for example, procedures.
through stored procedures)?  Examine database and
application configuration
settings.
(b) Is user direct access to or queries to of databases  Review database
restricted to database administrators? authentication policies and
procedures.
 Examine database access
control settings.
 Examine database application
configuration settings.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 42
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
(c) Are application IDs only able to be used by the  Review database
applications (and not by individual users or other authentication policies and
processes)? procedures.
 Examine database access
control settings.
 Examine database application
configuration settings.

8.8 Are security policies and operational procedures for  Examine security policies and
identification and authentication: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 43
Requirement 9: Restrict physical access to cardholder data
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.1 Are appropriate facility entry controls in place to limit  Observe physical access controls.
and monitor physical access to systems in the  Observe personnel.
cardholder data environment?

9.1.1 (a) Are either video cameras or access control  Review policies and procedures.
mechanisms (or both) in place to monitor individual  Observe physical monitoring
physical access to sensitive areas? mechanisms.
Note: “Sensitive areas” refers to any data center, server  Observe security features.
room, or any area that houses systems that store,
process, or transmit cardholder data. This excludes
public-facing areas where only point-of-sale terminals
are present such as the cashier areas in a retail store.

(b) Are either video cameras or access control  Observe processes.

mechanisms (or both) protected from tampering or  Interview personnel.
disabling?
(c) Is data collected from video cameras and/or access  Review policies and procedures.
control mechanisms reviewed and correlated with  Interview security personnel.
other entries?
(d) Is data collected from video cameras and/or access  Review data retention processes.
control mechanisms stored for at least three months  Observe data storage.
unless otherwise restricted by law?
 Interview security personnel.

9.1.2 Are physical and/or logical controls in place to restrict  Review policies and procedures.
access to publicly accessible network jacks?  Interview personnel.
For example, network jacks located in public areas and  Observe locations.
areas accessible to visitors could be disabled and only
enabled when network access is explicitly authorized.
Alternatively, processes could be implemented to
ensure that visitors are escorted at all times in areas
with active network jacks.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 44
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.1.3 Is physical access to wireless access points, gateways,  Review policies and procedures.
handheld devices, networking/communications  Interview personnel.
hardware, and telecommunication lines restricted?
 Observe devices.

9.2 (a) Are procedures developed to easily distinguish  Review policies and procedures.
between onsite personnel and visitors, which  Interview personnel.
include:
 Observe identification methods
- Identifying onsite personnel and visitors (for
(e.g. badges).
example, assigning badges),
 Observe visitor processes.
- Changing access requirements, and
- Revoking terminated onsite personnel and
expired visitor identification (such as ID
badges)
For the purposes of Requirement 9, “onsite personnel”
refers to full-time and part-time employees, temporary
employees, contractors and consultants who are
physically present on the entity’s premises. A “visitor”
refers to a vendor, guest of any onsite personnel,
service workers, or anyone who needs to enter the
facility for a short duration, usually not more than one
day.

(b) Do identification methods (such as ID badges)  Observe identification methods.

clearly identify visitors and easily distinguish
between onsite personnel and visitors?
(c) Is access to the badge system limited to authorized  Observe physical controls and
personnel? access controls for the badge
system.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 45
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.3 Is physical access to sensitive areas controlled for  Interview personnel.
onsite personnel, as follows:  Examine access control lists.
 Is access authorized and based on individual job  Observe onsite personnel.
function?
 Compare lists of terminated
 Is access revoked immediately upon termination employees to access control lists.
 Upon termination, are all physical access
mechanisms, such as keys, access cards, etc.,
returned or disabled?

9.4 Is visitor identification and access handled as follows:

9.4.1 Are visitors authorized before entering, and escorted at  Review policies and procedures.
all times within, areas where cardholder data is  Observe visitor processes
processed or maintained? including how access is
controlled.
 Interview personnel.
 Observe visitors and badge use.

9.4.2 (a) Are visitors identified and given a badge or other  Observe badge use of personnel
identification that visibly distinguishes the visitors and visitors.
from onsite personnel?  Examine identification.
(b) Do visitor badges or other identification expire?  Observe process.
 Examine identification.

9.4.3 Are visitors asked to surrender the badge or other  Observe processes.
identification before leaving the facility or at the date of  Observe visitors leaving facility.
expiration?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 46
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.4.4 (a) Is a visitor log in use to record physical access to  Review policies and procedures.
the facility as well as for computer rooms and data  Examine the visitor log.
centers where cardholder data is stored or
transmitted?  Observe visitor processes.
 Examine log retention.
(b) Does the visitor log contain the visitor’s name, the  Review policies and procedures.
firm represented, and the onsite personnel  Examine the visitor log.
authorizing physical access?
(c) Is the visitor log retained for at least three months?  Review policies and procedures.
 Examine visitor log retention.

9.5 Are all media physically secured (including but not  Review policies and procedures
limited to computers, removable electronic media, paper for physically securing media.
receipts, paper reports, and faxes)?  Interview personnel.
For purposes of Requirement 9, “media” refers to all
paper and electronic media containing cardholder data.

9.5.1 Is the location where media back-ups are stored  Review policies and procedures
reviewed at least annually to confirm storage is secure? for reviewing offsite media
locations.
 Interview security personnel.

9.6 (a) Is strict control maintained over the internal or  Review policies and procedures
external distribution of any kind of media? for distribution of media.
(b) Do controls include the following:

9.6.1 Is media classified so the sensitivity of the data can be  Review policies and procedures
determined? for media classification.
 Interview security personnel.

9.6.2 Is media sent by secured courier or other delivery  Interview personnel.

method that can be accurately tracked?  Examine media distribution
tracking logs and documentation.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 47
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.6.3 Is management approval obtained prior to moving the  Interview personnel.
media (especially when media is distributed to  Examine media distribution
individuals)? tracking logs and documentation.

9.7 Is strict control maintained over the storage and  Review policies and procedures.
accessibility of media?

9.7.1 (a) Are inventory logs of all media properly maintained?  Examine inventory logs.

(b) Are periodic media inventories conducted at least  Examine inventory logs.
annually?  Interview personnel.

9.8 (a) Is all media destroyed when it is no longer needed  Review periodic media destruction
for business or legal reasons? policies and procedures.
(b) Is there a periodic media destruction policy that  Review periodic media destruction
defines requirements for the following? policies and procedures.
- Hard-copy materials must be crosscut
shredded, incinerated, or pulped such that
there is reasonable assurance the hard-copy
materials cannot be reconstructed.
- Storage containers used for materials that are
to be destroyed must be secured.
- Cardholder data on electronic media must be
rendered unrecoverable (e.g., via a secure wipe
program in accordance with industry-accepted
standards for secure deletion, or by physically
destroying the media).
(c) Is media destruction performed as follows:

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 48
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.8.1 (a) Are hardcopy materials cross-cut shredded,  Interview personnel.
incinerated, or pulped so that cardholder data  Examine procedures.
cannot be reconstructed?
 Observe processes.
(b) Are storage containers used for materials that  Examine security of storage
contain information to be destroyed secured to containers.
prevent access to the contents?

9.8.2 Is cardholder data on electronic media rendered  Observe processes.

unrecoverable (e.g. via a secure wipe program in  Interview personnel.
accordance with industry-accepted standards for secure
deletion, or otherwise by physically destroying the
media), so that cardholder data cannot be
reconstructed?

9.9 Are devices that capture payment card data via direct
physical interaction with the card protected against
tampering and substitution as follows?
Note: This requirement applies to card-reading devices
used in card-present transactions (that is, card swipe or
dip) at the point of sale. This requirement is not intended
to apply to manual key-entry components such as
computer keyboards and POS keypads.

(a) Do policies and procedures require that a list of  Review policies and procedures.
such devices be maintained?
(b) Do policies and procedures require that devices are  Review policies and procedures.
periodically inspected to look for tampering or
substitution?
(c) Do policies and procedures require that personnel  Review policies and procedures.
are trained to be aware of suspicious behavior and
to report tampering or substitution of devices?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 49
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.9.1 (a) Does the list of devices include the following?  Examine the list of devices.
- Make, model of device
- Location of device (for example, the address of
the site or facility where the device is located)
- Device serial number or other method of unique
identification
(b) Is the list accurate and up to date?  Observe devices and device
locations and compare to list.
(c) Is the list of devices updated when devices are  Interview personnel.
added, relocated, decommissioned, etc.?

9.9.2 (a) Are device surfaces periodically inspected to detect  Interview personnel.
tampering (for example, addition of card skimmers  Observe inspection processes
to devices), or substitution (for example, by and compare to defined
checking the serial number or other device processes.
characteristics to verify it has not been swapped
with a fraudulent device) as follows?
Note: Examples of signs that a device might have been
tampered with or substituted include unexpected
attachments or cables plugged into the device, missing
or changed security labels, broken or differently colored
casing, or changes to the serial number or other
external markings.

(b) Are personnel aware of procedures for inspecting  Interview personnel.

devices?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 50
 Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
9.9.3 Are personnel trained to be aware of attempted
tampering or replacement of devices, to include the
following?
(a) Do training materials for personnel at point-of-sale  Review training materials.
locations include the following?
- Verify the identity of any third-party persons
claiming to be repair or maintenance personnel,
prior to granting them access to modify or
troubleshoot devices.
- Do not install, replace, or return devices without
verification.
- Be aware of suspicious behavior around
devices (for example, attempts by unknown
persons to unplug or open devices).
- Report suspicious behavior and indications of
device tampering or substitution to appropriate
personnel (for example, to a manager or
security officer).
9.9.3 (b) Have personnel at point-of-sale locations received  Interview personnel at POS
(cont.) training, and are they aware of procedures to detect locations.
and report attempted tampering or replacement of
devices?
9.10 Are security policies and operational procedures for  Examine security policies and
restricting physical access to cardholder data: operational procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 51
Regularly Monitor and Test Networks
Requirement 10: Track and monitor all access to network resources and cardholder data
Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
10.1 (a) Are audit trails enabled and active for system  Observe processes.
components?  Interview system
administrator.
(b) Is access to system components linked to individual  Observe processes.
users?  Interview system
administrator.

10.2 Are automated audit trails implemented for all system

components to reconstruct the following events:

10.2.1 All individual user accesses to cardholder data?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.2.2 All actions taken by any individual with root or  Interview personnel.
administrative privileges?  Observe audit logs.
 Examine audit log settings.

10.2.3 Access to all audit trails?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.2.4 Invalid logical access attempts?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.2.5 Use of and changes to identification and authentication  Interview personnel.

mechanismsincluding but not limited to creation of new  Observe audit logs.
accounts and elevation of privilegesand all changes,
 Examine audit log settings.
additions, or deletions to accounts with root or
administrative privileges?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 52
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
10.2.6 Initialization, stopping, or pausing of the audit logs?  Interview personnel.
 Observe audit logs.
 Examine audit log settings.

10.2.7 Creation and deletion of system-level objects?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.3 Are the following audit trail entries recorded for all
system components for each event:

10.3.1 User identification?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.3.2 Type of event?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.3.3 Date and time?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.3.4 Success or failure indication?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.3.5 Origination of event?  Interview personnel.

 Observe audit logs.
 Examine audit log settings.

10.3.6 Identity or name of affected data, system component, or  Interview personnel.

resource?  Observe audit logs.
 Examine audit log settings.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 53
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
10.4 Are all critical system clocks and times synchronized  Review time configuration
through use of time synchronization technology, and is standards and processes.
the technology kept current?
Note: One example of time synchronization technology
is Network Time Protocol (NTP).

10.4.1 Are the following processes implemented for critical

systems to have the correct and consistent time:
(a) Do only designated central time server(s) receive  Review time configuration
time signals from external sources, and are time standards and processes.
signals from external sources based on International  Examine time-related
Atomic Time or UTC? system parameters.
(b) Where there is more than one designated time  Review time configuration
server, do the time servers peer with each other to standards and processes.
keep accurate time?  Examine time-related
system parameters.
(c) Do systems receive time only from designated  Review time configuration
central time server(s)? standards and processes.
 Examine time-related
system parameters.

10.4.2 Is time data is protected as follows:  Examine system

(a) Is access to time data restricted to only personnel configurations and time-
with a business need to access time data? synchronization settings.

(b) Are changes to time settings on critical systems  Examine system

logged, monitored, and reviewed? configurations and time-
synchronization settings
and logs.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 54
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
10.4.3 Are time settings received from specific, industry-  Examine system
accepted time sources? (This is to prevent a malicious configurations.
individual from changing the clock).
Optionally, those updates can be encrypted with a
symmetric key, and access control lists can be created
that specify the IP addresses of client machines that will
be provided with the time updates (to prevent
unauthorized use of internal time servers).

10.5 Are audit trails secured so they cannot be altered, as

follows:

10.5.1 Is viewing of audit trails limited to those with a job-  Interview system
related need? administrators.
 Examine system
configurations and
permissions.

10.5.2 Are audit trail files protected from unauthorized  Interview system
modifications via access control mechanisms, physical administrators.
segregation, and/or network segregation?  Examine system
configurations and
permissions.

10.5.3 Are audit trail files promptly backed up to a centralized  Interview system
log server or media that is difficult to alter? administrators.
 Examine system
configurations and
permissions.

10.5.4 Are logs for external-facing technologies (for example,  Interview system
wireless, firewalls, DNS, mail) written onto a secure, administrators.
centralized, internal log server or media?  Examine system
configurations and
permissions.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 55
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
10.5.5 Is file-integrity monitoring or change-detection software  Examine settings,
used on logs to ensure that existing log data cannot be monitored files, and results
changed without generating alerts (although new data from monitoring activities.
being added should not cause an alert)?

10.6 Are logs and security events for all system components
reviewed to identify anomalies or suspicious activity as
follows?
Note: Log harvesting, parsing, and alerting tools may be
used to achieve compliance with Requirement 10.6.

10.6.1 (a) Are written policies and procedures defined for  Review security policies
reviewing the following at least daily, either and procedures.
manually or via log tools?
- All security events
- Logs of all system components that store,
process, or transmit CHD and/or SAD
- Logs of all critical system components
- Logs of all servers and system components
that perform security functions (for example,
firewalls, intrusion-detection systems/intrusion-
prevention systems (IDS/IPS), authentication
servers, e-commerce redirection servers, etc.)
(b) Are the above logs and security events reviewed at  Observe processes.
least daily?  Interview personnel.

10.6.2 (a) Are written policies and procedures defined for  Review security policies
reviewing logs of all other system components and procedures.
periodically—either manually or via log tools—
based on the organization’s policies and risk
management strategy?
(b) Are reviews of all other system components  Review risk assessment
performed in accordance with organization’s policies documentation.
and risk management strategy?  Interview personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 56
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
10.6.3 (a) Are written policies and procedures defined for  Review security policies
following up on exceptions and anomalies identified and procedures.
during the review process?
(b) Is follow up to exceptions and anomalies  Observe processes.
performed?  Interview personnel.

10.7 (a) Are audit log retention policies and procedures in  Review security policies
place and do they require that logs are retained for and procedures.
at least one year, with a minimum of three months
immediately available for analysis (for example,
online, archived, or restorable from backup)?
(b) Are audit logs retained for at least one year?  Interview personnel.
 Examine audit logs.
(c) Are at least the last three months’ logs immediately  Interview personnel.
available for analysis?  Observe processes.

10.8 This requirement applies only to service providers.

10.9 Are security policies and operational procedures for  Review security policies
monitoring all access to network resources and and operational
cardholder data: procedures.
 Documented  Interview personnel.
 In use
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 57
Requirement 11: Regularly test security systems and processes
Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.1 (a) Are processes implemented for detection and  Review policies and
identification of both authorized and unauthorized procedures.
wireless access points on a quarterly basis?
Note: Methods that may be used in the process include,
but are not limited to, wireless network scans,
physical/logical inspections of system components and
infrastructure, network access control (NAC), or wireless
IDS/IPS.
Whichever methods are used, they must be sufficient to
detect and identify any unauthorized devices.

(b) Does the methodology detect and identify any  Evaluate the methodology.
unauthorized wireless access points, including at least
the following?
- WLAN cards inserted into system components;
- Portable or mobile devices attached to system
components to create a wireless access point (for
example, by USB, etc.); and
- Wireless devices attached to a network port or
network device.
(c) If wireless scanning is utilized to identify authorized  Examine output from recent
and unauthorized wireless access points, is the scan wireless scans.
performed at least quarterly for all system components
and facilities?
(d) If automated monitoring is utilized (for example,  Examine configuration
wireless IDS/IPS, NAC, etc.), is monitoring configured settings.
to generate alerts to notify personnel?
11.1.1 Is an inventory of authorized wireless access points  Examine inventory records.
maintained and a business justification documented for all
authorized wireless access points?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 58
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.1.2 (a) Does the incident response plan define and require a  Examine incident response
response in the event that an unauthorized wireless plan (see Requirement
access point is detected? 12.10).
(b) Is action taken when unauthorized wireless access  Interview responsible
points are found? personnel.
 Inspect recent wireless
scans and related
responses.
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), as follows:
Note: Multiple scan reports can be combined for the
quarterly scan process to show that all systems were
scanned and all applicable vulnerabilities have been
addressed. Additional documentation may be required to
verify non-remediated vulnerabilities are in the process of
being addressed.
For initial PCI DSS compliance, it is not required that four
quarters of passing scans be completed if the assessor
verifies 1) the most recent scan result was a passing scan,
2) the entity has documented policies and procedures
requiring quarterly scanning, and 3) vulnerabilities noted in
the scan results have been corrected as shown in a re-
scan(s). For subsequent years after the initial PCI DSS
review, four quarters of passing scans must have occurred.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 59
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.2.1 (a) Are quarterly internal vulnerability scans performed?  Review scan reports.

(b) Does the quarterly internal scan process address all  Review scan reports.
“high risk” vulnerabilities and include rescans to verify
all “high-risk” vulnerabilities (as defined in PCI DSS
Requirement 6.1) are resolved?
(c) Are quarterly internal scans performed by a qualified  Interview personnel.
internal resource(s) or qualified external third party,
and if applicable, does organizational independence of
the tester exist (not required to be a QSA or ASV)?
11.2.2 (a) Are quarterly external vulnerability scans performed?  Review results from the
Note: Quarterly external vulnerability scans must be four most recent quarters of
performed by an Approved Scanning Vendor (ASV), external vulnerability scans.
approved by the Payment Card Industry Security
Standards Council (PCI SSC).
Refer to the ASV Program Guide published on the PCI
SSC website for scan customer responsibilities, scan
preparation, etc.

(b) Do external quarterly scan and rescan results satisfy  Review results of each
the ASV Program Guide requirements for a passing external quarterly scan and
scan (for example, no vulnerabilities rated 4.0 or higher rescan.
by the CVSS, and no automatic failures)?
(c) Are quarterly external vulnerability scans performed by  Review results of each
a PCI SSC Approved Scanning Vendor (ASV? external quarterly scan and
rescan.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 60
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.2.3 (a) Are internal and external scans, and rescans as  Examine and correlate
needed, performed after any significant change? change control
Note: Scans must be performed by qualified personnel. documentation and scan
reports.
(b) Does the scan process include rescans until:  Review scan reports.
- For external scans, no vulnerabilities exist that are
scored 4.0 or higher by the CVSS,
- For internal scans, a passing result is obtained or
all “high-risk” vulnerabilities as defined in PCI DSS
Requirement 6.1 are resolved?
(c) Are scans performed by a qualified internal resource(s)  Interview personnel.
or qualified external third party, and if applicable, does
organizational independence of the tester exist (not
required to be a QSA or ASV)?
11.3 Does the penetration-testing methodology include the  Examine penetration-
following? testing methodology.
 Is based on industry-accepted penetration testing  Interview responsible
approaches (for example, NIST SP800-115) personnel.
 Includes coverage for the entire CDE perimeter and
critical systems
 Includes testing from both inside and outside the
network
 Includes testing to validate any segmentation and
scope-reduction controls
 Defines application-layer penetration tests to include, at
a minimum, the vulnerabilities listed in Requirement 6.5
 Defines network-layer penetration tests to include
components that support network functions as well as
operating systems
 Includes review and consideration of threats and
vulnerabilities experienced in the last 12 months
 Specifies retention of penetration testing results and
remediation activities results

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 61
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.3.1 (a) Is external penetration testing performed per the  Examine scope of work.
defined methodology, at least annually, and after any  Examine results from the
significant infrastructure or application changes to the most recent external
environment (such as an operating system upgrade, a penetration test.
sub-network added to the environment, or an added
web server)?
(b) Are tests performed by a qualified internal resource or  Interview responsible
qualified external third party, and if applicable, does personnel.
organizational independence of the tester exist (not
required to be a QSA or ASV)?
11.3.2 (a) Is internal penetration testing performed per the  Examine scope of work.
defined methodology, at least annually, and after any  Examine results from the
significant infrastructure or application changes to the most recent internal
environment (such as an operating system upgrade, a penetration test.
sub-network added to the environment, or an added
web server)?
(b) Are tests performed by a qualified internal resource or  Interview responsible
qualified external third party, and if applicable, does personnel.
organizational independence of the tester exist (not
required to be a QSA or ASV)?
11.3.3 Are exploitable vulnerabilities found during penetration  Examine penetration testing
testing corrected, followed by repeated testing to verify the results.
corrections?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 62
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.3.4 If segmentation is used to isolate the CDE from other
networks:
(a) Are penetration-testing procedures defined to test all  Examine segmentation
segmentation methods, to confirm they are operational controls.
and effective, and isolate all out-of-scope systems from  Review penetration-testing
systems in the CDE? methodology.
(b) Does penetration testing to verify segmentation  Examine results from the
controls meet the following? most recent penetration
- Performed at least annually and after any changes test.
to segmentation controls/methods.
- Covers all segmentation controls/methods in use.
- Verifies that segmentation methods are
operational and effective, and isolate all out-of-
scope systems from systems in the CDE.
(c) Are tests performed by a qualified internal resource or  Interview responsible
qualified external third party, and if applicable, does personnel.
organizational independence of the tester exist (not
required to be a QSA or ASV)?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 63
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.3.4.1 This requirement applies only to service providers.

11.4 (a) Are intrusion-detection and/or intrusion-prevention  Examine system

techniques that detect and/or prevent intrusions into configurations.
the network in place to monitor all traffic:  Examine network diagrams.
- At the perimeter of the cardholder data
environment, and
- At critical points in the cardholder data
environment.
(b) Are intrusion-detection and/or intrusion-prevention  Examine system
techniques configured to alert personnel of suspected configurations.
compromises?  Interview responsible
personnel.
(c) Are all intrusion-detection and prevention engines,  Examine IDS/IPS
baselines, and signatures kept up-to-date? configurations.
 Examine vendor
documentation.

11.5 (a) Is a change-detection mechanism (for example, file-  Observe system settings
integrity monitoring tools) deployed to detect and monitored files.
unauthorized modification (including changes,  Examine system
additions, and deletions) of critical system files, configuration settings.
configuration files, or content files?
Examples of files that should be monitored include:
• System executables
• Application executables
• Configuration and parameter files
• Centrally stored, historical or archived, log, and audit
files
• Additional critical files determined by entity (for example,
through risk assessment or other means)

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 64
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
11.5 (b) Is the change-detection mechanism configured to alert  Observe system settings
(cont.) personnel to unauthorized modification (including and monitored files.
changes, additions, and deletions) of critical system  Review results from
files, configuration files or content files, and do the monitoring activities.
tools perform critical file comparisons at least weekly?
Note: For change detection purposes, critical files are
usually those that do not regularly change, but the
modification of which could indicate a system compromise
or risk of compromise. Change detection mechanisms such
as file-integrity monitoring products usually come pre-
configured with critical files for the related operating
system. Other critical files, such as those for custom
applications, must be evaluated and defined by the entity
(that is the merchant or service provider).

11.5.1 Is a process in place to respond to any alerts generated by  Examine system

the change-detection solution? configuration settings.

11.6 Are security policies and operational procedures for  Examine security policies
security monitoring and testing: and operational
 Documented procedures.
 In use  Interview personnel.
 Known to all affected parties?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 65
Maintain an Information Security Policy
Requirement 12: Maintain a policy that addresses information security for all personnel
Note: For the purposes of Requirement 12, “personnel” refers to full-time part-time employees, temporary employees and personnel, and
contractors and consultants who are “resident” on the entity’s site or otherwise have access to the company’s site cardholder data environment.

Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.1 Is a security policy established, published, maintained,  Review the information
and disseminated to all relevant personnel? security policy.
12.1.1 Is the security policy reviewed at least annually and  Review the information
updated when the environment changes? security policy.
 Interview responsible
personnel.

12.2 (a) Is an annual risk assessment process implemented  Review annual risk
that: assessment process.
- Identifies critical assets, threats, and  Interview personnel.
vulnerabilities, and
- Results in a formal, documented analysis of
risk?
Examples of risk assessment methodologies include but
are not limited to OCTAVE, ISO 27005 and NIST SP
800-30.

(b) Is the risk assessment process performed at least  Review risk assessment
annually and upon significant changes to the documentation.
environment (for example, acquisition, merger,  Interview responsible
relocation, etc.)? personnel.

12.3 Are usage policies for critical technologies developed to

define proper use of these technologies and require the
following:
Note: Examples of critical technologies include, but are
not limited to, remote access and wireless technologies,
laptops, tablets, removable electronic media, e-mail
usage and Internet usage.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 66
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.3.1 Explicit approval by authorized parties to use the  Review usage policies.
technologies?  Interview responsible
personnel.
12.3.2 Authentication for use of the technology?  Review usage policies.
 Interview responsible
personnel.
12.3.3 A list of all such devices and personnel with access?  Review usage policies.
 Interview responsible
personnel.
12.3.4 A method to accurately and readily determine owner,  Review usage policies.
contact information, and purpose (for example, labeling,  Interview responsible
coding, and/or inventorying of devices)? personnel.
12.3.5 Acceptable uses of the technologies?  Review usage policies.
 Interview responsible
personnel.
12.3.6 Acceptable network locations for the technologies?  Review usage policies.
 Interview responsible
personnel.
12.3.7 List of company-approved products?  Review usage policies.
 Interview responsible
personnel.
12.3.8 Automatic disconnect of sessions for remote-access  Review usage policies.
technologies after a specific period of inactivity?  Interview responsible
personnel.
12.3.9 Activation of remote-access technologies for vendors  Review usage policies.
and business partners only when needed by vendors  Interview responsible
and business partners, with immediate deactivation after personnel.
use?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 67
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.3.10 (a) For personnel accessing cardholder data via  Review usage policies.
remote-access technologies, does the policy specify  Interview responsible
the prohibition of copying, moving, and storage of personnel.
cardholder data onto local hard drives and
removable electronic media, unless explicitly
authorized for a defined business need?
Where there is an authorized business need, the usage
policies must require the data be protected in
accordance with all applicable PCI DSS Requirements.

(b) For personnel with proper authorization, does the  Review usage policies.
policy require the protection of cardholder data in  Interview responsible
accordance with PCI DSS Requirements? personnel.
12.4 Do security policy and procedures clearly define  Review information security
information security responsibilities for all personnel? policy and procedures.
 Interview a sample of
responsible personnel.

12.4.1 This requirement applies only to service providers.

12.5 (a) Is responsibility for information security formally  Review information security
assigned to a Chief Security Officer or other policy and procedures.
security-knowledgeable member of management?
(b) Are the following information security management
responsibilities formally assigned to an individual or
team:
12.5.1 Establishing, documenting, and distributing security  Review information security
policies and procedures? policy and procedures.
12.5.2 Monitoring and analyzing security alerts and information,  Review information security
and distributing to appropriate personnel? policy and procedures.
12.5.3 Establishing, documenting, and distributing security  Review information security
incident response and escalation procedures to ensure policy and procedures.
timely and effective handling of all situations?

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 68
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.5.4 Administering user accounts, including additions,  Review information security
deletions, and modifications? policy and procedures.
12.5.5 Monitoring and controlling all access to data?  Review information security
policy and procedures.

12.6 (a) Is a formal security awareness program in place to  Review security awareness
make all personnel aware of the cardholder data program.
security policy and procedures?
(b) Do security awareness program procedures include
the following:
12.6.1 (a) Does the security awareness program provide  Review security awareness
multiple methods of communicating awareness and program.
educating personnel (for example, posters, letters,  Review security awareness
memos, web based training, meetings, and program procedures.
promotions)?
 Review security awareness
Note: Methods can vary depending on the role of the program attendance
personnel and their level of access to the cardholder records.
data.

(b) Are personnel educated upon hire and at least  Examine security
annually? awareness program
procedures and
documentation.
(c) Have employees completed awareness training and  Interview personnel.
are they aware of the importance of cardholder data
security?
12.6.2 Are personnel required to acknowledge at least annually  Examine security
that they have read and understood the security policy awareness program
and procedures? procedures and
documentation.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 69
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.7 Are potential personnel (see definition of “personnel”  Interview Human Resource
above) screened prior to hire to minimize the risk of department management.
attacks from internal sources?
Examples of background checks include previous
employment history, criminal record, credit history and
reference checks.
Note: For those potential personnel to be hired for
certain positions, such as store cashiers who only have
access to one card number at a time when facilitating a
transaction, this requirement is a recommendation only.

12.8 Are policies and procedures maintained and

implemented to manage service providers with whom
cardholder data is shared, or that could affect the
security of cardholder data, as follows:
12.8.1 Is a list of service providers maintained, including a  Review policies and
description of the service(s) provided? procedures.
 Observe processes.
 Review list of service
providers.
12.8.2 Is a written agreement maintained that includes an  Observe written
acknowledgement that the service providers are agreements.
responsible for the security of cardholder data the  Review policies and
service providers possess or otherwise store, process, procedures.
or transmit on behalf of the customer, or to the extent
that they could impact the security of the customer’s
cardholder data environment?
Note: The exact wording of an acknowledgement will
depend on the agreement between the two parties, the
details of the service being provided, and the
responsibilities assigned to each party. The
acknowledgement does not have to include the exact
wording provided in this requirement.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 70
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.8.3 Is there an established process for engaging service  Observe processes.
providers, including proper due diligence prior to  Review policies and
engagement? procedures and supporting
documentation.

12.8.4 Is a program maintained to monitor service providers’  Observe processes.

PCI DSS compliance status at least annually?  Review policies and
procedures and supporting
documentation.

12.8.5 Is information maintained about which PCI DSS  Observe processes.

requirements are managed by each service provider,  Review policies and
and which are managed by the entity? procedures and supporting
documentation.

12.9 This requirement applies only to service providers.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 71
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.10 Has an incident response plan been implemented in
preparation to respond immediately to a system breach,
as follows:
12.10.1 (a) Has an incident response plan been created to be  Review the incident
implemented in the event of system breach? response plan.
 Review incident response
plan procedures.
(b) Does the plan address the following, at a minimum:

- Roles, responsibilities, and communication and  Review incident response

contact strategies in the event of a compromise plan procedures.
including notification of the payment brands, at
a minimum?
- Specific incident response procedures?  Review incident response
plan procedures.
- Business recovery and continuity procedures?  Review incident response
plan procedures.
- Data backup processes?  Review incident response
plan procedures.
- Analysis of legal requirements for reporting  Review incident response
compromises? plan procedures.
- Coverage and responses of all critical system  Review incident response
components? plan procedures.
- Reference or inclusion of incident response  Review incident response
procedures from the payment brands? plan procedures.
12.10.2 Is the plan reviewed and tested at least annually,  Review incident response
including all elements listed in Requirement 12.10.1? plan procedures .
 Interview responsible
personnel.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 72
 Response
(Check one response for each question)
PCI DSS Question Expected Testing
Yes with Not
Yes CCW No N/A Tested
12.10.3 Are specific personnel designated to be available on a  Observe processes.
24/7 basis to respond to alerts?  Review policies.
 Interview responsible
personnel.
12.10.4 Is appropriate training provided to staff with security  Observe processes.
breach response responsibilities?  Review incident response
plan procedures.
 Interview responsible
personnel.
12.10.5 Are alerts from security monitoring systems included in  Observe processes.
the incident response plan?  Review incident response
plan procedures.
12.10.6 Is a process developed and in place to modify and  Observe processes.
evolve the incident response plan according to lessons  Review incident response
learned and to incorporate industry developments? plan procedures.
 Interview responsible
personnel.
12.11 This requirement applies only to service providers.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 73
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 for Card-Present POS POI Terminal
Connections
Response
(Check one response for each question)
PCI DSS Question Expected Testing Yes
with Not
Yes CCW No N/A Tested
A2.1 For POS POI terminals (at the merchant or payment-  Review documentation (for
acceptance location) using SSL and/or early TLS: Are the example, vendor documentation,
devices confirmed to not be susceptible to any known system/network configuration
exploits for SSL/early TLS details, etc.) that verifies POS
Note: This requirement is intended to apply to the entity POI devices are not susceptible
with the POS POI terminal, such as a merchant. This to any known exploits for
requirement is not intended for service providers who serve SSL/early TLS.
as the termination or connection point to those POS POI
terminals. Requirements A2.2 and A2.3 apply to POS POI
service providers.

A2.2 This requirement applies only to service providers.

A2.3 This requirement applies only to service providers.

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 to this Appendix should use the DESV Supplemental Reporting Template and Supplemental Attestation
of Compliance for reporting, and consult with the applicable payment brand and/or acquirer for submission procedures.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 74
Appendix B: Compensating Controls Worksheet
Use this worksheet to define compensating controls for any requirement where “YES with CCW” was
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 Define the compensating controls and
Compensating explain how they address the
Controls objectives of the original control and
the increased risk, if any.
5. Validation of Define how the compensating controls
Compensating were validated and tested.
Controls
6. Maintenance Define process and controls in place to
maintain compensating controls.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 75
Appendix C: Explanation of Non-Applicability
If the “N/A” (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

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 76
Appendix D: Explanation of Requirements Not Tested
If the “Not Tested” column was checked in the questionnaire, use this worksheet to explain why the
related requirement was not reviewed as part of the assessment.

Describe which part(s) of the

Requirement requirement was not tested Describe why requirements were not tested
Examples:

Requirement 12 Requirement 12.2 was the only This assessment only covers requirements in
requirement tested. All other Milestone 1 of the Prioritized Approach.
requirements from Requirement 12 were
excluded.

Requirements Only Requirement 9 was reviewed for this Company is a physical hosting provider (CO-
1-8, 10-12 assessment. All other requirements were LO), and only physical security controls were
excluded. considered for this assessment.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 2: Self-Assessment Questionnaire June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 77
Section 3: Validation and Attestation Details

Part 3. PCI DSS Validation

This AOC is based on results noted in SAQ D (Section 2), dated (SAQ completion date).
Based on the results documented in the SAQ D 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, all questions 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: One or more requirements are marked “No” due to a legal
restriction that prevents the requirement from being met. This option requires additional review from
acquirer or payment brand.
If checked, complete the following:

Affected Requirement Details of how legal constraint prevents requirement being met

Part 3a. Acknowledgement of Status

Signatory(s) confirms:
(Check all that apply)

PCI DSS Self-Assessment Questionnaire D, 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.1 SAQ D for Merchants, Rev. 1.0 – Section 3: Validation and Attestation Details June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 78
 Part 3. PCI DSS Validation (continued)
Part 3a. Acknowledgement of Status (continued)
No evidence of full track data*, CAV2, CVC2, CID, or CVV2 data, or PIN data storage after transaction
authorization was found on ANY system reviewed during this assessment.
ASV scans are being completed by the PCI SSC Approved Scanning Vendor (ASV Name).

Part 3b. Merchant Attestation

Signature of Merchant Executive Officer  Date:

Merchant Executive Officer Name: Title:

Part 3c. Qualified Security Assessor (QSA) Acknowledgement (if applicable)

If a QSA was involved or assisted with
this assessment, describe the role
performed:

Signature of Duly Authorized Officer of QSA Company  Date:

Duly Authorized Officer Name: QSA Company:

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:

*
Data encoded in the magnetic stripe or equivalent data on a chip used for authorization during a card-present transaction.
Entities may not retain full track data after transaction authorization. The only elements of track data that may be retained are
primary account number (PAN), expiration date, and cardholder name.
The three- or four-digit value printed by the signature panel or on the face of a payment card used to verify card-not-present
transactions.
Personal identification number entered by cardholder during a card-present transaction, and/or encrypted PIN block present
within the transaction message.
PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 3: Validation and Attestation Details June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 79
 Part 4. Action Plan for Non-Compliant Requirements
Select the appropriate response for “Compliant to PCI DSS Requirements” for each requirement. If you answer
“No” to any of the requirements, you 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 the applicable payment brand(s) before completing Part 4.
Compliant to PCI Remediation Date and
PCI DSS DSS Requirements Actions
Description of Requirement
Requirement (Select One) (If “NO” selected for any
YES NO Requirement)

Install and maintain a firewall

1
configuration to protect cardholder data.

2 Do not use vendor-supplied defaults for

system passwords and other security
parameters.

3 Protect stored cardholder data.

Encrypt transmission of cardholder data

4
across open, public networks.

Protect all systems against malware

5 and regularly update anti-virus software
or programs.

Develop and maintain secure systems

6
and applications.

Restrict access to cardholder data by

7
business need to know.

Identify and authenticate access to

8
system components.

Restrict physical access to cardholder

9
data.

Track and monitor all access to network

10
resources and cardholder data.

Regularly test security systems and

11
processes.

Maintain a policy that addresses

12
information security for all personnel.

Additional PCI DSS Requirements for

Entities using SSL/Early TLS for Card-
Appendix A2
Present POS POI Terminal
Connections.

PCI DSS v3.2.1 SAQ D for Merchants, Rev. 1.0 – Section 3: Validation and Attestation Details June 2018
© 2006-2018 PCI Security Standards Council, LLC. All Rights Reserved. Page 80